Custom Solutions
No base fee. Priced feature by feature, scoped with you.
Most operators fit a Reconcile tier or the register's per-transaction model. For the ones who do not, the Custom plan is priced feature by feature. No base fee. The bill is the features agreed with your team, at the amounts agreed. Each feature starts from a list price in the console and is agreed with your team before it is billed.
The features a custom plan is built from.
These are the features listed publicly in the price list. Others exist in the console; each is scoped and priced with you, never quoted from this page.
Reconciliation AI
The reconciliation workspace with a model reading every variance beside the point-of-sale, Metrc and count records: likely causes ranked and the next step proposed, never a correction made on its own.
Priced per agreement, from the price list in force.
Manifest & receiving firewall
Every inbound manifest checked line by line before stock is accepted: quarantine, recall and expiry holds, short and over deliveries, and nothing sellable until a person accepts it.
Priced per agreement, from the price list in force.
Vendor protection
A vendor issue opened from the dock with its evidence, tracked through return, buyback or replacement, with a secure link the vendor answers on.
Priced per agreement, from the price list in force.
Amounts already agreed with a customer never change when a list price changes. Nothing on this page is a quote.
Four situations we scope rather than force into a tier.
- Requires setup
A point of sale without a read connector
Only one incumbent POS has a built connector today. For another, we scope a read connector under the implementation agreement, or start from that system's CSV export, before anything is signed.
- Planned
A reporting feed into your own tooling
Reconciliation findings, receiving exceptions or the audit log flowing into your BI or data warehouse. Scoped as an export; a public customer API is on the roadmap and is not sold as live.
- Available
Multi-brand operators on one back end
Several retail brands sharing one operation have different reporting and access needs from a plain multi-location rollout. Roles, locations and findings are scoped to how you actually run.
- Available
An audit-led engagement
Start with the NYS Systems & Compliance Audit and let its findings decide which features you take on, in what order.
- Available
- Available features still require store setup and authorized data. This is not a connected-account status.
- Requires setup
- Provider credentials, a partner agreement or approval may be needed before use.
- Planned
- Not available yet.
Scoped with you, in three steps.
- 01
Discovery
Your POS, your locations, your state system and what you need out of the data. Twenty minutes to an hour, with Ken and Charles.
- 02
A written scope
The features, what each does for you, its status today, and the monthly amount agreed for each. What is roadmap is marked roadmap.
- 03
Implementation
Delivered by the team under the implementation agreement: connections, mapping, baseline, training and a controlled cutover where the register is involved.
Not sure which plan fits?
Tell us your POS, your state system and your location count, and we will say honestly whether you need Custom or a standard tier.