About CannAgent

Built for cannabis retail.
The whole shop, one system.

Built for the cannabis operator’s whole day — every register, the back office, the compliance gates, on one login. For operators who’d rather own the system than rent it.

Origin

Built because nothing else fit.

Cannabis retail is its own animal — cash-first, a state rulebook at every step, §280E hanging over the books. For years the tooling didn’t reflect that: a general-purpose register, then a stitch of that + a bolt-on POS + a third-party payroll vendor + a spreadsheet for vendor management. Each surface broke in a different specific place.

A cannabis-native build starts from the state’s ID and traceability rules and keeps them at the register, not three tickets deep in a help queue. The back office — hiring, write-ups, performance reviews, and payroll once it ships — belongs on the same system the bookkeeper already works in, not a separate tool reconciled by hand. Vendor ordering runs off live velocity, not PDFs. Compliance is code at the register, not a poster on the wall.

The team building CannAgent runs licensed cannabis retail itself, and the features that ship are the ones that broke on a real register first.

CannAgent puts register, inventory, compliance, and the books on one database instead of five vendors you reconcile by hand. It’s built ground-up for cannabis retail — state track-and-trace, §280E, cash discipline — not a general POS with cannabis bolted on. The platform is productized under Sureel Ventures LLC and offered to dispensary operators who’d rather own their system than file another support ticket.

The Team

The team behind CannAgent.

The CannAgent team

Built for cannabis retail

CannAgent is built for cannabis retail from the ground up — WAC 314-55 in the cart, cash-first at the till, §280E in the books. Cannabis rules are the foundation, not a module added later. CannAgent is built ground-up for the floor: register, compliance, books, and vendor management on one Postgres database, not five you reconcile by hand.

Why we built it

Three things a cannabis-native build does that a bolted-on POS can’t.

Cash-first by design

Cannabis retail clears in cash, and most dispensary software was built around a credit-card workflow the industry spent years waiting on. CannAgent is cash-first: manager-PIN gates, a till-variance ladder that escalates in three steps, from a note to a manager review to a camera pull, safe-drops and payouts as first-class workflows, and a closer who can finish a Friday night without texting the owner.

Native cannabis compliance

The state rulebook isn’t a config switch — it’s the rail the workflow runs on. Vertical-ID stops the cart at the register, not on a poster. Trade-sample units are counted against the per-employee quarterly cap in the cart, not on a clipboard. The waste form will not save without the name of a second employee who watched the destruction — that one is our workflow, not a PDF, and no section requires it. In Washington the age floor is WAC 314-55-079(1) and the trade-sample cap is -096(1)(j)(vi). Most systems tell you the rules; we run them.

Self-learning ordering

Reorder isn’t a vendor PDF you re-key. CannAgent drafts purchase orders against velocity, vendor reliability, and what each vendor actually delivered — the math runs off your real sales history, not a static days-of-supply formula. Change any quantity before you confirm the draft. Every vendor row carries its license number and expiry, so a lapsed supplier is flagged before you reorder from it.

See the full feature set

Verify our story

Every claim above is checkable on a public surface. Don’t take our word for it.

Live status

5-min probes

Per-target uptime visible.

Trust posture

Sub-processors, retention

Named vendors, data ownership, security status.

Common questions

What operators ask first.

Who owns our customer and transaction data?

You do. Always. Each location runs on its own Postgres database, exportable any time in standard SQL. No vendor-database lock-in. Your customer list is not aggregated, not resold, and not used to train any model — it sits in your database.

Does Anthropic see our customer data when the AI features run?

Only the minimum slice needed to draft the suggestion, and never your customer list. The reorder-queue explainer sees product SKUs and sell-through rates — not who bought them. The write-up drafter sees the incident facts and the relevant WA labor rule — not employee personal info. The scope generator sees what the prospect typed into the demo form — not your historical transaction set. Anthropic’s paid API tier doesn’t retain prompts for training — that’s their published commitment, not a handshake — and we don’t mirror prompts to any analytics tool. Patient PHI on the medical surface never crosses into AI calls. If your compliance team needs the per-feature data-scope written out, ask at the demo and we’ll send it.

Are you HIPAA-compliant if we sell to medical patients?

No — the platform is built to cannabis retail rules, but it is not a HIPAA-covered system. Medical-patient verification is built in as a staff check (patient ID and card checks, age-and-eligibility gating at the cart — the platform does not query any state patient registry) and that flow is handled under state cannabis rules — in Washington, WAC 314-55-080 (medical cannabis endorsement) and chapter 246-71 WAC (the medical cannabis authorization database, including its confidentiality rule at 246-71-100) — not 45 CFR 164. PHI in patient ID-checks doesn’t cross into our system as covered HIPAA data. If you operate a medical-only retail surface that requires a BAA, that’s a separate conversation — talk to us at the demo.

What about cannabis advertising rules — does the platform enforce them?

Partly — WAC 314-55-155 governs cannabis advertising in Washington, and CannAgent’s product and content pages are scoped to it; bulk SMS is not. The one operators most often miss is subsection (7): except for outdoor advertising, ALL advertising must carry four warning statements — intoxicating effects and habit forming; impairs concentration, coordination and judgment, do not drive or operate machinery; there may be health risks; and for adults 21 and older, keep out of reach of children — each at no less than 10% of the largest type in the advertisement. A text message is advertising and is not outdoor advertising, so all four apply, and they run 341 characters before your own copy begins. CannAgent’s product and content pages carry the (2)(c) 21+ statement and those four warnings. Bulk SMS does not add them: it goes only to opted-in customers, holds during quiet hours, and is capped at 160 characters, so adding the WAC 314-55-155(7) warnings to an advertising text is on you. The product helps the business; we don’t make claims about cannabis itself, and the templates we ship don’t either.

Why are some features marked PROPRIETARY on your site?

We describe the implementation in the demo, not on a marketing page competitors can scrape. The black bar is the implementation detail held for the call. If you book a demo, you see everything — the self-learning vendor reliability + auto-PO scaling, the training-completion gate at the POS, the variance escalation ladder with the offset-window camera-review trigger, and the jurisdiction-aware proportionate-response engine on manager write-ups. We’d rather show you on a working call than print it for the next vendor to copy.

See all questions

Ready when you are

See if it fits your shop.

30-minute demo. We walk the same three surfaces a working day touches: a register transaction with a vertical-ID gate, a manager write-up against the WA labor rubric, and a month-close from the back office.

Request a demo

Built for cannabis retail. The whole shop, one system.