Offline Mode

Offline mode is what a system keeps doing when the internet drops in the middle of a sale, so the work carries on until the connection returns.

Also known as offline working offline first works without internet

Definition

Offline mode is what a system keeps doing when the internet drops and the work has to carry on anyway. The screen stays open, the sale still goes through, and the record waits on the device until the connection comes back. Once it does, the sale is sent up and joins everything else. For a shop on a busy street, that gap decides whether the queue moves or walks out.

Not everything can be queued, and knowing which half is which is the whole design. A sale can wait, because the price and the product list already sit on the tablet. A card payment usually cannot, because the bank has to answer while the customer stands there, and a discount code checked against head office fails for the same reason. So anything needing an answer from elsewhere stops, while anything that only needs writing down carries on. Linkysoft draws that line on paper with the client before a single screen is built.

The surprises arrive at sync time rather than during the outage itself. The classic one is the duplicate receipt, where a cashier presses print, sees nothing, presses again, and two identical sales turn up an hour later. A system that numbers every sale on the device catches that pair, while one that numbers sales on the server cannot tell them apart. The other surprise is two branches editing the same record while both are cut off, because one of them is going to lose. You want to know in advance which one, and whether anybody is told.

Stock is where this hurts most, because two counters can sell the last unit of the same item while both are offline. The shelf ends up empty while the system still thinks there is one left. That is why Storek keeps stock branch by branch and raises a flag on the clash instead of quietly picking a winner. Linkysoft treats that flag as part of the design, because a silent overwrite only shows up weeks later in a stock count, when nobody can say which sale was real.

Three plain questions tell you most of what you need from a supplier. How long can we work offline before the device fills up, and what exactly stops working while we are cut off. And when the connection returns, who reviews the conflicts, because somebody has to. Linkysoft answers all three in writing before quoting a web application project, and the same questions apply to the phone app your delivery drivers carry.

Questions about Offline Mode

Can I keep selling when the internet goes down?
Usually yes. The sale is saved on the device and sent up when the connection returns. Card payments are the exception, because the bank has to approve them at that moment.
What stops working while a system is offline?
Anything that needs an answer from somewhere else. Card approval, checking a discount code with head office, seeing live stock in another branch, and sending email or messages all wait.
Why do duplicate receipts appear after the connection returns?
Because the button was pressed twice during the outage and each press became its own sale. A system that numbers every sale on the device spots the copy and drops it before it reaches the accounts.
What happens if two branches change the same record while both are offline?
One change wins and the other is overwritten, unless the system flags the clash for a person to settle. Ask a supplier which of the two it does, and ask to see it on screen.

Still not sure how this applies to your project?

Tell us what you are building and we will answer in plain language.