There is one question most merchants never ask before buying their point of sale software, and every one of them ends up wishing they had: what happens when the connection drops?
For most cloud registers on the market, the answer is blunt. The screen freezes, the open cart vanishes, and the queue starts growing while you reboot the router.
What a frozen register actually costs
A POS outage is not a technical incident. It is a production stoppage. As long as the screen is unresponsive, you are not selling.
The math is easy to run yourself. Take a normal day’s revenue, divide by your opening hours, and you have your hourly revenue. A 40-minute outage on a Saturday afternoon, right in the busiest slot of the week, easily costs a neighbourhood shop several hundred euros.
And the direct shortfall is only the visible part. Add to it:
- Permanently lost sales. A customer in a hurry who sees a stalled queue walks out. They do not wait, and they do not necessarily come back.
- Recovery errors. Taking payments “on paper” during the outage and re-keying everything afterwards produces stock discrepancies and forgotten lines.
- Reputation. A shop that puts up a “sorry, our system is down” sign twice in one month loses credibility with its regulars.
The retail industry has documented this for years: point of sale downtime is one of the most underestimated losses in retail (Jumpmind).
The problem is not just the internet going down
Plenty of merchants wave the topic away: “my fibre never fails.” That may well be true. But your register’s connectivity does not depend on your subscription alone.
It also depends on the shop’s wifi, which drops in the back room. On mobile coverage, when you take payment on the terrace, at a market stall, or on delivery. On the power cut that reboots the router for five minutes. And, in many countries, on network infrastructure that is simply irregular.
For a mobile trader, a food truck, a market stand, or a shop in an area with patchy coverage, offline mode is not insurance. It is the normal operating mode.
What “offline” really means
The word is used loosely. Three very different levels hide behind it, and the distinction changes everything.
Level 1, read-only. The app displays the last products it loaded but refuses to record a sale. Useless in practice.
Level 2, degraded checkout. You can take payment, but without the full catalogue, without stock updates, and sometimes without printing a receipt. It gets you through. It does not replace anything.
Level 3, full operation. Catalogue, prices, customers and stock levels are stored locally on the device. You sell normally, the receipt prints, stock decrements. On reconnection, everything uploads and synchronises.
Level 3 is what you should demand. The first two mostly allow a vendor to write “offline mode” on their pricing page.
Questions to ask before you sign
Put the vendor in front of concrete questions. Evasive answers are themselves an answer.
- How long can I sell without a connection? A few minutes, a day, a week? Some products force a reconnection every 24 or 72 hours.
- Does stock update offline? If it does not, you will sell items you no longer have.
- What happens if two registers sell the same item offline? Sync conflict handling is the real technical test.
- Is local data encrypted? A stolen device must not hand over your customer file.
- Can I print a receipt offline? That requires a directly connected printer, not a cloud-routed one.
- Is offline mode included or a paid add-on? It is often the feature that pushes you to the higher tier.
Offline and compliance
One worry comes up constantly: is taking payment without a connection compliant?
Yes, provided the software meets the requirements that apply in your country. In France, cash register software must satisfy conditions of inalterability, security, retention and archiving of data (economie.gouv.fr). Nothing in those requirements mandates a permanent connection.
What matters is that every sale recorded offline is timestamped, tamper-proof, and folded into the data chain once synchronisation happens. A serious vendor explains this in two minutes. A vendor who dodges the question deserves your suspicion.
A criterion that belongs at the top
Offline mode rarely leads comparison tables. Those focus on visible features: interface design, number of integrations, reporting.
That is a ranking error. A beautiful interface that does not work at 12:30 on a Saturday is worth less than a plain one that always takes payment. Resilience is not one feature among many. It is the precondition for all the others.
That is why we built digabloPos with offline at the core of the architecture rather than bolted on afterwards:
- Full operation without a connection: catalogue, prices, customers and stock available locally.
- Automatic synchronisation as soon as the network returns, with nothing to click.
- Multi-device: smartphone, tablet or computer, with consistent data after resync.
- Built-in mobile money: M-Pesa, Orange Money, Airtel Money, for markets where mobile payment dominates.
- Free, with no mandatory subscription: offline is not reserved for a premium plan.
Want to check whether your current setup would survive a two-hour outage? Let’s talk about your project and we will look at it with you.