Offline POS: Keep Selling When the Internet Drops
Why a dropped connection kills the checkout queue, how a PWA-based POS works offline with automatic sync, and what to ask a vendor before you buy.
Picture the rush at your checkout. The queue is long, customers have cash or a phone ready to pay — and then the internet drops. A purely “online” POS app stops dead: no new transactions, no receipts, no payments. The queue jams, customers walk, and revenue disappears in the most valuable seconds of the day.
The truth is that on-site internet is never 100% stable. WiFi hiccups, data runs out, the provider has an outage, or the location simply has weak signal. The real question isn’t whether your connection will drop — it’s whether your cashier can keep selling when it does.
Why a dropped connection kills the queue
The checkout is the one point in a business that must never stop. When a POS dies because of the connection, the queue jams instantly, and every second of waiting feels long to someone standing there with money in hand. In F&B and retail, customers who wait too long often just abandon the purchase.
The damage continues after the outage, too. Anything scribbled on paper has to be re-keyed later — error-prone, easy to forget, and stock goes out of sync. And there’s a cost no report captures: “their system errors out a lot” is an expensive reputation to shake.
The problem is that many POS apps require a live connection for every transaction because everything is processed on the server. The moment the connection drops, there’s no backup plan.
How a PWA POS works offline
A modern POS built as a PWA (Progressive Web App) solves this by keeping core capability on the checkout device itself. The app runs in the browser, but once opened, its assets and the data it needs (product catalog, prices) are stored locally — no app-store install required.
While online, transactions sync straight to the server as usual. When the internet drops, the cashier keeps ringing up sales; each transaction goes into a local queue on the device, the customer is served, the receipt is recorded. Once the connection returns, that queue syncs to the server automatically, one by one, with no re-keying.
Most important: this sync must have a double-transaction guard. Without it, a transaction that was partially sent could be sent twice as the connection flaps up and down — and your sales figures get scrambled. A well-designed POS gives each transaction a unique marker, so the server rejects duplicates: one transaction stays one, no matter how many times the connection cut out midway.
What works and what doesn’t while offline
It’s important to set honest expectations. When truly offline, the cashier can still create transactions, take cash or card (EDC) payments, record items and quantities, print or save receipts, and queue everything up to sync later.
What genuinely needs a connection is dynamic QRIS — the “paid” confirmation comes from the payment gateway over the internet, not from your device. A good POS automatically falls back to cash/EDC while offline, then re-enables QRIS once online. The queue keeps moving; you just switch payment method temporarily.
So “offline” doesn’t mean every online feature is available without internet. What’s required is that core transactions don’t stop and no data is lost.
What to ask a vendor
Every vendor demo happens on smooth office WiFi. So make them walk through the bad day, and ask these specifically:
- “If the internet drops mid-queue, can the cashier still transact?” The right answer: yes, transactions go into a local queue and sync automatically when online.
- “How do you prevent double transactions when the connection flaps?” The vendor should be able to explain an anti-duplicate mechanism (a unique marker per transaction), not just “don’t worry.”
- “Do I need a special app or special hardware?” A PWA-based POS just needs a browser — not locked to a single hardware brand.
- “Which payment methods still work offline?” At minimum cash and EDC should work; QRIS reasonably needs to be online.
- “After coming back online, do stock and reports adjust automatically?” A correct sync updates stock and reports with no manual re-entry.
If any answer feels vague, test it yourself: flip on airplane mode in the middle of a demo transaction and watch what happens. Your checkout shouldn’t stop over something as mundane as five minutes of bad WiFi.
Tenavora is built with a PWA POS that keeps running offline and syncs automatically once online, with a double-transaction guard. See the F&B solution or start free for 30 days, no credit card required.