When NEPA Takes Light: What Offline-First Software Actually Means

Every vendor selling business software in Nigeria says it works offline. Very few mean the same thing by it, and the difference only shows up on the afternoon your band drops and there is a queue at the counter.

Three things "offline" can mean

It shows you old data. The screens load from a cache, so you can look at yesterday's figures. You cannot sell. This is the weakest version and the most common.

It queues what you type. You can ring a sale and it is held on the device, then sent when the connection returns. Better — but if the queue is not designed carefully, two tills selling the same last item both succeed, and your stock goes negative.

It runs locally and reconciles. The device holds a real copy of what it needs, applies your sale immediately, and merges properly when the connection returns — including resolving the case where two devices touched the same stock. This is what you want, and it is the hardest to build, which is why it is rare.

Five tests before you commit

Do these in the shop, not in a demo.

1. Turn off the router mid-sale. Not before — during. Does the sale complete, or do you lose the basket?
2. Complete five sales offline, then reconnect. Do all five appear, once each, with the right totals? Watch for duplicates as much as for missing ones.
3. Sell the same last unit on two devices while both are offline. Then reconnect. What does the system do? It should tell you clearly, not silently show minus one.
4. Print a receipt offline. If receipts need the server, your gate control stops when the network does.
5. Kill the power to the device entirely, then restart it. Is the sale you were part-way through still there?

Why this is a Nigerian requirement, not a nice-to-have

Software designed where power and connectivity are assumed treats offline as an error state — something to warn about and recover from. Software designed here has to treat it as a normal Tuesday.

That difference shows up in the architecture, not the marketing. You cannot bolt real offline capability onto a system that assumes a live database, which is why the honest test is the router test, not the sales pitch.

The part people forget: staff behaviour

The real cost of a system that stops during an outage is not the lost minutes. It is what staff learn to do instead — hand-written slips, goods released on trust, sales entered later from memory. Those habits outlive the outage, and they are where losses come from.

A till that always works removes the excuse permanently.

Frequently asked questions

Do I still need a generator or inverter? Yes — offline software keeps the software running, not the hardware. A small inverter for the till and printer is usually enough, and far cheaper than powering the whole shop.

How long can it stay offline? Ask the vendor for a number and test it. A system that copes for an hour and one that copes for two days are very different products.

Is my data at risk if it is on the device? Only if it stays there. What matters is that it syncs when it can, and that you can see clearly what has not yet synced.