Your tills never talk to the internet, so losing it changes nothing
The shop keeps trading when the connection does not. Tills keep selling, kitchens keep printing, receipts keep coming out — and when the line returns, everything reconciles into the same books. There is no separate offline system to merge afterwards.
An outage should be a non-event, not a recovery
In most systems, the internet is load-bearing. The till asks a server somewhere for a price, and when the line drops the queue stops with it — so a shop either turns customers away or writes sales on paper and re-keys them later, hoping the totals still agree at close.
An unreliable connection is the single most common reason a business keeps running an old system it otherwise dislikes. EloERP removes the dependency rather than working around it. Nothing on the shop floor was relying on the internet in the first place, so there is nothing to fall back to when it goes.
Three layers, and only one of them needs the internet
The ledger, stock, costing, invoice numbering and tax all live centrally. This is the single source of truth, and it stays that way whether a sale happened online or not.
It holds a mirror of the menu, prices and customers, a queue of everything sold, and the printing. It is the only thing on site that ever needs a connection.
All of them are browsers on the shop's own network. They talk to the branch server, never to the cloud directly — which is exactly why an outage does not reach them.
There is no second set of books, because there was never a second set
The till works out the bill using the same pricing code the cloud uses, then queues the finished sale. When the connection returns, the server replays each sale through exactly the same path an online sale takes.
So the ledger entries, the stock movements, the cost of sales, the invoice number and the tax are all still produced by the central system, in order. Nothing is estimated on the shop floor and corrected later — the offline sale and the online sale are the same transaction taking the same route, just at different times.
Each till is also given its own reserved block of invoice numbers, so two tills selling through the same outage cannot produce the same invoice number.
What keeps working
- Product search, barcode scanning, weighed labels, quantity and line discounts
- Cash tendering with change calculation, and split payment across methods
- Quantity-break pricing and promotions, resolved on the till itself
- Age-restriction prompts
- Hold a sale and recall it
- Sale returns and refunds, and voiding a sale
- Cash in and cash out of the drawer
- Opening and closing a shift
- Silent receipt printing, with the same receipt layout as online
- Creating a new customer at the counter
- Dine-in, takeaway and delivery orders, and the table plan
- Send to kitchen, with tickets printing to the right department
- The kitchen display, served from the branch server
- The waiter terminal — take an order, mark served, request the bill, add a tip
- Held orders, and recalling them
- A draft or temporary bill for a table, printed without posting anything
- Delivery address on the bill, and assigning a rider
- Service charge and tips, credited to the right waiter
- The "86" board — items marked unavailable, including timed availability
- Call-centre order taking
X offline, Z online
A cashier can take an X report at any point during an outage. It is calculated with the identical expected-cash formula the server uses, so the numbers match what the final report will say — a supervisor can check a drawer mid-shift without waiting for the line to come back.
The Z report posts cash variance to the ledger, so it is only permitted once every event from that shift has reached the cloud and the sequence is confirmed to have no gaps. A manager can override this in a genuine emergency, and the override is recorded.
What stays online, on purpose
Every item below is a case where working offline would let two tills spend the same thing twice, or where the feature depends on the outside world by definition. Allowing them offline would create a reconciliation problem worse than the outage.
- Redeeming gift cards, store credit and loyalty balances. Earning all three works offline — it is only spending a shared balance that needs the connection, so two tills cannot draw on it at once.
- Credit sales and instalment plans. Offline sales are cash-settled, because extending credit against a limit needs the current balance.
- QR-code table ordering and the waiting list. Both reach the customer's own phone over the internet.
- Delivery-aggregator channels. Orders arrive from an outside platform, so there is nothing to receive while the line is down.
- Sending a receipt by SMS. Printed receipts are unaffected.
A console on site, and control from head office
Licensed, paired and revocable
Any software installed on a shop's own computer can eventually be tampered with, and we would rather say what the controls actually are than claim they are perfect.
Offline POS, answered
Do I need to install anything on site?
Yes — one small branch server per site, installed once. The tills, waiter tablets and kitchen screens are browsers on your own network and need no separate installation. The branch server is what holds the local mirror, the sale queue and the printing, and it is the only thing on site that talks to the internet.
Will my books be different for offline sales?
No. The till prices the basket using the same code the cloud uses, then queues the sale. When the connection returns, the server replays each sale through exactly the same path an online sale takes, so the ledger entries, stock movements, cost of sales, invoice number and tax are all produced centrally as normal. There is no separate offline ledger to merge, because one was never created.
Can two tills issue the same invoice number during an outage?
No. Each till is given its own reserved block of invoice numbers before it ever goes offline, so tills trading through the same outage draw from different blocks and cannot collide.
Can customers redeem loyalty points or gift cards while the internet is down?
Earning works offline — points, stamps and cashback all accrue normally. Redeeming needs a connection, and that is deliberate: a shared balance spent on two offline tills at once would be spent twice. Treating redemption as an online action is what keeps balances correct.
Can I close the shift without a connection?
You can take an X report at any time offline. It uses the identical expected-cash formula the server uses, so its numbers match the final report. The Z report — the finalised close, which posts cash variance to the ledger — waits until every event from that shift has reached the cloud and the sequence is confirmed complete. A manager can override this in a genuine emergency, and the override is recorded.
Does the kitchen keep printing during an outage?
Yes. Kitchen tickets print to the right department and the kitchen display keeps running, because both are served by the branch server on your own network rather than from the cloud.
See it with the cable pulled out
The most convincing version of this demo is the one where we disconnect the line mid-sale and keep going. Book thirty minutes and we will do exactly that.