POS food systems: what changes when you sell meals

A pos food system is a counter system built for a kitchen rather than a shop. It sounds like a small distinction and it is not.

A shop sells a thing that already exists. A restaurant sells a thing that has to be made, from stock that goes off, with choices the customer makes at the moment of ordering. Every one of those three differences breaks something in software built for retail.

Where a shop system breaks

Stock that is a recipe, not a shelf. A shop sells one unit and has one fewer. A kitchen sells a chicken sandwich and has less bread, less chicken and less of one sauce. Most food point of sale products handle this at the finished-dish level only, which is fine as long as you remember to update it. Nobody remembers on a Friday.

Choices made at the counter. Retail has variants set in advance. Food has decisions made in the moment: no onions, extra sauce, make it large. If a choice is a free-text note rather than a priced option, two things happen. Somebody forgets to charge for it, and the kitchen gets a sentence instead of data.

Time. A shop transaction ends at payment. A restaurant order starts at payment: the kitchen has to know, the ticket has to be right, and somebody has to carry it. A system that ends at the receipt has done about half the job.

The Saudi part, which comes first

Before any of the above matters, the invoicing has to be right. ZATCA publishes its e-invoicing requirements and its VAT rules directly, and whichever system issues your invoices has to meet both.

Ask each supplier for the certification document rather than a claim, ask who is responsible when the specification changes, and ask what happens to invoices already issued if you leave. A restaurant pos system that cannot produce the paperwork is not on your shortlist, whatever its screens look like.

We are clear about our own position so nobody wastes a meeting: Get Menu does not issue your tax invoices to ZATCA and is not sold as a compliance product.

What the counter never sees

Your counter serves the person standing at it. It does not see the family ordering from home at eight in the evening, and it never has.

"The counter is the part owners can see, so it is the part they buy. The orders they cannot see are the ones being lost, and those never appear on any counter report."

— Tanzeel ur Rehman, co-founder of Get Menu

That second half is a separate layer, and it needs no hardware:

• WhatsApp handles the talking: confirmation to the customer the moment the order is placed, ticket to the kitchen, link with the pin dropped at checkout to the rider. 3 messages in about 2 seconds.
• The stock counts down by itself on items and on options, and a dish at zero disappears before anyone can order it.
• Stamps and tiers for your regulars, automatic discounts attached, the card in the wallet through Google's loyalty card format and no app to install.
• Invoices carrying your registration number, which the customer can download as a PDF without an account.
• A code on each table, designed to look like yours, with the print pack emailed to whoever prints it.
• Table numbers travel with the code, which means a waiter never has to ask twice where an order goes.
• Your colours and logo on the wallet card, set in a designer, and the card updates itself as stamps land.
• Coupons with exclusions and expiry dates, upsells, and bundles at a fixed price, and two automatic discounts never stack.
• A branded page, not a listing: 12 page layouts so the menu reads as yours, and a link you can put anywhere.
• Sizes, sauces and extras each with their own prices, required choices enforced, and you make the edits yourself.
• Priced at the moment of checkout, every line, from the menu as it is now rather than as it was when the page opened.

What to ask a supplier, in order

Most demos are structured to show strengths. These four questions are structured to find the edges, and they are worth asking in this order.

1. Show me a dish with three required choices being ordered. Not a coffee. A dish where the customer must pick a size, a sauce and a side. Count the taps and watch what reaches the kitchen ticket.
2. Make an option run out during the demo. Not the dish, the option. Then try to order it. If it is still selectable, you have found the thing that will cost you at nine in the evening.
3. Change a price while I watch. Then ask what that costs if they have to do it, and whether you are permitted to do it yourself.
4. Export my sales and my customers, now. If the answer involves a ticket, a fee, or a format nobody can open, your data is in their custody rather than yours.

A supplier who answers all four plainly is telling you something real about how the next three years will go.

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 real limit and it is worth weighing honestly. It rules out prepayment. In exchange, no card details exist in the system, so none can be taken from it, and old order details are cleared automatically after 120 days.

What the trial is for

The trial runs 15 days and takes no card, which is enough to answer the only question that matters: does this remove work on your worst evening, not your quietest one.

Load your real menu, including the dishes with three required choices. Put a code on two tables during a genuine service. Let one dish run to zero deliberately. Take one delivery order yourself and open the rider link on a phone. Then look at what the sales split tells you on Monday.

Current pricing is on the pricing page rather than in this article, because a figure written into a guide goes quietly out of date.

Frequently asked questions

Is a food point of sale different from a normal retail system?

Yes, in three ways that matter: stock behaves like a recipe rather than a shelf, choices are made at the moment of ordering rather than set in advance, and the transaction does not end at payment because the kitchen still has to make it.

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 beside the system you already have.

Does being in the cloud make a system ZATCA compliant?

No. Where the software runs says nothing about whether its invoicing meets the rules. Ask for the certification document.

How do customers pay?

Cash or your own card machine when the food arrives. The software carries the order and the messages and never touches the money.

What happens to my customer list if I leave?

You export it yourself, on any day, including your last one.