The cloud-vs-local POS debate is usually framed as old versus new. That framing hides the only question that matters operationally: when the internet connection drops, what exactly must keep working? A shop can be open when its connection is not — and your architecture has to decide what happens during that gap before anything else.
Decide where the counter must keep working
Some functions cannot pause: taking a sale, printing a receipt, recording a shift, applying a loyalty discount. Other functions tolerate delay: consolidated reporting, catalog updates, cross-branch stock views. Write your own list in those two columns. The architecture follows from that list, not from vendor marketing.
Pure-cloud systems answer the first column with "the counter waits" — acceptable for some businesses, unacceptable for others. Pure-local systems answer the second column with "reports lag". Most real operations need a deliberate mix: local-first selling with cloud consolidation.
Synchronization is the hard part
A local-first system needs clear answers to unglamorous questions. Who owns a record when two locations change it while disconnected? How are stock counts reconciled after an outage? What does the operator see when something could not sync? "It syncs" is not an answer; it is the beginning of the specification.
“Offline-first is not a feature. It is a set of decisions about failure modes, made before the first sale goes through a dead connection.”
The questions to ask any vendor — or your own build
What happens to an in-progress sale when the network drops mid-transaction? How are refunds handled offline? Can two branches both sell the last unit, and what resolves it? How long can the system run disconnected before behavior changes? If these questions get vague answers, the sync layer is not finished.
What we would build today
For retail and restaurant operations in Pakistan — where connectivity varies by district and power events are part of life — we design counters that keep selling through outages and reconcile safely on reconnect, with cloud reporting that reflects the outage window transparently rather than hiding it. That is the standard we hold Ropulse to, and it is the standard we would apply to any POS engagement.