Skip to content

How Wameed keeps selling when the internet does not

Local-first, not cloud-with-a-cache. Here is what that actually means, what happens to the ZATCA signature, how two disconnected terminals are reconciled, and the one part that still needs the network.

By Wameed product teamProduct and engineering

7 min read

In short: Wameed islocal-first, not cloud-with-a-cache: the full application and its data live on each terminal, and the cloud is where terminals synchronise, not part of the sale. Itsigns ZATCA invoices on the device, so an invoice issued disconnected is complete and valid when it prints (correct XML, hash chain and QR with stamp and public key), and it is reported inside the 24-hour window when the line returns. Offline invoices continue the same hash chain; sales are never rejected on a sync conflict; stock reconciles to reality on sync (a negative is an exception to investigate). The browser cashier works offline too, and kitchen tickets run over the local network. Offline lasts up to 24 hours; card authorisation, the online store, kiosk and B2B clearance still need a connection.

"Works offline" is claimed by almost every point of sale and means something different in each. Here is precisely what it means in ours, including where it stops.

Local-first, not cloud-with-a-cache

The distinction matters.

Cloud with a cache means the application lives on a server and the terminal holds a copy of some data so the screen does not go blank. When the connection drops, you may be able to look at things; you generally cannot complete a compliant sale.

Local-first means the full application and the data it needs live on the terminal. The terminal is complete on its own. The cloud is where terminals synchronise with each other and with the back office — it is not on the critical path for a sale.

The practical consequence: a Wameed terminal does not behave differently when the network drops. It carries on, because the network was never what was making the sale work.

The ZATCA part

This is the piece that makes offline selling legally meaningful rather than just convenient.

Under Phase 2, every invoice carries a cryptographic stamp produced with a certificate issued to that specific device. Two architectures are possible:

  • Sign on a server. The terminal sends invoice data up, the server signs, the signature comes back. Simple to build, and completely dependent on connectivity.
  • Sign on the device. The production certificate and its private key live on the terminal. The stamp is computed locally in milliseconds.

Wameed signs on the device. So an invoice issued while disconnected is a complete, valid invoice at the moment it prints — correct XML, correct hash chain, correct QR with the stamp and public key. Not a placeholder to be fixed later.

Reporting to the authority happens when connectivity returns, inside the 24-hour window that simplified invoices have. Seeoffline rules.

The hash chain across an outage

Each invoice references the hash of the previous one from the same device. Offline invoices continue that same chain — they do not start a parallel one that has to be merged later, because a merge is exactly what produces a visible break.

When the device reconnects, it reports the already-signed documents in order.

Two terminals, both disconnected

This is the genuinely hard engineering problem in local-first design, and it is why fewer vendors build this way.

Two terminals, both offline, both selling the last unit of the same product. Both are locally correct; together they are wrong.

How we handle it:

  • Sales are never rejected. A sale that happened, happened. Reversing a completed transaction because of a sync conflict is not acceptable behaviour at a till.
  • Stock reconciles to reality on sync, which may produce a negative figure. A negative is a true statement — you sold more than you had — and it surfaces as an exception to investigate rather than being silently rounded to zero.
  • Invoice sequences are per device, so two terminals cannot collide on numbering or on the hash chain.
  • Last-write-wins is not used for anything that matters. Price changes, stock adjustments and configuration are ordered by the server, not by whichever terminal syncs last.

The browser cashier

Unusually, the browser cashier is also offline-capable. It holds its data locally and signs ZATCA invoices the same way the native app does.

The practical value is a failure plan: when a terminal dies on a busy evening, any laptop becomes a working till in about five minutes, and it works whether or not the internet is up. Seedowntime procedures.

What still needs the network

Selling, signing and printing do not. A few things cannot work without a connection, and we would rather name them:

  • Card authorisation. A card payment needs the network even when the POS does not. Plan a cash or separate mobile-data fallback.
  • Online-store checkout and the WhatsApp inbox, which are online by nature.
  • The self-service kiosk and drive-thru lanes.
  • Booking checkout and package redemption in the services system (plain service lines still sell offline).
  • Standard (B2B) invoices, which need clearance from the authority.

The kitchen isnot on this list any more. Kitchen tickets and the kitchen display run over the restaurant’s local network (Professional and above), so losing the internet line does not stop the pass. If the local network itself fails, the fallback is printed tickets from a wired kitchen printer, and it is worth rehearsing the switch once. Seekitchen printing offline andkitchen display systems. Of the systems in our comparison set, Wameed, NCR and Revel are marked as having an offline kitchen display.

How long

Twenty-four hours of offline operation. The limit exists because reporting obligations do not pause, and a terminal that has been disconnected for days accumulates a reporting backlog that needs attention rather than silence.

The terminal shows the pending-report count where staff can see it, and reporting resumes automatically on reconnection.

How to verify any of this

Do not take our word for it. Unplug the router, complete a sale with a modifier and a discount, take a card payment, print the invoice, scan the QR with your phone, ring up nine more, reconnect, and check all ten arrived once each.

The ten-minute protocol is in theoffline comparison, and it works on any vendor's demo, including ours.

Related:which POS actually works offline,ZATCA invoicing when the internet is down,POS downtime procedures andcloud vs on-premise vs local-first.

Frequently asked questions

What does “local-first” mean?

The full application and the data it needs live on each terminal, so it sells, signs and prints with or without internet. The cloud synchronises terminals and the back office but is not on the critical path for a sale.

How long can Wameed work offline?

Up to 24 hours, because reporting obligations do not pause. The terminal shows the pending-report count and reports automatically when the line returns.

What happens if two offline terminals sell the last unit?

Both sales stand. Stock reconciles on sync and may show a negative, which surfaces as an exception to investigate. Invoice sequences are per device, so there are no numbering or hash-chain collisions.

Does the kitchen display work offline?

Yes, over the restaurant’s local network on Professional and above; keep a wired printer as the fallback for a local-network failure.

What still needs the internet?

Card authorisation, online-store checkout, WhatsApp, the kiosk and drive-thru lanes, booking checkout and package redemption, and B2B clearance.

  • #كاشير بدون إنترنت
  • #العمل دون اتصال
  • #كاشير وميض
  • #توقيع زاتكا على الجهاز
  • #offline POS
  • #local-first
  • #on-device ZATCA signing
  • #browser cashier

Share this article

Ask about your own shop

Thirty minutes on your products, your tax setup and your hardware — not a slide deck.

Keep reading