Buyer scorecard
Picking a cannabis POS: the 7-question scorecard
Every cannabis-POS sales call sounds the same — same buzzwords, same enterprise-grade everything. The questions below cut through that. Ask each vendor the same seven and score the answers. The one who can answer all seven without hedging is the one that actually ships.
How to use this
Don't read this once and forget. Print it. Bring it to every demo. Score each vendor 0-2 on each question (0 = couldn't answer, 1 = answered with caveats, 2 = clean answer with proof). Top score is 14. Anyone under 10 is a maybe at best — under 7 is a no.
1. How deep does your compliance code go?
Every POS says 'WSLCB-compliant' (or MED, DCC, CRA, OLCC, depending on your state). The question is whether compliance is built into the platform or handed back to you to enforce manually.
- 0 points: 'Our customers handle compliance themselves.' That's your job, not the platform's.
- 1 point: Documentation + reports — the rules are listed somewhere, you're responsible for following them.
- 2 points: Coded gates that refuse the action. Sale to minor at 9pm? The register won't process it. Manager override? Logged with reason + audit row.
2. What's your contract length and exit cost?
Multi-year contracts and exit fees are how legacy cannabis POS keeps customers who would otherwise leave. The platform should earn its keep monthly — your data should leave with you.
- 0 points: Multi-year minimum, exit fees, data-export fees.
- 1 point: Annual minimum, free data export, no exit fee.
- 2 points: Month-to-month, full SQL or CSV export anytime, no exit fee, no penalty.
3. Who owns the hardware?
Some POS vendors lease hardware with the software bundle. The number reads cheaper but the math gets uglier when you renew or want to leave. A few vendors lock the hardware to their cloud — your printer stops working the day you cancel.
- 0 points: Vendor-locked hardware, can't run without their cloud.
- 1 point: Vendor-leased but commodity (any printer/scanner works).
- 2 points: Operator-owned commodity hardware. Software runs on standard iPad / Windows / Linux register. You buy hardware once at retail.
4. Does payroll live in the same database as the till?
Most cannabis-POS treats payroll as a third-party integration — your hours come out of the POS but you still pay Gusto / Comploy / a separate provider for the actual filings. That's two vendors, two bills, two places where data drift starts.
- 0 points: No payroll. Hours export to a separate system you manage.
- 1 point: Payroll integration with a third-party provider. Hours sync but filings live elsewhere.
- 2 points: Form 941, W-2 batch, W-3, 940 FUTA, state-specific filings (WA L&I + PFML + SUI / OR similar / CA EDD) all generated from the same database as the till. No re-keying.
5. Can you walk me through your dogfood?
The fastest signal of platform quality: do the people who built it actually use it? Does anyone at the company run a dispensary on this code? If yes, ask them to walk a real Monday morning — opening till, first transaction, customer lookup. Watch for hesitation.
- 0 points: 'We don't operate stores ourselves.'
- 1 point: 'A few of our staff have worked at dispensaries.' Past-tense.
- 2 points: 'Our founder owns and operates [N] dispensaries on this code right now.' Present-tense + verifiable license numbers.
6. What's your status-page history?
Cannabis POS outages happen. They cost real revenue every minute. The question isn't whether the vendor will have an outage — it's whether they tell you about it before you find out from a customer in line.
- 0 points: No status page. No published incident history.
- 1 point: Status page exists but updates are vendor-discretion (they post when they feel like it).
- 2 points: Public incident history, postmortems for every SEV-1 / SEV-2, status page tracks the actual surfaces (POS / inventory / payroll / payments) — not just 'all systems operational.'
7. Cutover plan — by week, with names
If a vendor can't tell you what week 1 looks like, they don't know how to migrate you. The good answer is a written plan with named owners and defined hand-offs. The bad answer is 'we'll figure it out together once you sign.'
- 0 points: 'We'll work that out after contract.'
- 1 point: Generic timeline (4-8 weeks) with vague phases.
- 2 points: Week-by-week plan, named owner per surface, fixed-scope quote written ON the demo call. Cutover date that respects your busiest day.
Score sheet
| Question | Vendor A | Vendor B | Vendor C |
|---|---|---|---|
| 1. Compliance depth | _/2 | _/2 | _/2 |
| 2. Contract + exit | _/2 | _/2 | _/2 |
| 3. Hardware ownership | _/2 | _/2 | _/2 |
| 4. Payroll integration | _/2 | _/2 | _/2 |
| 5. Dogfood | _/2 | _/2 | _/2 |
| 6. Status-page history | _/2 | _/2 | _/2 |
| 7. Cutover plan | _/2 | _/2 | _/2 |
| Total | _/14 | _/14 | _/14 |
If no vendor scored above 10, the right move is to wait. The cost of switching POS twice is higher than the cost of running on what you have for another quarter while a 10+ option emerges.
Takeaways
- Score every vendor 0-2 on the same 7 questions — vibe-check loses to a written rubric
- WSLCB / MED / DCC compliance is either coded into gates or handed back to you — there's no middle
- Month-to-month + free data export is the cleanest contract shape; multi-year + exit fees is how legacy POS retains operators
- Dogfooding (founder runs stores on this code) catches bugs vendors never hit — ask for the license number
- If no vendor scored 10+, wait a quarter — the cost of switching twice exceeds the cost of running on what you have
Ready to talk through your migration?
30-minute demo. We end by quoting the cutover from your current setup — fixed scope, no hourly games.