We talk to dispensary operators every week who are trying to pick a POS, and the first question we ask is: what state are you in? The answer matters more than feature checklists. A POS that crushes it in Oregon can be unusable in Florida because the compliance backend, the reporting cadence, and even the unit-of-measure rules are different.
The state filter: why it dominates the decision
Cannabis POS vendors build for the biggest markets first. That means California, Colorado, and Michigan get the most mature integrations, while newer markets like New York get early, sometimes buggy, support. The regulatory body in your state sets the rules that the POS must follow. If the vendor has not spent real engineering time in your state, you will be the beta tester.
California: METRC plus DCC reporting
California is the largest cannabis market in the world by revenue. The Department of Cannabis Control (DCC) requires METRC integration for all licensees, plus quarterly tax reporting through the CDTFA portal. Any POS you evaluate must support: daily METRC sales sync, package-level inventory tracking, and delivery manifest creation with real-time driver assignment.
Colorado: METRC plus MED audit logs
Colorado was the first recreational state, and the Marijuana Enforcement Division (MED) has the most mature inspection program in the country. Colorado METRC integration is table stakes, but the real test is the MED's audit-log requirements. Every inventory adjustment must include a reason code, a timestamp, and the user who made the change.
Florida: BioTrack vertical integration
Florida does not use METRC. It uses BioTrack, a traceability system operated by Akern. BioTrack's API is SOAP-based, not REST, which means many modern POS vendors either do not support it or outsource the integration to a middleware partner. Florida also requires vertical integration for medical operators.
Washington: Leaf Data Systems
Washington State uses Leaf Data Systems, not METRC. Leaf Data has a REST API, but the data model is different: Washington tracks every plant and product with a unique identifier, and the Liquor and Cannabis Board (LCB) requires sales data to be reported in near real time. Latency matters here.
New York: METRC plus OCM rules
New York is transitioning to METRC under the Office of Cannabis Management (OCM). The OCM has added fields for social-equity tracking, delivery-route planning, and conditional adult-use retail licenses that are not part of the standard METRC spec.
Illinois: METRC plus CRTA limits
Illinois uses METRC, but the Cannabis Regulation and Taxation Act (CRTA) imposes strict purchase limits: non-residents can buy half the amount of residents, and medical patients have separate, higher limits tracked by the state's medical registry. The registry lookup is not instant. On a busy Friday night, the state API can time out or return stale data.
How to filter the field
- Ask for the vendor's state-specific compliance checklist, not a generic features list.
- Request a demo with your actual license type and state rules, not a generic sandbox.
- Check whether the vendor has in-state support or relies on a third-party integrator.
- Ask how the POS handles API outages from the state traceability system.
- Verify that purchase-limit logic is enforced locally, not just passed to the state API.
No POS is best for every state. The right choice is the one that has spent real engineering hours in your market, understands your regulator's edge cases, and gives you direct access to the people who built the integration.