Planning reliability · 6-minute read
Cloud vs offline POS: what keeps your counter working?
Compare cloud, local and hybrid POS using real checkout dependencies, outage tests, backup recovery and the cost of keeping a counter working.
The practical answer
Should your shop choose cloud or offline POS?
Choose by the tasks that must keep working when a connection fails. A local checkout may still depend on online payments or invoicing services; a cloud product may offer limited offline functions. Test the exact edition, its reconnection behaviour and recovery process instead of deciding from the label alone.
1. Separate the counter from its dependencies.
“Cloud” often describes where software or data is hosted. “Offline” describes whether a particular task can work without a connection. Neither label tells you what happens to every task in your shop.
Draw a simple dependency map: the checkout device, local network, internet connection, payment provider, invoicing service and remote reports. For each task, ask which links it needs. Billing locally does not by itself make a card terminal, a remote dashboard or an external invoicing service available offline.
2. Compare the operating model, not just the label.
| Model | What to investigate | What not to assume |
|---|---|---|
| Cloud-centred | Which tasks require internet? What remains usable during an outage? | That all cloud products stop completely—or all support offline checkout |
| Local or offline-first | Where are records stored? How are devices backed up and recovered? | That offline billing also makes payments and external services work offline |
| Hybrid | Which records sync, when, and how are conflicts handled? | That reconnection guarantees an immediate, complete or conflict-free sync |
These are evaluation categories, not claims about features in Oasis POS. Confirm its available edition and behaviour against your requirements during a consultation.
3. Run an outage-and-reconnection drill.
Agree a safe demonstration with the supplier using test records. Start by completing one normal sale. Then interrupt the relevant connection and try the tasks you cannot afford to lose. Do not interrupt a live payment or production system for this exercise.
- Can the cashier sign in and find the required products?
- Can they record a sale and print the intended receipt?
- Which payment methods and invoice steps remain available?
- What happens at a second counter using the same product?
- After reconnecting, which records are queued, rejected or duplicated?
- How does an owner see and resolve an incomplete transaction?
Ask the supplier to show the report after reconnection, not only the successful sale screen. Check the stock and payment totals against the test transactions.
The useful question is “how stale can this number be?”
A remote stock figure or dashboard is useful only if you understand when it was last updated. Ask for a visible update time and a way to identify pending work. A fast-looking report can still be based on yesterday’s records.
4. Price the recovery work as well as the subscription.
Ask for a complete quote: counters, devices, setup, training, renewals, backup arrangements, remote access if needed, and the service scope when something fails. For local systems, establish who maintains the machine and restores a backup. For hosted systems, establish export access and what happens when your subscription ends.
Use a simple planning exercise: missed transactions × your estimated contribution per transaction, plus staff recovery time. This is a scenario, not a forecast of lost sales. Repeat it for a short connection failure and a failed checkout device. The comparison may reveal that your biggest dependency is hardware, power or payment acceptance rather than the software hosting model.
5. Write the decision in one paragraph.
Try this: “We need these checkout tasks during a connection failure. These other tasks may wait until reconnection. Our records must be recoverable using this tested process. These people own the backup, reconciliation and support steps.”
Now compare each proposal with that paragraph and the demo evidence. If you are planning several counters, test shared stock and permissions as well. If you are starting from scratch, work through the POS setup guide before buying equipment.
Common questions
Does offline POS mean no internet is ever needed?
No. Specific workflows, updates, integrations or reporting may require a connection. Ask for a task-by-task explanation for the exact edition.
Is a cloud backup enough?
A backup location alone does not establish recovery. Confirm what is backed up, how often, how access is controlled and whether a restore has been tested. Sync and backup serve different purposes; synchronising an accidental change may copy that change elsewhere.