Sell through the outage
SumPOS is offline-first by design, not by fallback. The till reads and writes locally, always - the network is just how the data eventually travels.
100%
of till functions available offline
Local-first architecture
Conflict-safe merging
Optional local server
Local-first architecture
A real database on the device holds your catalogue, customers, prices and today's transactions. Reads are instant.
Conflict-safe merging
Stock movements are recorded as events, not overwrites, so two tills offline at once never lose each other's sales.
Optional local server
For large sites, run a SumPOS node on the premises so branches keep sharing data even with no internet at all.
Why offline-first matters more than it should
Fibre gets cut. Routers die. Power goes at the worst hour. Mobile data drops in a basement food court. In many of the markets we serve, this is a weekly event rather than an emergency. A POS that stops selling when the internet stops is a POS that costs you money on exactly the days you can least afford it.
- Full checkout, returns, held bills and shift close while offline
- Customer lookup and loyalty balance from the local cache
- Receipt printing and cash-drawer control unaffected
- Clear, calm indicator showing sync status - never a blocking error
- Automatic background sync the moment the line returns
Sync you can inspect
Sync is not a black box. A sync centre shows exactly what is queued, what has been accepted, and anything that needs a human decision - with a plain-English explanation rather than an error code.
- Per-device queue with counts and timestamps
- Retry and priority controls
- Event log with plain-language descriptions
- Alerts if a device has not synced within a window you set
- Encrypted local storage and encrypted transport
One codebase, every platform
The rules that price a bill, apply a tax and post a journal entry are written once and shared by the Android till, the iPhone in your pocket, the Windows counter machine, the macOS back office and the web dashboard. Identical behaviour everywhere - because it is literally the same code.
Everything in Offline Mode & Sync
No asterisks, no 'coming soon' hidden in a footnote. If it is listed here, it ships.
Offline
- Full offline checkout
- Local catalogue & customer cache
- Offline returns & exchanges
- Offline shift open / close
- Local receipt & KOT printing
- Configurable offline duration limits
Sync
- Event-sourced stock movements
- Background incremental sync
- Conflict detection & resolution
- Sync centre with queue visibility
- Stale-device alerts
- Bandwidth-aware scheduling
Deployment
- Cloud (managed by us)
- On-premise local node
- Hybrid cloud + local node
- Private cloud for enterprise
- Data residency options
- Automated backups
Security
- Encryption at rest on device
- TLS 1.3 in transit
- Remote device wipe
- Device registration & approval
- Session and PIN policies
- Tamper-evident audit log
Offline Mode & Sync - the usual questions
Still unsure about something? Ask us directly - a person answers, usually the same day.
Indefinitely, in practice - the limit is device storage. We recommend setting a policy alert so head office knows if a till has been offline for longer than, say, 24 hours, but there is no hard cut-off that stops you trading.
Works even better with
These modules share the same data, so turning one on makes the others more useful.
Ready to see your business on one screen?
The point of sale is free forever - unlimited registers, unlimited stores, no card required. Add the back office only when you actually need it.
No card required · Free forever · No commission on your sales · Your data stays yours