See the real product. 30 minutes. No commitment.

A typical switch takes about four weeks; your dates are set in a written scope, because it depends on how clean the data in your current system is and on what is ready in your state. The cutover itself is planned overnight — last close on the old system Saturday night, first open on CannAgent Sunday morning. The ramp before that is data audit, hardware swap, and three days of on-floor support during the first week. Multi-location chains stage cutovers one store at a time; we don’t flip ten registers at once. The shape is the same whichever system you are coming off — what changes is how much of your history your outgoing vendor lets you export, which is the first thing we check.

METRC continuity is scoped per state during onboarding. The manifest and transfer mapping is built and tested; the live feed connects per store as each operator’s METRC credentials clear — so METRC states (CO, MI, OK, MA, MO, NV, OR, NJ, IL and more) are in build today, not live. Washington runs its own system instead, CCRS, and we build that file natively. BioTrack states — CT, NM, DE — are regulatory coverage right now, not a connected feed. Some states are first-class, others need custom integration work quoted separately, and we tell you which bucket your state lands in before you sign anything.

Hybrid. Every page in the back office has an in-app help panel — 150-plus surfaces — so a new manager solves their question without texting the owner at 11pm. The training portal ships with role-tracks for budtenders, leads, inventory, purchasing, and admin. On top of that, every cutover includes a 30-minute operator-team onboarding call and three days of on-floor support during the switch. We don’t bill for training the people who run the store.

Most budtenders are comfortable on the register inside one or two shifts — the cart flow looks like the cart flow on every other cannabis POS, with the vertical-ID gate and the till-variance ladder as the noticeable adds. Inventory leads take a week or two to absorb the cycle-count, waste-log, and self-learning ordering surfaces. Owners get the back office (payroll, write-ups, performance reviews) as a sequence — we don’t hand you eleven new modules on day one.

Each location runs on its own Postgres database hosted on Neon, with the application served from Vercel’s edge. The register has an offline cache for the last-known cart state, so an in-flight transaction completes even if the connection blips. A full regional outage on either provider would degrade the back office (analytics, reorder queue) before the register; we’ve held that as the design boundary from the start, because the register is the one surface a sale can’t wait on.