CNBS — Product requirements

Problem

Cannabis dispensary operators stitch together a generic retail POS, a separate state-compliance portal, a spreadsheet for inventory, and an add-on loyalty product. Every shift produces reconciliation work, every audit produces risk, and every customer experience is gated by how well those tools agree.

Goal

Ship a single, cannabis-native operating system that owns the register, the inventory, the customer record, and the state-compliance hand-off in one flow.

Core capabilities (v1)

1. Point of sale
   • Age verification and ID scanning at the start of every basket
   • Per-customer daily purchase limit enforcement (state-aware)
   • Discounts, taxes, tips, split tender, refunds, voids
   • Receipts (email / print) and customer attach-to-basket
2. Inventory
   • Per-package records linked to METRC tag and lab COA
   • Receiving from manifest, transfers between locations, adjustments
   • Audit workflows with deltas, reasons, and operator attribution
3. Compliance
   • METRC sales, returns, and inventory adjustments written from the register flow
   • No separate end-of-day reconciliation step required
4. Customer
   • Unified customer record with compliance history and loyalty balance
   • Loyalty redemption at the register
   • Marketing exports filtered by compliance state
5. Operator console
   • Daily revenue, top SKUs, basket size, budtender performance, waste
   • Multi-store rollups for operators with more than one license

Non-goals (v1)

• Seed-to-sale cultivation / manufacturing workflows
• Delivery dispatch (out of scope for this release)
• Third-party menu marketplace listing management

Success criteria

• A budtender can run an end-to-end transaction (ID → age → basket → limits → tender → METRC write) faster than the dispensary's current stack
• A manager can close a day without opening the state compliance portal
• An auditor can trace any inventory variance to the exact package, manifest, and operator action