In short
- 01An offline-first POS records each sale on the device first and syncs it in the background, so the till keeps selling when the internet or the server is down.
- 02Cash sales, receipts, stock deductions and most checks can carry on offline. Card payments depend on your card terminal and processor, not on the POS.
- 03The hard part is the return trip: each sale needs its own ID so it is recorded once, however many times it is resent.
- 04Test it yourself: unplug the router mid-sale, finish the sale, reconnect, and check the sale appears once.
On this page
- In short
- What does offline-first actually mean?
- What keeps working offline, and what doesn't?
- How do offline sales sync without duplicates?
- What does an outage cost a store without offline POS?
- Why does offline matter more for multi-store businesses?
- What should you ask a POS vendor about offline mode?
- How does Momentum handle going offline?
- Questions people ask
When the internet goes down, a cloud-only POS stops taking sales, because every sale needs the server. An offline-first POS keeps selling: it records each sale, receipt and stock movement on the device and syncs them in the background when the connection returns, with safeguards so a sale is never recorded twice. Card payments are the exception to check, because they depend on your card terminal and processor rather than on the POS itself.
What does offline-first actually mean?
Most cloud POS systems treat the server as the place a sale happens: the till sends the sale, waits for an answer, then prints the receipt. When the connection fails, the till has nothing to wait for, so it stops.
Offline-first reverses that. The sale is committed on the device first, and the network is used to sync it afterwards. If the connection is slow, down, or the server is having a bad day, the cashier doesn't notice, and a queue of sales waits to go up. The difference matters as much for a slow or overloaded server as for a cut cable.
What keeps working offline, and what doesn't?
The answer depends on the product, which is why you should ask for it in writing. For a well-built offline-first POS it looks like this:
- Offline-first POS
- Keeps working
- What to check
- That nothing needs to be switched on in advance
- Offline-first POS
- Keeps working
- What to check
- The drawer session closes normally later
- Offline-first POS
- Depends on your terminal and processor
- What to check
- The processor's offline limit and who carries the risk of a decline
- Offline-first POS
- Deducted on the device; synced later
- What to check
- How other stores see the change once it syncs
- Offline-first POS
- Checked against the last synced figures
- What to check
- What happens when a limit is crossed offline
- Offline-first POS
- Apply as last synced
- What to check
- How quickly a price change reaches the till once it's back online
- Offline-first POS
- Catch up after sync
- What to check
- That you can see which sales haven't synced yet
| At the till | Offline-first POS | What to check |
|---|---|---|
| Ring up sales, scan barcodes, print receipts | Keeps working | That nothing needs to be switched on in advance |
| Cash payments and change | Keeps working | The drawer session closes normally later |
| Card payments | Depends on your terminal and processor | The processor's offline limit and who carries the risk of a decline |
| Stock levels | Deducted on the device; synced later | How other stores see the change once it syncs |
| Customer balances and credit limits | Checked against the last synced figures | What happens when a limit is crossed offline |
| Prices, offers and permissions | Apply as last synced | How quickly a price change reaches the till once it's back online |
| Reports across all stores | Catch up after sync | That you can see which sales haven't synced yet |
On card payments, read your processor's rules. Square, for example, tells sellers that offline payments on some devices must be uploaded within 72 hours (24 is recommended) and that the seller is responsible for any expired, declined or disputed payments accepted offline.
How do offline sales sync without duplicates?
The risky moment is not the outage; it's the reconnection. A till that sent a sale just as the connection dropped doesn't know whether the server received it, so it sends it again. A naive system records it twice: double revenue, stock deducted twice, a customer charged twice on account.
The fix is idempotency. Every sale gets a unique ID on the device when it is created, and the server records a sale with a given ID only once, however many times it arrives. The till can resend freely, and the books stay right. Ask any vendor how they handle a sale that is sent twice, and ask to see it.
What does an outage cost a store without offline POS?
It depends on when it happens and how long it lasts. A rough, illustrative sum for one busy store:
Why does offline matter more for multi-store businesses?
With one store, an outage is one store's problem. With a chain on one cloud POS, a problem at the provider or the server stops every till at once. An offline-first POS lets each store keep trading on its own and catch up when the connection returns, while the rest of the chain carries on.
- Each store keeps selling if its own connection drops
- Stock sold offline syncs to the shared count when the till reconnects
- Customer balances and limits are checked against the last synced figures
- Consolidated reports catch up automatically after sync
What should you ask a POS vendor about offline mode?
- 1Show me a sale taken with the network unplugged, then reconnected. Does it appear once?
- 2What stops working offline, exactly? Get it in writing.
- 3How long can a till stay offline, and what happens to sales after that?
- 4How do my card terminal and processor behave offline, and who carries the risk?
- 5Can staff see that the till is offline and how many sales are waiting to sync?
- 6Does a slow or overloaded server count as offline, or does the till just hang?
For the full list of questions to ask about a multi-store system, see the multi-store POS buying checklist.
How does Momentum handle going offline?
Momentum's POS records sales on the till and syncs them in the background, so the till keeps selling when the internet or the server is down. Every sale carries its own ID, so a sale resent after a dropped connection is recorded once, not twice. Split payments, refunds, receipts and barcode scanning work at the till; permissions for price overrides and below-cost sales, and customer credit limits, are enforced there too.
It runs in a modern browser on the hardware you choose, with standard receipt printers, cash drawers and barcode scanners. Card payments go through your own card terminal, so check your processor's offline rules.
Questions people ask
Can a POS work without internet?
An offline-first POS can: it records sales on the device and syncs them later. A cloud-only POS usually can't take sales while the connection is down.
Are card payments possible when the POS is offline?
Sometimes, depending on your card terminal and processor. Many processors allow offline card payments with limits and time windows, and the seller usually carries the risk if a card is later declined.
Will offline sales be duplicated when the internet comes back?
Not in a well-built system. Each sale has a unique ID created on the device, and the server records each ID once, however many times the sale is sent.
Does stock stay accurate while tills are offline?
Each till deducts what it sells straight away, and the shared stock figure catches up when the till syncs. For a short outage the difference is small; for a long one, other stores see the change once the offline till reconnects.
Connections fail, and so do servers. An offline-first POS turns an outage into a short sync queue instead of a closed till, as long as it records every sale once when it reconnects. Ask any vendor to show you both halves: the sale taken offline, and the same sale appearing exactly once afterwards.
Sources
Pull the plug in a demo
In a Momentum demo we'll take a sale with the network off, reconnect, and show the sale synced once, with the stock and the books updated.
