Cloud or on-premise POS? The question is actually about outages

There are three architectures, not two, and the third is the one that matters most in Saudi Arabia.

Cloud-only

The application runs on the vendor's servers; the terminal is a window onto it.

Good: updates arrive automatically, multi-branch reporting is consolidated by default, you need no server and no IT person, and your data is backed up by someone whose job that is.

Bad: when the line goes down, the terminal is a window onto nothing. No sale, no invoice, no shift close.

Most modern POS systems, including several sold in Saudi Arabia, are cloud-only. Our August 2026 audit marks eight of the eleven systems we track as not offline-capable.

On-premise

A server in the back room; terminals talk to it over the local network.

Good: the shop keeps working when the internet goes down, because nothing left the building. Latency is very low.

Bad: you now own a server. Backups are yours. Updates are a project. Multi-branch reporting means either a VPN or a nightly export. When the server's disk fails on a Friday, you have a much bigger problem than an internet outage. And it is only resilient againstinternet failure — a power cut or a hardware fault takes everything.

Enterprise platforms often deploy this way, which is part of why they need an implementation partner.

Local-first, cloud-synced

The full application and the data live on each terminal. The cloud is where terminals synchronise, not where the application lives.

Good: the terminal is complete on its own. It sells, signs ZATCA invoices, prints and closes shifts whether the internet is up or not. When connectivity returns it reconciles. You still get automatic updates, consolidated multi-branch reporting and managed backups, because there is still a cloud — it just is not on the critical path for a sale.

Bad: it is harder to build. Conflict resolution between terminals is a genuine engineering problem — two terminals selling the last unit of the same product while disconnected is a case someone has to have thought about. That is why fewer vendors do it.

This is Wameed's architecture, and it is the reason a Wameed terminal keeps issuing compliant invoices for 24 hours offline, including in the browser.

The question that decides it

Not "do I want my data in the cloud?" but:

What does an hour of not being able to sell cost me, and how many of those hours will I have this year?

Work it out: peak-hour revenue × expected outage hours. For a restaurant doing SAR 8,000 in a peak evening hour with four outage hours a year, that is SAR 32,000 — considerably more than the difference between any two subscription tiers.

Then ask what your connectivity is actually like. A mall unit on a leased line is a different risk profile from a street unit on consumer fibre, and both are different from a temporary unit at an event.

Data ownership, properly considered

The ownership question is real but it is usually asked the wrong way round. What matters is not where the bytes sit; it is:

1. Can you export everything, in a standard format, whenever you want?
2. Is the export included or billed?
3. How long is your data retained after you leave?
4. Who else can see it?

A cloud vendor who answers all four well gives you more real control than an on-premise server whose database format nobody at your shop can read.

ZATCA changes the calculus

Under Phase 2, the terminal signs invoices with its own certificate. That is a local capability by design — which means the architecture that keeps the certificate on the device is also the architecture that can keep trading offline. See theoffline rules.

A cloud-only system that signs on the server has tied your compliance to your connection.

The short recommendation

• Reliable connectivity, single site, no IT appetite: cloud-only is fine and is the simplest thing that works.
• Unreliable connectivity, or revenue concentrated into peak hours, or multiple branches: local-first with cloud sync.
• On-premise: only if you have an IT function and a specific reason, because you are taking on real operational burden.

More on how Wameed's sync works on thefeatures page, and how to test any vendor's claim in theoffline comparison.