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. This guide is our honest take on what to look for in the six states where we see the most buying activity. We are not going to rank vendors or pretend that one system rules them all. Instead, we are going to give you the regulatory context that most sales demos skip, so you can ask questions that actually matter during your evaluation.
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 — DCC, MED, OCM, LCB — 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. California also has some of the strictest product testing requirements in the country. Every batch must be tested for potency, contaminants, and terpenes, and the results must be linked to the METRC package tag before the product can be sold. Your POS should be able to scan a package tag and immediately surface the associated lab certificate. If the certificate is expired or the batch failed a test, the POS should block the sale. We have seen operators get fined because their POS allowed a sale of a failed batch that was still visible in inventory.
California also has strict product labeling rules that flow into receipt formatting. Your POS should print compliant labels and receipts without manual workarounds. We see operators waste hours every week on label formatting because their POS treats California like a generic METRC state.
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. The MED does not accept "other" as a reason code for recurring adjustments. If your inventory shrinkage is consistently coded as "other," you will get flagged for a deeper inspection. A good Colorado POS enforces reason-code selection at the point of adjustment and prevents generic catch-all codes from being overused.
When you demo a POS in Colorado, ask the vendor to show you the inventory adjustment log. If it does not export a MED-ready CSV with reason codes and user IDs, you will be building spreadsheets during your first inspection. We built DubLedger's Colorado module specifically around MED audit readiness because we have watched operators fail inspections over missing reason codes.
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: cultivators, processors, and dispensaries must be under common ownership. This changes how inventory moves through your system. In most states, a dispensary buys wholesale from a separate cultivator. In Florida, the dispensary is often receiving product from its own cultivation facility. The transfer rules, the tax treatment, and the reporting cadence are all different. Your POS must handle intra-company transfers with different documentation than arm's-length purchases.
If you are in Florida, you need a POS with a direct BioTrack integration, not a promise that it is "coming soon." You also need inventory tracking that handles vertical-integration transfers between your own facilities, because those transfers have different reporting rules than arm's-length wholesale transactions.
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 — if your POS batches sales reports hourly, you may fall out of compliance. The LCB also requires strict chain-of-custody documentation for every gram of product. From the moment a plant is harvested to the moment a customer walks out the door, every handoff must be recorded. Your POS should generate the required LCB reports automatically, not as an afterthought export. Ask the vendor to show you the Washington-specific compliance dashboard during the demo.
Washington also has unique tax rules. The LCB requires excise tax to be calculated and reported at the point of sale, not at the end of the day. Your POS must apply the correct tax rate by product category and jurisdiction, then push the taxed amount to Leaf Data in the same transaction payload.
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. New York also has one of the most complex delivery frameworks in the country. Delivery drivers must follow pre-approved routes, and the POS must generate route manifests that include estimated arrival times, vehicle information, and real-time GPS tracking integration. If the driver deviates from the route, the dispensary must document the reason. This is not a feature most generic POS systems have built in.
If you are opening in New York, the most important question is not whether the POS supports METRC — every vendor will say yes. The question is whether the POS supports OCM-specific fields and reporting cadences. Ask for a demo of the New York compliance module, not just the generic METRC sync screen.
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. Your POS must have a local cache of verified patient statuses and a fallback workflow that prevents sales when the registry is unreachable. We have seen operators get fined because their POS allowed a customer to exceed the limit on a busy Friday night when the registry lookup timed out. A robust Illinois POS handles registry failures gracefully instead of failing open.
Your POS must check purchase limits in real time against the state registry and the customer's rolling 30-day history. METRC does not enforce these limits — it is your responsibility. We have seen operators in Illinois get fined because their POS allowed a customer to exceed the limit on a busy Friday night when the registry lookup timed out.
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. If a vendor cannot name the regulatory body in your state without checking notes, they have not done the work. If they cannot show you a state-specific demo with real compliance fields populated, they are selling you a generic product with a cannabis skin. Demand better. Your license depends on it.