Do you need a POS machine for restaurant service?

The quote says four units. One for the counter, one for the pass, two for the floor. Nobody in the meeting questions the number, because the number came from the supplier and the supplier has seen a lot of restaurants.

That number is the most expensive line in the whole decision, and it is the one worth arguing about. A pos machine for restaurant use is a screen, a drawer, a printer and usually a card reader. It rings up an order, takes payment and prints a receipt. This guide is about how many of those you actually need, what the UAE rules ask of them, and the orders none of them will ever see.

The one machine you should not argue about

If people pay you face to face, buy the machine. Something has to open a drawer, take a card, print a receipt and add up the day, and that is exactly what it is for.

Buy a good one, put it where the money is, and stop reading comparison tables about it. The counter is a solved problem.

The machines after the first one

Now split the rest of the quote into two piles.

Pile one: money changes hands here. A second counter, a takeaway hatch with its own cash drawer, a bar that closes its own day. These are real. Each of them has a physical job that needs physical hardware.

Pile two: an order is taken here. Everything bought so the floor can send an order without walking to the counter. That is the pile that doubles a quote, and it is a pile of devices you may not need to buy at all.

Every guest at every table is already holding a screen. It is charged, it is cleaned, it is replaced at their expense rather than yours, and nobody has to be trained on it. A table that orders for itself needs no stand, no cable, no licence and no spare unit in a cupboard.

That is not an argument for buying none. It is usually an argument for buying fewer than the quote assumes, and spending the difference on the part of the business a counter has never been able to see.

What the UAE asks of your invoices

Whatever system issues an invoice has to hold up when somebody asks to see it. The Federal Tax Authority publishes its guidance on tax invoices, including the full guide as a download, and that is the standard your supplier should be working to.

Do not accept a slide on this. Ask to see one real invoice their system produces. Check your TRN is printed on it. Check the VAT is shown separately. Then ask to reprint one from three months ago without ringing support. These are dull questions and they are the ones that matter on the day somebody audits you.

The orders the machine will never see

A point of sale machine for restaurant service is built for the person standing in front of it. It cannot show a menu to somebody at home, it cannot confirm anything to a customer who is not in the room, and it cannot notice that a regular has stopped coming.

In this country the customers it misses mostly arrive on WhatsApp, typing at somebody who is also cooking. That is not a workaround, it is the channel, and the messaging platform is documented and built for business use.

"Restaurants here buy a machine for the customers who walk in, then lose the evening to the ones who message. The machine was never wrong. It was just answering a different question."

— Anzul Aqeel, founder of Get Menu

What pile two was supposed to buy you

Look again at what the extra terminals were for: taking an order somewhere other than the counter, getting it to the kitchen correctly, and finding the customer afterwards. Here is how that works without hardware.

Taking the order. Each table is given a code of its own, drawn in a designer so it matches the room instead of looking like a parking sticker, and the finished print pack is emailed over ready for a printer. Because the code belongs to the table, the ticket knows where the food is going. Six friends at one table can order from 6 phones and still be handed a single bill. The setup is covered in our QR menu guide.

Getting it right. You look after the menu yourself from a browser. Each add-on and each option has a price of its own, and a choice marked as required has to be made before checkout will run, which is what stops the kitchen guessing. A long menu is uploaded from a spreadsheet in one pass.

Charging correctly. At checkout the whole basket is priced again from the menu as it stands right now, so a page opened before lunch cannot sell at before-lunch prices. Counts run down on items and on options as orders land, and a dish that reaches zero greys itself out instead of being sold a second time.

Telling everybody. The customer is confirmed, the managers' group receives a ticket, and the riders' group receives a dispatch with the GPS pin the customer dropped. All 3 messages are gone in about 2 seconds, and nobody typed a word of them.

Finding the address. A delivery fee is set for each building, so a tower and a villa are charged their own rates, and your rider opens a link that needs no account.

Keeping the customer. A stamp is earned by the order rather than by anybody at a counter. Regulars grow into tiers, each carrying its own automatic discount, and their card lives in the wallet already on the phone through Google's loyalty card format. Upsells, coupons and fixed-price bundles all take caps, exclusions and an expiry date, and only the better of two automatic discounts is ever applied.

Producing paper. A tax invoice carrying your registration number is available for the customer to download as a PDF, with no account, alongside whatever your counter prints.

Getting the real number out of a quote

Ask for a two year total rather than a monthly figure, and make sure it includes the second machine, the installation visit, and a call-out when the menu changes shape.

Then ask three questions. What does a price change cost if the supplier has to make it, and may you make it yourself? What is the notice period? And how do you get your sales history and your customer list out, by yourself, on any day you choose?

The delivery marketplaces are the other cost worth writing down. They take a cut of every order, including orders from people who already knew your restaurant and would have called you anyway. Your own ordering page takes no commission on your sales.

What we charge is kept on the pricing page, where it can be updated, rather than in a guide that ages. You get 15 days to try it and nobody asks for a card, which covers two real weekends of service. If you are still working out what the counter software itself should do, our plain guide to a restaurant POS covers that side.

How customers pay

Customers pay you, not the software. Notes, or a tap on your own reader, when the food reaches them. Nothing is ever charged through the website.

That is a deliberate limit and it buys you something worth naming. There are no card numbers held anywhere in the software for anyone to steal, and the system throws away order details once they pass 120 days.

Frequently asked questions

How many terminals does a small restaurant really need?

Usually one per place where money physically changes hands. Terminals bought only so an order can be taken away from the counter are the ones worth questioning, because your guests are already holding screens.

Is Get Menu a point of sale machine for restaurant use?

No. There is no machine at all. It runs in a browser, drives no drawer and no card reader, and sits beside whatever you already own.

Will it produce a UAE tax invoice?

It produces a VAT invoice carrying your TRN that the customer downloads as a PDF. Check the Federal Tax Authority guidance against what your counter system issues too, since most receipts start there.

How do customers pay?

They hand over cash, or tap on the reader you already own, at the moment the food reaches them. The order travels through the software, the money does not.

Can I use it across two branches?

Yes. Each branch keeps its own menu, hours and delivery area, staff see only their own outlet, and the owner sees both side by side.