POS for restaurants in Saudi Arabia
Last reviewed 2026-05-26 · by the RetailPOS team
Saudi Arabia is the second-largest restaurant market in the GCC by revenue, growing roughly 8% a year on the back of Vision 2030 tourism + entertainment investment. The POS market that serves it has two distinct halves — international chains running Oracle Micros or Toast, and independents running a mix of regional players (Foodics, Marn, Posista) plus a long tail of legacy Windows systems.
The buying decisions in KSA differ from neighbouring markets on two big axes: ZATCA's e-invoicing mandate (Fatoorah, now in Phase 2 for all VAT-registered businesses) and Mada — the domestic card network that processes the majority of in-person card sales. This guide is for owner-operators of independent restaurants — counter shops, casual dining, ghost kitchens, multi-brand groups — making the POS choice with both constraints front of mind.
ZATCA / Fatoorah Phase 2 is non-negotiable
All VAT-registered businesses in Saudi Arabia are now required to integrate their POS with ZATCA's e-invoicing system (Fatoorah Phase 2). Each invoice gets a QR code, a UUID, and a cryptographic signature; the data submits to ZATCA in near-real-time via their API. Non-compliance penalties start at SAR 5,000 and escalate.
The integration is technical: device certificates, CSR generation, invoice signing, real-time clearance API calls. Most international POS systems (Square, Toast) don't support it natively. Regional players (Foodics, Marn) do. RetailPOS' integration ships via our connector layer; the certificate provisioning + ongoing compliance is part of the onboarding.
The question to ask any POS vendor: “Do you have a ZATCA-certified integration today, or is it on the roadmap?” “On the roadmap” is a hard no — the penalty for non-compliance accrues per day.
Mada — the domestic card network
Roughly 80% of in-person card transactions in Saudi Arabia route through Mada (the domestic card scheme). Visa + Mastercard handle the rest, primarily on higher-end cards and tourist transactions. A POS that doesn't route Mada natively forces you to take Mada cards through a generic Visa/Mastercard rail, which costs 0.5-1.0% more in interchange than the direct Mada rate.
Common processors with native Mada routing: Tap Payments, Foodics Pay, Geidea, Hyperpay, Payfort (now Amazon Payment Services), MyFatoorah. Stripe is available in KSA but routes Mada via card-network rails (no direct domestic settlement yet as of 2026).
For a typical independent restaurant doing SAR 200,000/month in card volume, the difference between a Mada-native processor and a generic rail is SAR 1,000-2,000/ month in saved interchange. Worth the integration effort.
VAT + ZATCA + the tip workflow
KSA VAT is 15% on most restaurant services. The POS must charge it, line-item it on the receipt, file it through Fatoorah. Tax-inclusive vs tax-exclusive on the menu varies — both are common.
Tips are technically not VAT-able if voluntary. The POS should distinguish a voluntary tip (no VAT) from a mandatory service charge (which IS subject to VAT). Some POS systems collapse the two into one “gratuity” field; that's an audit risk. Pick a system that tracks both separately + flags them correctly on the e-invoice.
Working hours, Ramadan + Hajj
Saudi restaurant hours typically run 11am-12am, with peak dinner traffic 8pm-11pm. During Ramadan, daytime closes; iftar service from sunset to ~midnight; suhoor from 2-5am for some shops. The POS needs to handle the shift in operating hours + menu (iftar-specific items) cleanly.
Hajj season (varies by Hijri calendar) brings dramatic traffic shifts in Makkah + Madinah specifically — pilgrim traffic peaks for 5-10 days, restaurants run extended hours, ticket sizes shift. Outside the Holy Cities, Hajj has minimal traffic impact.
Saturday is the weekend (along with Friday in Saudi Arabia's 2013-onwards calendar). Thursday + Friday + Saturday are peak; Sunday is low. POS reports should respect this weekly rhythm — “Mondays are slow” is a North American assumption that doesn't apply.
Multi-brand groups + ghost kitchens
A common structure in Saudi food is one operator running 4-8 brands out of a shared kitchen — burgers under one brand, shawarma under another, dessert as a third, all delivered via Talabat / Hungerstation / Jahez / Mrsool. The POS needs to handle multi-brand orders with per-brand reporting + the multi-aggregator channel mix.
Each aggregator has its own commission (usually 25-35%) + their own ordering API. The POS should integrate with all four major aggregators in KSA (Talabat, HungerStation, Jahez, Mrsool) so orders land directly in the kitchen-ticket flow rather than requiring manual re-entry on a separate tablet. Manual re-entry is where double-orders happen.
Saudization (Nitaqat) impact on POS workflow
Saudization quotas (under the Nitaqat programme) require restaurants to maintain a percentage of Saudi citizens in their workforce, with the percentage varying by business size. The POS should track staff demographics + hours worked per employee with citizenship status so the monthly Nitaqat report falls out of the normal payroll flow.
This isn't a POS feature most international systems support; it's a workflow your HR + payroll system handles. The POS's role is honest timekeeping per shift — opening, closing, breaks — so the data feeds whichever HR tool produces the Nitaqat-compliance numbers.
Hardware supply — Riyadh, Jeddah, Khobar
iPads + tills: Apple stores in Riyadh + Jeddah + Khobar + Dammam carry stock. Refurbished iPads through Jarir Bookstore are common + reliable.
Card terminals: Geidea + Foodics Pay + Tap ship Mada-enabled terminals at sign-up. Verifone + Ingenico available through enterprise resellers in Riyadh; required for restaurants needing PIN-debit handling beyond Mada contactless.
Printers + scanners: Star Micronics + Epson distributors operate from Riyadh + Jeddah industrial zones; lead time is 2-4 days. Common alternative is buying via Souq / Amazon SA with 1-2 day delivery.
Kitchen displays:Standard iPad mounted on the line works; the POS's KDS view is a web view, no specialised hardware needed.
Frequently asked
- Does the POS handle ZATCA Phase 2 e-invoicing?
- RetailPOS' integration with ZATCA Fatoorah ships through our connector layer. Onboarding includes the device-certificate provisioning + the ongoing real-time clearance flow. Confirm the integration is live at sign-up; non-compliance penalties accrue daily.
- Can I route Mada cards natively?
- Yes — RetailPOS works with Tap Payments + Geidea + Foodics Pay for native Mada routing. Bring-your-own processor lets you pick the rate + scheme support that fits your card mix. Generic Visa/Mastercard routing on Mada cards costs 0.5-1.0% more in interchange.
- How does the POS handle Ramadan operations?
- Time-of-day menus + per-day schedule overrides let you preset the Ramadan hours (closed daytime, iftar service from sunset, suhoor from 2am for some shops). Configured once; runs all month. Outside Ramadan: standard 11am-12am operating hours.
- Can the till print receipts in Arabic?
- Yes — bilingual receipts (English + Arabic) print on Star + Epson printers configured for Arabic character sets. The till UI is currently English-only; Arabic UI is on the roadmap. For ZATCA compliance, the e-invoice itself is XML + the QR-code on the print receipt; the human-readable part is bilingual.
- Multi-brand ghost-kitchen support?
- RetailPOS treats each brand as a separate “sub-tenant” under one parent group. One kitchen, one POS, multiple brand menus + reports. Aggregator integrations (Talabat, HungerStation, Jahez, Mrsool) are in the connector layer; orders flow directly to the kitchen-ticket queue.
- What about Saudization / Nitaqat reporting?
- The POS tracks staff timekeeping per shift (open, close, breaks); the demographics + citizenship-status + monthly Nitaqat compliance number lives in your HR / payroll system. We export the timekeeping data in a format your HR tool consumes.
Open your shop in 30 seconds.
No card. Free until your first 100 sales. Bring your own Stripe; keep your hardware.