Dispensary POS Offline Mode: What Happens When It Goes Down

What happens when your dispensary POS goes down?

If your point of sale has a true offline mode, sales keep running on the terminal, transactions are stored locally, and everything syncs to your state track-and-trace system once the connection returns. If it does not, the register stops. The sales you take on paper in the meantime are not reported, purchase limits are not enforced, and you have created a compliance problem rather than just a bad afternoon.

Last updated August 2026. General information for licensed US operators, not legal advice. Track-and-trace reporting deadlines are set by your state, not by your software vendor, and they vary. Confirm your own rules with your regulator.

Offline mode is three separate questions, and vendors usually answer one

Ask a POS vendor whether they have offline mode and you will almost always get a yes. The word covers at least three distinct capabilities, and a platform can genuinely have the first while quietly lacking the other two. Getting a yes to the question you did not ask is how shops end up surprised at 4pm on a Saturday.

Can you keep taking money? This is the one everybody demos. The terminal holds the catalog and prices locally, rings a sale, prints a receipt and queues the transaction. It is real and it is worth having, but it is the easiest of the three to build and the least interesting from a compliance standpoint.

Can you keep enforcing the rules? This is the one that matters and the one people forget to ask about. A cannabis sale is gated on things the terminal may not know while it is offline: how much this customer has already bought today, at another register or earlier in the week, and whether that puts them over a daily weight limit or a possession cap. IndicaOnline, writing about exactly this scenario, flags customer purchase limits, product equivalencies and daily weight limits as the violations that surface when a POS loses its connection. Exceeding a daily weight limit is not a paperwork error. It is the kind of thing that draws a real penalty.

Can you reconcile cleanly afterwards? Storing transactions is not the same as reconciling them. When the connection returns, the queued sales have to post to your state system in the right order, against the right package tags, without double-counting anything a staff member also entered by hand during the outage. Ask to see what the sync log looks like and what happens to a transaction that fails to post.

The deadline that bites is set by your state, not by your POS

This is the part almost every vendor article skips, and it is the single most useful thing to understand. Metrc runs an open API that more than 500 software providers integrate with, and each transaction at the register updates your Metrc inventory records through that connection. But Metrc is the pipe, not the rulebook. It does not set the deadline by which your sales have to arrive.

Your state does, and states configure it differently. California operates on a 24-hour reporting window, and reporting on the wrong side of it is treated seriously enough that a manifest submitted an hour late can trigger the same escalation path as a deliberate diversion. Mississippi requires dispensing information to be reported every 24 hours to its prescription monitoring program. Other Metrc states set their own timing. The practical implication is that your tolerance for an outage is not a technical number your vendor can quote you, it is a regulatory one you have to look up.

So the question to answer before you need the answer is this: how many hours can my shop be disconnected before I am late under my own state's rule, and what is the manual process for getting those sales in on time if the integration is still down when the clock runs out? Write it down. An outage is a bad time to be reading regulations.

What actually breaks, and what keeps working

The column on the right is the one worth staring at. Offline mode is designed for the failure on the left, your own connection dropping. It does very little for you when the failure is upstream at the vendor.

The outage you did not cause

Cannabis retail learned this distinction the hard way. On 4/20, the single biggest sales day of the year, MJBizDaily reported cascading ecommerce failures across Dutchie's platform, with chief executive Tim Barash subsequently promising payouts to affected retailers. No amount of in-store offline capability protects you from that, because the thing that failed was not in your store.

Vendors know reliability sells, and they market it. Cova, which competes directly with Flowhub and therefore has an obvious interest in the framing, claims eight years of perfect uptime including on peak holidays, and points to its offline mode. Take the specific claim with the appropriate salt and take the underlying point seriously: uptime is a purchasing criterion in this category in a way it is not in general retail, because your busiest days are known in advance and shared industry-wide.

Two practical defenses. First, ask any vendor you are evaluating for their uptime history on 4/20 and Green Wednesday specifically, not their annual average, because an annual average hides exactly the hours you care about. Second, know when you are down. Most operators find out their online menu has stopped loading because a customer mentions it, which means the revenue was already lost. Pointing something that checks the page every thirty seconds and texts you when it stops responding at your menu and your ordering flow costs almost nothing and turns a two-hour silent outage into a two-minute one.

Does a dispensary POS work without internet?

Some do and some do not, and it is a genuine differentiator rather than a given. Cloud-native platforms vary widely in how much they can do disconnected, because everything the terminal needs has to have been cached locally in advance. A system that stores the catalog, prices, tax rules and recent customer purchase history on the device can keep selling. One that queries the server for each of those cannot.

The connection quality question sits underneath this and gets ignored. Cultivera's own setup documentation stresses stable wifi dedicated to shop devices, which is a polite way of saying that a lot of reported POS instability is actually a store network shared with a guest hotspot and a security camera system. Before you blame a platform, find out whether your registers are on their own network segment. It is the cheapest reliability fix available to you.

What to ask a POS vendor before you sign

• In offline mode, can the register still enforce daily purchase and weight limits using data from other registers and from earlier in the week, or only from this terminal?
• How long can we operate offline before the local queue fills or the session expires?
• When the connection returns, what does the sync produce, and how are failed or duplicate transactions surfaced to us?
• If your platform goes down rather than our internet, what still works in the store?
• What was your uptime on 4/20 and Green Wednesday for the last two years, by hour?
• What is your credit or service-level commitment when an outage costs us a sales day?
• Does our online menu stay up and keep accepting orders while the in-store system is offline, and where do those orders land?

That last one catches people. A shop can be selling perfectly well in person on offline mode while its ecommerce queue silently discards orders, and the first sign is a run of one-star reviews about unanswered pickup orders the following week.

Where this sits in the buying decision

Offline behavior is rarely on anybody's shortlist criteria and it should be, because it is one of the few POS attributes you cannot fix later with a workaround or a bolt-on. If you are still narrowing the field, our comparison of cannabis dispensary POS systems and what each one reportedly costs lays out the main platforms US operators shortlist, and the pricing pages are worth reading alongside it: what Flowhub reportedly costs per month and what Dutchie reportedly costs both cover quote-based vendors where the published figures disagree with each other.

If reliability is what is pushing you to look elsewhere, that is a common enough reason that we wrote up the main Dutchie alternatives and why operators switch, and the mechanics of moving without breaking your compliance history are in our guide to how to switch dispensary POS systems. One related thing worth checking while you are at it: your payment rails are a separate dependency with their own failure modes, covered in cannabis payment processing and what rescheduling did not change.

The short version

Assume you will lose connectivity at some point, on a day you cannot afford it. Ask about limit enforcement rather than just about selling, look up your state's reporting deadline before you need it, keep a written paper-sale procedure that includes how those sales get entered afterwards, put your registers on their own network, and monitor your own menu so you learn about an outage from software rather than from a customer. None of that is expensive. All of it is much cheaper than a weight-limit violation.