Offline POS guide
Offline POS: How to Keep Selling When the Internet Drops
Learn how offline POS works, what should be stored locally and what merchants must check before relying on it.
The short answer
An offline POS keeps essential checkout functions available on the device during a connection problem, then makes pending work visible for review and synchronization. It should never hide whether an invoice is saved locally, submitted or accepted.
What an offline POS should do
A useful offline workflow lets staff find locally available products, build a basket, record the sale and produce the supported receipt output. Each transaction needs its own reference and a clear state so a retry is not mistaken for a second sale.
- Keep the local product and price data needed at checkout.
- Show queued, failed and completed states in plain language.
- Protect against duplicate submission when the network returns.
- Preserve a review trail for managers and support teams.
Offline selling is not the same as fiscal acceptance
A transaction saved on a device may still need a tax authority response. Country rules decide which documents may be created offline, how long they may wait and what must happen after connectivity returns. Confirm those rules before rollout.
- Ask which actions require a live response.
- Define who reviews unresolved items.
- Test a real outage and recovery before launch.
Questions to ask a provider
Ask for a live demonstration that begins online, loses connectivity and then recovers. The operator should be able to explain every status without reading a technical log.
- What remains available offline?
- How are retries and duplicates handled?
- What happens during a long outage?
- Which local fiscal rules limit offline use?