Cloud based point of sale in Saudi Arabia: what to check first

A cloud based point of sale keeps your menu, prices and sales on a server instead of on the machine at your counter. You reach it from a browser or an app, and your data is not trapped in one box.

In Saudi Arabia there is a second question that comes before any feature list: does it satisfy the invoicing rules. This guide covers that first, then what the software actually does, then the jobs it will not do at all.

What "cloud based" really means here

The word gets used loosely, so it helps to have a fixed definition. The US standards body NIST defines cloud computing around a few properties, and the ones that matter to a restaurant are simple: you get the service on demand, you reach it over a network from any device, and the supplier pools the underlying machines so you never see them.

In practice that means three things for you:

• Your prices live in one place. Change a price once and every screen has it.
• Your sales are readable from anywhere, not only from the machine at the counter.
• If the machine at the counter breaks, your data did not live inside it.

That last point is the real reason to prefer it. Older systems kept everything on the terminal, so a failed hard drive was a lost month.

The invoicing question comes first

Saudi Arabia runs a national e-invoicing programme, and ZATCA publishes the requirements itself. Any system that issues your invoices has to meet them.

This is where a shortlist gets short. Ask each supplier three things, in writing:

1. Is the invoicing part certified, and can you see the certificate rather than a claim on a slide?
2. Who is responsible when the format changes: them, or you?
3. What happens to invoices already issued if you leave?

Do not accept "it is compliant" as an answer. Compliance is a document, not an adjective. A restaurant pos system that cannot produce the paperwork is not a shortlist candidate, however good the screens look.

We are direct about our own position because it saves you time. Get Menu does not issue your tax invoices to ZATCA and is not sold as a compliance product. It is the ordering and customer layer that runs beside whatever certified system you use.

What the counter software will never do

A counter system serves the person standing at the counter. It does not put your menu in the hand of somebody sitting at home in Riyadh at 9 in the evening. It does not send that person anything. It does not remember them next week.

"Owners ask for a system that does everything, then find the everything is thin in the parts they actually needed. The counter and the customer are two different jobs."

— Tanzeel ur Rehman, co-founder of Get Menu

Sold as restaurant management software, most boxes bolt a weak marketing module onto a strong counter module. The marketing half is usually the part you cannot leave later, because it holds your customer list.

The layer that handles the orders you do not see

This is the part we build, and it needs no hardware:

• Your own ordering page. A web address that is yours, with your menu on it, live from the first day.
• A QR menu for the tables and the window, printed from a designer so it suits your room.
• Table numbers that route themselves. The code says which table it came from, so nobody writes it down.
• Orders into WhatsApp, typed by nobody. The customer gets a confirmation, the kitchen gets a ticket, and a delivery rider gets a link carrying the map pin dropped at checkout. That is 3 messages in about 2 seconds.
• Live stock. Counts fall as orders arrive and a dish greys itself out at zero, so nothing sells after it runs out.
• Group ordering. Everybody at a table orders from their own phone and it lands as one bill.
• Loyalty that runs itself. Stamps per order, per riyal spent, or on one chosen dish, growing into tiers that carry their own automatic discount. The card sits in the phone wallet with no app to install.
• Coupons, upsells and bundles, each with caps, exclusions and expiry dates, and no two automatic discounts ever stack.
• Your menu imported from a spreadsheet, so you are not retyping two hundred items to start.

What it costs against the delivery apps

A delivery marketplace takes a share of every order it sends you, on orders that often come from people who already knew your restaurant. A flat monthly subscription with no commission changes that shape completely, because your tenth order in a night costs the same as your first: nothing extra.

Current pricing lives on our pricing page rather than in this article, since a number written into a guide goes out of date quietly. The trial is 15 days and takes no card, which is enough time to run a real weekend through it.

How customers pay

Cash, or your own card machine at the door or the table. There are no online payments anywhere in the system.

That is a deliberate limit and it has one large benefit worth saying plainly: no card details exist in the system, so none can be stolen from it. Old order details are cleared automatically after 120 days.

What to test in the first fifteen days

Do not test the demo. Test your own Friday.

Load your real menu, including the awkward items with three required choices. Put a code on two tables and let staff use it during service. Let stock run to zero on one dish on purpose and watch it grey out. Send yourself a delivery order and open the rider link. Then look at the sales split on Monday and see whether it tells you something you did not already know.

Frequently asked questions

Is a cloud based point of sale automatically ZATCA compliant?

No. Being in the cloud says where the software runs, not whether its invoicing meets the rules. Ask for the certification document and check who is responsible when the format changes.

Is Get Menu a restaurant pos system?

No. It does not run a cash drawer, a card terminal or your end of day, and it does not issue your tax invoices. It is the ordering, menu, stock and loyalty layer that runs beside the system you already have.

How do customers pay?

Cash or your own card machine, taken the way you take payment now. The software carries the order and the messages and never touches the money.

Can a small cafe in Riyadh run this alongside its existing counter system?

Yes, and that is the normal setup. Nothing is replaced. Your counter keeps doing what it does, and the ordering page handles the orders that never reach the counter.

What happens to my customer list if I leave?

You export it, on any day, including the last one. It is your list.