Set the target. Hold the line.
Your POS records what sold. Canntrol runs everything else: the open, the floor, the order, the cash, the close, the owner’s review. Every store, one screen. Every sign-off signed by name.
The operating layer for cannabis retail. $100 per store per month, month to month. Built on Greenline, live. TechPOS, Cova and Dutchie next. Canada-first, for independent operators running 2 to 10 stores.
Your POS records what happened. Canntrol runs the store.
The POS stays the source of truth for sales and stock. Canntrol sits on top and runs what the POS does not. The daily rhythm. Cash. Ordering and receiving. Targets, training, safety and compliance. It reads POS data and never processes a transaction. If Canntrol is ever down, the POS keeps selling.
Built on Greenline, live
Connect the POS once. Map each POS location to a store. Switch syncing on per location.
Read-only, by design
Reads products and inventory. Never writes to the POS. Never touches a sale.
Canada-first
Most provinces route wholesale through one body, so list cost is known, not estimated. Price decreases flag before you order.
One screen, every store
Today leads with what is out of band across every store, ranked by dollar impact. One store and one action per row.
Open on what is out of band. Close on a locked count.
Features arrive in the order a store meets them. A manager opens Today before the doors open, reads last night’s handover and works one queue with the floor. Every dollar that moves is signed. Count each till once at close. The count locks.
Open
Today: a three-sentence read, then the exception list. The opening checklist, signed tick by tick. Last night’s handover in Manager Logs. A pinned Staff Note, marked seen by name.
Floor
One board per store: To do, In progress, Done. Customer requests in the Request Book. Anyone reports a repair or an incident. Urgent repairs and serious incidents reach managers at once.
Order and receive
The weekly order builds from POS reorder data and the provincial wholesaler’s order form, net of stock on the way. Send it for approval and the receiving list waits for landing day. New products get a label at receiving and a photo for the menu.
Cash
Mid-shift drops logged per till, same day. A bag sealed, picked up and bank-confirmed is three links, each signed and timestamped by name. Drops in equal bags out, to the cent.
Close
Count each till by denomination. Variance and drop compute themselves. Submit and it locks. Over the threshold? It flags itself and opens an investigation task. Reconcile the card terminal. Log the five-point lockup. Closing alone? Start a working-alone session.
The week’s review
One table replaces the weekly cash spreadsheet: close drops, mid-shift drops, deposits and variances. Chase anything red. Verify the week and it locks. Cash analytics find the same till short three nights running. Ownership reads every store from one place.
Seven areas. One bell.
The range, in the words operators already use. What you see is what you can act on. Staff see a shorter Today and only their own store. Managers run their stores. Ownership sees every store and the money.
Daily operations
Today · Tasks · Checklists · Calendar · Manager Logs · Staff Notes · SOP Library · Events · Alerts
Cash and finance
Till counts · Mid-shift drops · Deposits · Floats · Weekly summary · Cash analytics · Expenses · Invoices
Inventory and procurement
Inventory · Reorder suggestions · Transfers · Order form · Price changes · Receiving · Labels · Damages and returns · Product Photos
Sales, pricing and marketing
Targets · Competitor price log · Discount registry · Display campaigns · Marketing projects · Secret Shopper · Request Book
People and training
Courses and quizzes · Team progress · Employee files · Performance log · Review packet · Onboarding and offboarding · E-signatures
Safety and compliance
Working alone · Incident Reporting · Compliance checklists · Audit packet · Lockup log · Key custody · Maintenance and Repairs
System
Automatic alerts · Integrations · Setup · Team · Knowledge base · Help and search · In-app feedback queue
Every module writes to the same audit trail. Every alert lands in the same bell. Assignments, arrivals, approvals, alerts: one inbox, on the phone if you want it.
The parts that make money, not just save it.
Most of the platform stops leaks. These six push the top line. Each one is a real module, and each one carries its target and its band like everything else.
Targets on POS metrics
Set a target and a band on the POS sales numbers that move revenue, per store, per period. Drift shows amber before a month is lost.
Competitor price log
Managers log a nearby store's shelf price, with the date they read it. Ownership sees where you are priced out of the market and where you are leaving margin on the table.
Reorder suggestions and shelf coverage
The weekly order builds from POS velocity, net of stock on the way, and shows days of cover per slot before you send it.
Request Book
Every "do you carry" that you did not carry gets logged by the budtender who heard it. Demand you were turning away becomes a line on next week's order.
Display campaigns and marketing projects
Plan a campaign once, run it at every store with a checklist and a photo of the build. The board shows which store actually put it up.
Secret Shopper
Ownership scores a visit against the same sheet at every store. Results feed coaching, not gossip.
The money lines are arithmetic on the reader's own numbers, not results claims. Canntrol has no customer results to publish yet and will not invent any.
If the app refuses to let you change something, that is it working.
Six rules apply to every role, every store, every day. They are not settings.
Target. Actual. Band.
Ownership sets a target and a band per metric, per store or company-wide, per day, week or month. Inside the band reads teal. Drifting reads amber. Past the edge reads red and lands on Today. Bands know which side is good: under a spend target is a win, not an exception.
The setpoint. If a metric has no target, the screen asks you to set one.
The reading against the target, for the store and the period the target was set on.
The acceptable range around the target. Inside reads teal.
Movement toward the edge. Amber. No alert yet; a manager sees it before the doors open.
Past the edge. Red. Surfaces on Today with a store, a dollar impact and one action.
A new entry with a reason, beside the original. Never an edit.
Nothing out of band. Targets held, cash confirmed, queue clear.
Required courses assign themselves. A completion is signed by someone who is not the learner.
Mark a course required for a role and it assigns itself to every current and future person in that role. Quizzes score, retakes are unlimited, and a completion means nothing until a manager signs it. Then it is permanent: a compliance record, not a checkbox.
My training
Assigned courses, lessons in order, then a quiz or an acknowledge step. Progress, due dates and scores on one list.
Team progress
Every assignment at your stores: person, course, due date, status, score. Assign courses and sign off completions.
Read and sign
Publish a new version of a procedure and the signature sheet reopens. Old signatures stay on record and cover nothing new.
Employee files
One file per person: documents by type, certifications with expiry. Expiring warns ahead. Lapsed reads red. Offboarding starts itself the day someone leaves.
One month, eight scenes.
One month at a fictional three-store operator on Greenline. One owner, three store managers and an assistant manager who sometimes closes alone. The people, figures and timings are invented for illustration. The features and the rules are the real ones.
ST-02
She submits and locks the count anyway. The flag alerts ownership and opens an investigation task on the ST-02 board, carrying the count, the counter and the math. Next morning she recounts the drop bag. The slip was misread. She files a correction with the reason.
The original stays visible, marked Superseded, and drops out of the week’s totals. The task closes with the reason on record. A record, not an accusation.
ST-03
She taps Assign. The ST-03 manager has a task due today in her bell before the store opens.
Bank deposit confirmed at 11:20 with the slip photo. Slip matches bag. The third link is signed and the row leaves Today.
ST-01
He ticks one candidate line for the gap and leaves the price-drop line unticked. A pre-roll that ST-02 has sat on comes over as a transfer instead of an order. He sends it for approval.
The slot reads 12 days of cover. The order lands inside the weekly budget and the receiving list is saved for landing week.
ST-03
The store’s managers are told to check the cameras or call. The store manager calls. He taps I’m OK on the next screen and finishes the close.
One missed check-in and one alert, both on the permanent record. The session ends at shift over.
All stores
Everyone gets a bell to sign again. By Friday the sheet reads 20 of 22. Two names sit on the not-yet list, and the ST-01 manager catches them on shift.
22 of 22 signed on v2 by Monday. The v1 signatures stay on record and cover nothing new.
ST-02
She submits with 4 of 5 and a note. Management and ownership are alerted at once. In the morning she reports an urgent repair against the registered camera system. The service contact is one tap.
Fixed by 15:00. The service entry writes itself onto the asset’s history and the cost joins repair spend on Targets.
ST-02
She opens the row. The camera call-out is the reason. Nothing to correct yet, so she holds the target and notes it for the monthly review.
Inside the band, drifting toward the edge. One more repair this month and the row turns red.
ST-01
He reads the week’s table, chases nothing, and taps Verify this week as himself.
The week archives as a permanent signed record. No count can be added to it. The owner reviews the archived week, then opens Today.
Nothing out of band. Targets held, cash confirmed, queue clear.
The owner has not driven to a store all month. Every event above is now a row with a name, a time and a reason. Nothing was emailed. Nothing was retyped. Each store’s audit packet for the month exports as one PDF.
One number.
Every module, every role, every store, one price. No tiers to grow out of and no per-user fees, so the whole floor crew is on it, which is the point.
Per store
A store is a location with tills. Two stores, $200 a month. Five stores, $500.
Per month
Billed monthly, in Canadian dollars, plus tax. The first month starts when your first store goes live, not when you sign.
Pilot
One store, one week, on the real system. If it does not earn its place, you have paid for one store for one month.
POS
Greenline today. TechPOS, Cova and Dutchie next. The price does not change with the POS.
Your numbers, your math.
Change any figure. The result is arithmetic on what you typed, not a claim about what Canntrol will do. Defaults are placeholders, not averages.
Hours × 4.33 weeks × rate, plus variance, across your stores. Canntrol is $100 per store. Nothing here is stored or sent.
Your data stays yours.
Operators are asked to pipe cost, margin and pricing into a platform. The answer to “who can see this” is short. Access is enforced in the data itself, not by hiding buttons.
- Your own database, your own deployment.Each customer runs in their own isolated database and deployment, with scheduled backups of their own.
- No benchmarks, no pooled comparisons.No cross-customer aggregation of any kind. No “how you compare to other stores.” Competitor prices come only from public menus, with the date they were read.
- Every figure carries its source.A label sits under any figure whose origin could be questioned. It answers “where did you get that?” before anyone asks.
- Every action logged. Records that lock.Who, what, when, which store, before and after. Cash counts, deposits, compliance and training sign-offs cannot be edited once submitted. A correction sits beside the original.
In plain words.
The short version of both. Ask for the long version before you sign and you get it in writing. Nothing below changes without notice to you.
Privacy
- What Canntrol holds
- The POS data you connect, the records your team enters, and what you type into the access form on this page.
- Where it lives
- In your own database and your own deployment. The hosting region is chosen with you at setup and written into your agreement.
- Who can see it
- Your team, by role. Canntrol staff only for support you have asked for, and only while you have asked for it. Nobody else.
- What Canntrol never does
- Sell it. Pool it. Benchmark you against other customers. Read it for any purpose other than running your stores.
- When you leave
- You export everything. Your deployment is deleted after a written confirmation from you, on a date you set.
Terms
- Price
- $100 per store per month, in Canadian dollars, plus tax, billed monthly from the day your first store goes live.
- Term
- Month to month. Cancel by email at any time. The current month is the last one billed.
- Your POS
- Canntrol reads from it and never writes to it. If Canntrol is down, your POS keeps selling.
- Your records
- Locked records stay locked. Corrections sit beside originals. The audit trail is yours and exports with everything else.
- Support
- Email, replied to within one business day. Outages are posted to you directly, with what broke and what changed.
Before you ask.
The questions every owner asks in the first call, answered the same way here.
What do you need from me to start?
How long until it is running?
Which POS do you support?
Is this a POS? Does it touch my sales?
Can my staff see cash or another store?
Do you compare me with other operators?
What happens if I leave?
Can I bring my history?
Run one store on it for a week.
A pilot starts with Setup: company identity, stores, tills, invite the team. One store runs its full day in the first week, opening checklist to lockup log, with nothing on paper. Ask for the demo first: a fictional store after a month on the job, every module with history.
Canada-first. Independent operators running 2 to 10 stores. Prefer email? Write to hello@canntrol.com.