A network outage should not automatically make a store unable to sell. But offline capability is more than keeping the screen open. Local transaction safety, available data, reconnection synchronization and conflict handling must be designed in advance.
Why offline POS matters
Even with fiber or strong mobile connectivity, outages can come from the ISP, modem, local network or remote services. A few minutes during a peak period can create queues and lost revenue.
What data should be available locally?
Products, barcodes, valid prices and essential sales rules should be available in a controlled local form. The minimum-data principle is preferable to storing unnecessary customer or management data on the endpoint.
How should transactions be protected?
Every offline transaction needs a unique identity. Retries must not create duplicate sales, and synchronization state must be observable rather than guessed.
What happens when connectivity returns?
Synchronization should run through a controlled queue, separating successful, pending and failed records. Conflicts such as changed prices or inventory should follow predefined business rules.
Fiscal devices need separate consideration
Offline ERP/POS capability does not remove the connectivity requirements of fiscal devices or payment infrastructure. End-to-end continuity must assess ERP, fiscal POS, banking/payment and network dependencies separately.
Biltegra OfflineKasa
OfflineKasa is one of Biltegra’s five PWA applications and supports the browser-based sales-continuity approach. Its purpose is to help store operations continue in a controlled way during connectivity problems.