The 72-Hour Offline Promise: Why We Made an Impossible-Sounding Guarantee

The call came at 2:30pm on a Saturday. A saree shop owner in Coimbatore had been running an in-store sale — the kind with printed banners and SMS invites, the kind you build for weeks. Her internet went down at 10am. By the time it came back at 2pm, she'd lost four hours of the busiest window, turned away customers she couldn't bill, and processed a handful of orders in a notebook that she'd spend two days reconciling later.

Her previous POS software's offline mode showed a screen that said 'Reconnecting...' for four hours. That was her offline mode.

We heard versions of this story dozens of times in our first year. And every time, we asked ourselves the same question: why does internet connectivity have to be a prerequisite for commerce?

The Connectivity Reality in India

Here is what's true about internet connectivity in India in 2026: it is simultaneously better than it has ever been and more uneven than any aggregate statistic suggests. A merchant in Bandra West has fiber. A merchant running the same business model in Vellore may have spotty 4G that drops during peak hours. A merchant at a trade fair — one of the highest-GMV commerce events of the year — may have hundreds of vendors sharing a single overloaded hotspot.

Cloud-only commerce infrastructure treats all of these merchants the same way: if the internet is down, you're down. This isn't a design philosophy. It's a design omission — a failure to think about the actual physical reality of where commerce happens.

We chose to think about it. The 72-hour offline POS is the result.

What Actually Works Offline

Saying your POS works offline is easy. Making it work correctly offline — maintaining inventory accuracy, GST compliance, loyalty point tracking, and customer records across a team of four billing staff — is genuinely hard.

The technical architecture involves on-device encrypted data stores that mirror the essentials of the platform's state, a conflict resolution engine that handles simultaneous edits across multiple POS terminals on the same local network, and a cryptographic transaction log that ensures every offline sale is provably accurate when sync happens.

But the harder problem isn't the data engineering. It's the human interface design. An offline POS that works correctly but shows your staff a confusing UI under stress is almost as bad as one that doesn't work at all. We spent more time on the offline UX — the indicators, the confirmations, the staff-facing feedback — than on any other aspect of the feature.

The Sync Is as Important as the Offline

Here's the part most people don't think about: when connectivity returns after a 72-hour outage, you have an enormous reconciliation problem. Thousands of transactions, loyalty point accruals, inventory movements — all of them need to sync accurately, without duplicates, without gaps, and without overwriting any changes that happened in other channels (online storefront, other store locations) during the same window.

Our sync engine handles this deterministically. Every transaction that happened offline is sequenced, deduplicated, and merged with the authoritative state using vector clocks and conflict resolution rules that we've tested across every edge case we could imagine — and several we couldn't, until real tenants found them for us.

When the internet comes back, the POS syncs in the background. Your staff continues billing. Your reports are accurate. Your GST returns are clean. The outage becomes a footnote, not a crisis.

Why This Is a Promise, Not a Feature

We could have shipped offline mode as a beta feature, something we offered with caveats and fine print. We chose to make it a promise — 72 hours, full functionality, no asterisks — because we believe commerce infrastructure that works only when conditions are ideal is not actually infrastructure. It's a dependency masquerading as a tool.

India's commerce future involves enormous growth in tier-2 and tier-3 markets, in rural supply chains, in semi-urban retail. These are not edge cases. They are the growth frontier of the next decade. Building infrastructure that only works in ideal connectivity conditions means explicitly choosing not to serve this growth frontier.

We chose differently. And we made it a promise because promises create accountability. If our 72-hour offline mode fails, you have a right to call us on it.

The Larger Principle

The 72-hour offline promise is an instance of a larger principle: commerce infrastructure should be built for the reality of where commerce happens, not the ideal conditions of a San Francisco office. Real commerce happens in power outages, poor connectivity, peak demand that overloads networks, and venues designed for crowds rather than bandwidth.

Building for these realities isn't a constraint. It's a competitive advantage. The platform that works when everything else breaks is the platform merchants trust with everything — including their best customers, their highest-stakes sales, their most complex operations.

That's the platform we're building.

Subscribe to the QuantumOS Dispatch — weekly insights for commerce operators who want to compound their advantages.