Metrc
Package and transaction data is modeled to reconcile against state traceability reporting rather than being reshaped at export time.
Integrations
Connected where it actually matters.
Traceability, marketplaces, banking, and the hardware on your counter. This page lists what has an implementation behind it — if something you need is missing, ask, and we will tell you where it sits.
Traceability 2
BioTrack
A dedicated integration package for BioTrack traceability workflows, kept separate from core domain logic so jurisdiction changes stay contained.
Menus & marketplaces 2
Weedmaps
Menu syndication from the same catalog and inventory position the register reads, so your listing does not advertise what you cannot sell.
iHeartJane
Marketplace menu publishing driven from the platform catalog, keeping external ordering surfaces aligned with live stock.
Payments & banking 1
Plaid
Bank account linking so settlement activity can be matched against recorded sales instead of reconciled by hand.
Hardware 3
Receipt & label printers
Printing is driven through a local hub service, which is why receipts and labels keep working when the connection does not.
ID scanners
Identity document scanning integrated directly into the checkout flow, with the verification result attached to the transaction.
Cash drawers & scanners
Standard retail peripherals paired locally to the terminal, so the counter hardware behaves the way staff expect it to.
Building your own
If you would rather integrate yourself.
Services are built against published API contracts with contract tests, and operational activity is emitted as durable events through a transactional outbox. You are not limited to what a dashboard chooses to show you.
Need something on this list that is not here?
Tell us which systems you already run. Integration scope is one of the first things we work out with a design partner.