POS System for Saudi Arabia — Bilingual, VAT-Ready at 15%, Priced in Plain Dollars

VAT at 15%, e-invoicing, and the thing most vendors will not tell you

1. July 2020

   The current 15% value-added tax rate takes effect.

2. August 2026

   Electronic invoicing operates under a phased mandate.

Saudi Arabia has applied value-added tax at 15% since July 2020, administered by the Saudi tax and customs regulator. As of August 2026 that is the standard rate. Confirm your own registration threshold, filing frequency, and sector treatment with the regulator through my.gov.sa — a software vendor is not a tax adviser, and that includes us.

On VAT itself, here is the concrete version of "VAT-ready" — what the system actually does, so you can check it against what you need:

What the system actually does about VAT

• The rate is a configuration value, not a hardcoded assumption baked into the receipt renderer. It is set on the tax profile. That is what makes a rate change an edit rather than a release.
• The tax registration number field exists on the merchant profile and prints in the receipt header when populated.
• Line-level breakdown prints in Arabic and English, so a receipt shows net, tax, and gross per line rather than a single tax figure at the foot.
• Reports separate net, tax, and gross per branch, which is the shape an accountant wants and the shape a filing needs, rather than one consolidated number you then have to pick apart.
• Zero-rated and exempt items are handled as their own treatment, not as a 0% hack on a standard-rated product — the distinction matters on a return.

E-invoicing, and the part we will not dress up

Now the part that matters more, and that this page will not dress up. Saudi Arabia operates a mandatory electronic invoicing regime, phased in since 2021 and administered by the same regulator. For most established businesses it is not optional and it is not a future problem. Sandooq does not integrate with it today. Formal e-invoicing integration belongs to a later product rollout. That is a real gap, it is the largest one on this page, and you should weigh it before you weigh anything else here.

What that means in practice: if your business is already inside the mandate, Sandooq is not sufficient on its own for your invoicing obligations, and you should treat this page as a description of a till and a back office rather than of an invoicing solution. If you are below the thresholds or newly registering, check where you sit with the regulator directly before deciding.

We would rather lose the enquiry than win it on a misunderstanding that surfaces at your first filing. And it is worth saying that this is the question to put to every vendor whose Saudi page leads with the topic: ask what specifically is integrated, ask to see it working against a real account, and ask what happens when the specification changes. A page that treats the regime as a badge rather than an integration is telling you something.

What POS software actually costs in Saudi Arabia

This is the section that earns the page. The Saudi results do not answer the question at all: the aged domains holding the head terms quote "request a demo", the reseller listings bundle software into a per-terminal hardware price so you cannot see either number, and the regional platforms price by tier without publishing the tier. You are expected to get on a call to learn a number. We publish it instead: Sandooq is 29 US dollars per month for a single store, and 79 for up to 5 stores. Billed annually those become 24 and 66. That is the whole price.

Where the money actually goes

Larger chains are quoted individually. Three things are worth saying out loud about that price.

• It is charged in US dollars, not riyals, and there is no Saudi rate. A restaurant in Riyadh pays what a shop anywhere else pays. The riyal's peg makes the conversion trivial, which removes the last excuse for a vendor quoting an SAR figure that sits quietly above their home-market rate. We would rather show the dollar number and let you do the arithmetic.
• What is included is the whole back office, not a starter tier that upsells: inventory with stock counts and transfers between branches, purchasing and supplier orders, customer accounts and on-account balances, staff permissions per branch, and the sales and closing reports your accountant needs. The plan boundary is scale — stores, staff, products — not features you discover are missing in month two.
• Hardware is yours, not ours. Sandooq runs in the browser on tablets and standard computers, works with commodity ESC/POS receipt printers and USB or Bluetooth barcode scanners, and does not require a proprietary terminal. If you already have counter hardware, the likely outcome is that it works; confirm the specific models during setup rather than taking a compatibility promise on trust.

And the honest counterweight, since we are being plain about money: a published price is worth less than the right product. Read the tax section again before this one persuades you.

Selling when the network drops

Saudi connectivity is good, so this section is short and specific rather than dramatic. The failure you will actually meet is local and timed: mall network maintenance windows, and the load that arrives when a whole district sits down to eat at the same minute in Ramadan. The counter experience is the same either way — a reader thinking, a queue building, a customer waiting, and in a restaurant a kitchen going quiet behind them. Here is precisely what Sandooq does and does not do about that.

What keeps selling when connectivity dips

• What keeps working. The checkout loop: building a cart, attaching a customer, and taking a cash sale. Those are captured on the terminal and queued locally. When the connection returns the queue replays in order, with deduplication on the server, so queued sales aren't lost and nothing gets double-counted from a retry.
• What needs the network. Signing in, manager and device PIN checks, opening and closing a cash session, looking up an earlier receipt, voids, exchanges, and card payments. These are online-only by design — each one either moves money through a third party or changes control state the server has to arbitrate between terminals.
• The practical shape of that, for a Riyadh counter through an iftar rush: open the session before service, and a drop mid-shift does not stop cash checkout. Reloading the browser tab while offline will sign the cashier out, so don't. Take card payments and process returns when the connection is back.

Restaurants first, and the shops next door

Nearly everyone who reaches us from Saudi search is asking about food and beverage, so this section starts there rather than pretending to be a general guide.

What the shop next door needs from the same engine

• For shops and minimarkets, the parts that decide whether a system survives contact with a real store are inventory accuracy and control: barcode-driven checkout, stock counts that reconcile without closing the shop, transfers between Riyadh, Jeddah and Eastern Province branches with a full audit trail, purchase orders that land back in stock levels rather than in a spreadsheet, and per-branch permissions so a branch cashier does not see chain-wide margin.
• For tender tracking, cash, card-style tenders, and on-account payments are broken out separately in the daily report so the drawer reconciles and accounting gets clean numbers. We do not name acquirer integrations that are not product-backed, and you should be sceptical of any Saudi page that lists a wall of processor logos without saying what "supports" means.
• On bilingual operation, which in Saudi service is an operational requirement rather than a preference: a floor here routinely runs Saudi and expatriate staff on the same shift. Staff read the interface in whichever language they think in, switching per session without restarting. Receipts print in Arabic, English, or both. A layout that reads right to left is the default the product was built around, not a mirrored afterthought.