We pulled feature data from public docs, operator forums, and our own due diligence. Where we couldn’t verify, we say so. Where we don’t have something, we say so too. 50 features, 8 categories, 8 vendors.
Each tile carries the platform’s positioning, who serves them well in operator practice, and a one-line “best for” recommendation. Sometimes the right answer isn’t us — we say so.
The dispensary OS that runs the dispensary, not just the register. Built by operators on it.
$240–600 / store / mo
Month-to-month. No multi-year. · No per-transaction fee
1–15 store owner-operators in WA today (other states during onboarding) who’d rather own the system than rent it, and who want WSLCB-fluent compliance + payroll + self-learning ordering in one login.
The largest cannabis-vertical POS + e-commerce platform — multi-state, marketplace-rooted.
$500–1,500 / location / mo
Annual minimum, multi-year common · ~2.0–2.9% of card volume on Dutchie Pay / payments add-on (operator-reported)
Multi-state chains who already lean on the Dutchie consumer marketplace for distribution and accept the per-transaction-fee math as a marketing-cost line item.
Vertically integrated cannabis ERP — POS, inventory, e-commerce, and compliance for mid-market chains.
$600–1,800 / location / mo
Annual minimum, often multi-year · No per-transaction fee
Multi-license California chains running cultivation + retail under one roof who need the ERP-grade reporting and aren’t price-sensitive.
Cannabis retail POS with mobile checkout, inventory, and METRC integration.
$400–900 / location / mo
Annual minimum · No per-transaction fee
1–3 store operators in Colorado or Michigan who want the Maui mobile checkout, accept a dated UI as the trade, and don’t need a unified back office.
Budget-tier cannabis POS — Cova acquired Greenbits in 2024, the two stacks now operate under the Cova umbrella.
$300–700 / location / mo
Annual minimum, month-to-month available with markup · No per-transaction fee
Single-location operators on a budget who need a POS that takes the cash and reports to the state, and who accept manual back-office workflows as the trade for entry-tier pricing.
Cannabis ERP across cultivation, distribution, and retail — California-rooted, multi-state present.
$500–1,500 / location / mo
Annual minimum · No per-transaction fee
Vertically integrated California operators (cultivation + distro + retail) who want one ERP across the supply chain and have the ops maturity to run it.
California-native cannabis POS + delivery dispatch + e-commerce in one platform.
$400–1,000 / location / mo
Annual minimum, month-to-month available · Variable on payments / delivery routing add-ons (operator-reported)
California single-shop and small-chain operators where delivery is 30%+ of revenue and a native dispatch surface is the wedge.
Generic retail POS with a cannabis-certification vertical — POS-first, cannabis-overlay second.
$50–300 / location / mo (POS license)
Month-to-month · Payment-processing fees pass through (varies by processor)
Single-shop operators in low-compliance-load markets on a tight budget who accept manual state reporting + manual compliance gating as the trade for lowest TCO.
Where we’re strongest: WSLCB-coded compliance, payroll, AI reorder + write-up, cash discipline. Where we’re honest: no native delivery dispatch (Meadow has it). The honesty is the conversion driver.
Native age verification
Industry-discount 90d re-verify (WAC 314-55-095)
Manager-PIN gates on void / return / discount override
Customer display (2nd-screen)
Cash-first checkout flow
Soft-confirm on $200+ / 7+ item carts
Mobile / handheld checkout
Returns + voids with cannabis-quarantine routing
Pricing ranges are operator-reported, triangulated from r/Dispensary threads (2023–2026), MJBiz Daily coverage, Cannabis Business Times implementation-timeline threads, Ganjapreneur vendor-comparison articles, and vendor public marketing pages. We deliberately publish ranges rather than point figures — vendor pricing varies by location count, contract length, and discount cycle.
Feature ratings cite the platform’s public documentation where available and operator-reported behavior where it isn’t. “Partial” means the capability is present but limited or operator- managed; “Add-on” means it’s a separately-billed module; “Manual” means it’s possible by hand but not enforced.
For CannAgent, every ✓ ships in production today on the two stores Doug runs. Every ✕ is a feature we don’t have — said directly because the honesty is the credibility move.
Found something wrong, missing, or out of date? Email doug@cannagent.ai — we update the page.
The matrix is the briefing. The demo is the test. We walk three real surfaces — the register, the manager write-up, the Form 941 from the back office — and end by quoting your cutover.