Restaurant POS in Saudi Arabia: What to Check Before E-Invoicing

Choosing a restaurant POS in Saudi Arabia takes more than finding a system that "supports e-invoicing". You need one that survives the lunch rush, closes the shift with the right numbers, and still issues a valid invoice every time. This guide looks at it from the operations side: what really happens between the table, the kitchen and the till, what ZATCA requires of your invoices, and how to test any vendor before you sign.

How is a restaurant POS different from a normal shop POS?

A restaurant order isn't one sale. It is a journey through several hands: cashier or waiter, kitchen, delivery platform or driver, then the till. A weak link shows up in front of the guest. So judge a system by what it handles at rush hour, not by its feature list.

A café is similar, with differences: fast repeat orders, drink customisation, loyalty cards, and a queue at the counter instead of tables. So ask first: where do I lose time or money today? Then choose the system that fixes that.

What do you actually need before e-invoicing?

You need to know whether and when your business falls into the integration phase, a system that can issue simplified invoices and report them to the platform, and every invoicing device registered under your VAT number. Those are the basics; the rest is implementation detail.

Phase 1, the "Generation" phase, started on 4 December 2021. It requires taxpayers to generate and store invoices through a compliant electronic solution, which ended handwritten invoices and ones made in word processors or spreadsheets, as ZATCA's roll-out phases page explains. Phase 2, the "Integration" phase, has applied in waves since 1 January 2023, and each wave is notified at least six months ahead.

The latest wave, announced on 24 July 2026, is Wave 25: any taxpayer whose VAT-able revenue passed SAR 187,500 in 2022, 2023, 2024 or 2025, with integration by 1 February 2027 at the latest, according to ZATCA's announcement. Many small restaurants and cafés fall in that range. Our guide to ZATCA e-invoicing Phase 2 covers the details.

Which invoice does your restaurant issue?

Most restaurant sales are to individuals, so you issue a simplified tax invoice. Your system stamps it, hands it to the guest on paper or electronically, then reports it to the platform within 24 hours of issue, per ZATCA's Detailed Guidelines for E-Invoicing. It must carry a QR code that meets Phase 2 requirements.

If a company orders meals for staff and wants an invoice in its name, that's a standard tax invoice: it is sent to the platform for real-time clearance before the buyer receives it. The same guideline lets you issue a simplified invoice to a business customer when the supply is under SAR 1,000. Ask your vendor: does the system handle both routes, and does it capture the buyer's VAT number when needed?

What changes in your daily routine?

• An issued invoice can't be deleted or edited. Cancellations and refunds go through a credit note. Train cashiers on the difference between voiding an item before the bill closes and refunding a paid invoice.
• Every invoicing device is onboarded: the dine-in till, the takeaway till and the waiter's tablet. List your devices before you call a vendor.
• Your VAT number and National Address must be correct in the system settings.

What happens to your orders if the internet drops at rush hour?

The system should keep selling and printing invoices, then send them when the connection returns. For a restaurant serving dozens of tables that isn't a luxury, and queues shouldn't form because the network wobbled.

ZATCA's guideline says a compliant solution must protect invoices from alteration and undetected deletion, and must let you save them in XML without an internet connection. The seller has 24 hours to report a simplified invoice, and one who can't must notify ZATCA through a dedicated form. So ask the vendor plainly:

1. If the internet goes down, do the till and the kitchen both keep working, or does one stop?
2. Are invoices sent automatically when the connection returns, and where do I see the ones still waiting?
3. What happens to kitchen tickets if the local server stays down?

If the system is cloud-based, check where your data is stored and what the rules require, as we explain in cloud and data hosting regulations in Saudi Arabia.

How should you handle delivery-app orders?

Record them in your system with their channel and commission, so they appear in your reports next to dine-in sales. If app orders live in a notebook or a separate spreadsheet, you'll never know your real margin per channel.

Ask the vendor whether orders enter automatically from the app or a staff member keys them in. Don't accept a vague "yes, we connect to every app"; ask to see a real order from the app you use, on the demo screen. And ask your accountant how the platform's commission and its invoice are booked, because that is an accounting decision a till can't make for you.

Do you need recipes and stock control from day one?

Not necessarily from day one, but choose a system that won't block you later. Knowing what each dish costs and how many ingredients you use is what explains why sales look good while profit is thin. Start simple: what does your real best seller cost you?

Ask the vendor three things: can a recipe be recorded for each item? Is stock deducted at the point of sale or only at stock-take? Does the system warn you when a key ingredient runs low? If today you rely on a manual count at the end of the week, start with an organised count of your ten main items, then widen it once operations settle.

Which hardware and costs should you ask about?

Ask every vendor for an itemised offer in writing and compare line by line. We won't quote generic prices here, since they vary with devices, branches and plan; what matters is that no line is hidden.

How do you test a vendor before signing?

Ask for a trial on your own menu, not a canned one, and bring your worst-case scenarios. Thirty minutes of this shows what an hour of sales presentation won't.

1. Enter five items with modifiers and notes, and see what reaches the kitchen.
2. Merge two tables, then split the bill three ways.
3. Void an item after it was sent to the kitchen, and see what the report records.
4. Issue a simplified invoice, then an invoice to a company with a VAT number.
5. Disconnect the internet, keep selling, then reconnect.
6. Close a shift with cash, card and a delivery order, and read the reconciliation report.
7. Change one item's price and see whether it changes in every branch.
8. Get the status of the Fatoora integration in writing: live today, in testing, or scheduled?

The last question matters because "ZATCA-approved" can be said in a pitch without meaning what you assume. Ask for proof and test it yourself before you contract.

Where does Manzomia fit in this list?

Manzomia is our Arabic cloud system from Manzomia Digital Solutions. Its point-of-sale module is live today, and more modules are launching soon. Integration with Fatoora is "coming soon" and has not shipped, so we ask business owners to tell us their mandated date and we tell them honestly whether our system fits it. The Restaurant Management System page shows what it covers today.

What should you do next?

Before you call any vendor, write down three numbers: how many devices issue invoices, how many branches you run, and your mandated integration date. If your VAT returns are not up to date, start with our VAT return filing guide, because your VAT-able revenue decides your wave. For other kinds of business, we have matching guides to a POS for paint and hardware stores and to laundry software.

Manzomia is a foreign-owned, MISA-licensed company in Riyadh, and our founder has more than nine years of experience building web and mobile products. If you'd like to see Manzomia on a menu like yours, book a free demo or write to us through the contact page.