Which POS actually works offline? A test you can run in ten minutes

"Works offline" is the most abused claim in point-of-sale marketing, because it is technically true of almost anything. A screen that still displays when the wifi drops "works offline". Here are the five levels, from weakest to strongest.

Level 1: the screen does not crash

The app stays open. You cannot complete a sale. This is worth nothing and is still sold as offline support.

Level 2: the sale is queued

You can ring items up and the sale is stored locally, but you cannot print a compliant invoice. The customer gets a slip of paper that is not a tax invoice. Under ZATCA Phase 2 this is a compliance problem, not just an inconvenience.

Level 3: the sale completes but the invoice is not signed

The receipt prints, but without a valid cryptographic stamp and QR. It becomes compliant later, when the connection returns and the invoice is signed retroactively — which means the document you handed the customer and the document submitted to the authority are not the same document.

Level 4: the invoice is signed on the device

The device holds its own credentials and signs locally. The printed invoice is complete and valid at the moment of sale, with a correct QR. When the connection returns, the already-signed documents are reported.

Level 5: level 4, plus everything else

Signed offline sellingand the rest of the operation — the browser cashier, returns, shift close, cash reconciliation, printing to multiple stations, and a sync that reconciles without duplicates when the line comes back.

Where the Saudi systems land

Per an August 2026 audit, marked offline-capable:Wameed,Foodics,Revel.

Marked not offline-capable: NCR Aloha, Oracle Simphony, Rewaa, Marn, Geidea, Odoo, Sapaad, Hala.

Wameed is at level 5: sales, ZATCA signing and printing continue for 24 hours disconnected, in the native app and in the browser cashier, and the invoices are signed on the device at the moment of sale. Kitchen display is the exception — our KDS needs the local server, and we say so.

For Foodics and Revel, ask which level and get the answer demonstrated.

The ten-minute test

Take this to every demo. Do not accept a description; require the demonstration.

1. Ask the technician tophysically unplug the router, not to toggle a setting.
2. Ring up a sale with a modifier and a discount.
3. Take a card payment.
4. Print the invoice and inspect the QR. Scan it with a phone. Does it resolve to a valid ZATCA payload with a stamp?
5. Ring up nine more sales, including one return.
6. Close the shift and print the shift report.
7. Reconnect.
8. Open the back office and confirm all ten transactions arrived, once each, with correct totals.

Step 4 is the one vendors skip. Step 8 is the one that catches duplicate-sync bugs.

Why it matters more in Saudi Arabia than the brochures suggest

Three reasons:

Connectivity is not uniform. Mall units on leased lines are fine. Street units on consumer fibre, temporary units at events, and units in industrial areas are not.

Peak hours are concentrated. Saudi retail and restaurant revenue concentrates heavily around evenings and weekends. An outage at 9pm Thursday costs several times what the same outage costs at 11am Tuesday.

Phase 2 raised the stakes. Before Phase 2, an outage meant a manual receipt and a late entry. Now it means either a compliant signed invoice or a document that is not one.

What to do if your current system is level 2 or 3

Two options: accept the risk knowingly and write a paper fallback procedure your staff have rehearsed, or change systems. What you should not do is assume it will be fine, because the outage will happen during the busiest hour — that is when the network is under most load.

Our offline architecture is described on theZATCA page, and the full comparison across eleven systems is on thecomparison page.