Offline-first POS: keep selling when the internet drops

A cloud POS is a website with a database behind it. When the internet is down, the screen may still load, but saving a sale fails — or silently queues and later loses it. An offline-first POS is built the other way around: the application and database run locally, and the network is an optional extra.

What "offline-first" actually means

Offline-first means the primary copy of the data lives on your equipment, and the app is designed to work without a remote server. On a local network, the till, the back-office computer and a stock tablet talk to the same local system. Internet is used for sync, backups and remote support — not for every button press.

That design also changes the failure mode. A cloud outage is your outage. A local outage is a hardware problem you can see and fix, with your data still in the building.

What keeps working, and what waits

• Keeps working: selling, printing receipts, stock movements, customer balances, shifts and daily totals on the local network.
• Waits for the connection: syncing to a second location, remote dashboards, and some notifications.
• Depends on hardware: a dead tablet or router is still a dead tablet or router — no software design fixes that.

The honest question to ask any vendor is not "does it have an offline mode?" but "which of my daily tasks stop, and for how long?" A good answer lists them.

How sync works — and what to ask about conflicts

Most offline-first systems record each change locally and send it when a connection returns. The interesting cases are conflicts: two devices editing the same record, or a sale recorded twice. Vendors resolve these differently — some block the operation, some keep the latest change, some merge. Ask to see the rule, and ask who wins when two people edit the same customer balance.

For a single shop on one local network, conflicts are rare. For multiple branches, the sync rule is part of the buying decision, not a detail for later.

Power cuts and restarts

A local server needs power. A small UPS keeps the server and router alive long enough to close the shift, and an offline-first POS restarts into the same local database rather than waiting for a cloud login. Test this before you commit: unplug the internet, make a sale, restart the machine, and check that the sale is still there.

Questions to ask before you rely on it

• Does a sale save when the internet is off — and how do I verify that it did?
• What happens to a queued change if the device is switched off?
• Where is the database file, and can I take a copy of it?
• How are backups restored, and who can do it?
• What does support look like during an outage — and does it need the same internet?

How EBS fits

EBS systems run as a local server on your premises with offline-first operation as the default. The solutions overview lists the modules, live demos show the interface with sample data, and the on-premise vs cloud comparison covers the data-ownership side.

Frequently asked

Does the POS stop working when the internet goes down?

No. Selling, receipts and stock work on the local network; internet-dependent features such as remote dashboards and secondary-location sync wait for the connection to return.

What if the power goes out?

A UPS keeps the local server and router running long enough to close the shift safely. The system restarts into the same local database.

Can we still get remote support?

Yes, when the connection is available. Support sessions use the internet; the shop keeps trading locally if it is not.