PlatformPOS & Checkout
Cash-first register, vertical-ID gated at the cart.
What it does
Cash-first checkout, vertical-ID gated at the cart, manager-PIN where it counts.
Every drawer counted, every drop logged, every variance escalated on a ladder.
See it
The question every operator asks before switching: what happens to my store if your system has an issue? Written plainly, no bravado.
Per-store database
Your Postgres is yours alone — not multi-tenant. An issue on another customer’s data never reaches yours.
Offline cache at the register
The register keeps the last-known cart state, so an in-flight transaction completes even if the connection blips.
You hear it from us first
Your admin contacts get an email from us the moment we detect a critical-path issue, backed by the live 5-minute probe rollup on /status and a written postmortem — not a status-page color you have to refresh. SMS escalation is in build; we’ll say so here the day it ships.
If you want CannAgent to be your register, talk to us first: we’ll tell you what’s ready in your state before you plan a switch. The switching fear is real: loyalty balances vanishing and day-one numbers that don’t tie out. The cutover workspace, coming soon, answers both — a readiness board, a loyalty-balance snapshot taken before the flip, and a reconciliation dry-run that proves the numbers match before you commit. You move in phases — shadow first, then flip — not all at once on a Friday.
Try it
Change the product, the city, the card. The paper receipt is what your customer takes home. The CCRS panel with it is the row that goes to the state — the same fields, built by the same code. Set the customer under 21 and watch what happens to both.
Total $53.13. Files as RecreationalRetail.
Computed by src/lib/receipt-demo.ts, which emits the same CcrsSaleRow the WSLCB submission is built from and is pinned against the real CCRS validator in CI. Statutory rates shown; a live store computes from its own configured local tables.