Cloud point of sale system: what it does for a UAE restaurant

Restaurants in this country usually move to a cloud point of sale system for one of three reasons. A second branch opened and the numbers stopped adding up. The accountant asked for something the old machine could not produce. Or the machine behind the counter died and took the week with it.

All three are good reasons, and a cloud register solves all three. It also leaves something untouched, and for most restaurants here that untouched part is bigger than the part it fixes. This guide covers both halves honestly.

What the word is doing in that phrase

There is a published definition rather than a marketing one. NIST wrote it down, and the short version is that a genuine cloud service is available on demand, over a network, on shared infrastructure you never see or maintain.

For an owner it reduces to one test. If the machine at your counter died tonight, what would you have lost? With a real cloud pos the answer is the hardware and nothing more, because your menu, your prices and last week's sales were never inside it.

Where your orders actually start

Now walk through a normal Tuesday evening in a Dubai restaurant and count where the work arrives from.

Some orders come from people sitting at your tables. Those reach the counter, and the register handles them properly. Some come through a delivery app, which lands on its own tablet on a shelf and has its own rules. And a large share arrive as WhatsApp messages, typed by a customer at somebody who is holding a pan at the same time.

That third group is the one nobody bought software for. WhatsApp is not a workaround in this market, it is the front door, and the messaging platform is documented and built for exactly this kind of use. A restaurant pos system will never see any of it, because it was designed for the person standing in front of it.

"A cloud register is a good register. It still only knows about the customer standing at it. The ones on WhatsApp are invisible to it, and they are the ones who order twice a week."

— Tanzeel ur Rehman, co-founder of Get Menu

Three things that go wrong outside the room

The counter screen is not failing at these. It was never asked to do them.

The order arrives wrong. A message is a sentence, not a form. Somebody has to read it, decide what was meant, remember that one of the choices is finished, and type it into the kitchen.

The address costs a phone call. Which tower, which entrance, which flat, and what the delivery fee is for that building. In a city built vertically this is the single most repeated conversation of the evening.

The customer disappears. A regular who ordered every Thursday for a year stops, and there is no way to know, because the person who stopped coming is by definition not standing at your counter.

What we build for those three

None of it needs hardware, and it runs beside the register you already own.

For the order. You are given an ordering page that belongs to you, and 12 page layouts, so the menu reads as you intend. You edit it yourself: options and add-ons carry their own prices, and required choices have to be made before an order can go through, so the ticket the kitchen sees is complete. A long menu comes in from a spreadsheet in one go. Every line is priced again at checkout from the live menu, so a page somebody left open at lunch cannot sell at lunch prices. Stock counts on items and on options fall as orders arrive, and a dish greys itself out at zero.

For the address. Delivery fees are set per building, so a tower with its own rate and its own minimum is handled at checkout instead of on a call. When the order is placed, three messages send themselves: a confirmation to the customer, a ticket to the managers' group, and a link to the riders' group carrying the GPS pin dropped at checkout. In about 2 seconds, 3 messages have gone out. For the tables, each QR code carries its own table number, is made in a designer so it matches your room, and arrives as a print pack by email. A group can order from several phones onto one bill.

For the customer. Every order carries a name and a number, so a list builds itself. Stamps accrue from the order, tiers your regulars grow into carry their own automatic discount, and the card sits in the phone's wallet with no app to install and a designer for its colours and logo. Coupons, upsells and fixed-price bundles come with caps, exclusions and expiry dates, and two automatic discounts never land together. Tax invoices carrying your TRN are downloaded by the customer as a PDF without logging in, and sales can be read by day, by item and by channel.

What changes on a normal week

Your counter carries on doing exactly what it does. What changes is that orders arriving from outside the room stop depending on somebody being free to answer.

The second change is slower and larger. Once every order carries a customer, you have a list, and a list can be asked a question the register has never been able to answer: who used to order and does not any more. That is the whole basis of winning somebody back, and until the list exists it cannot be attempted.

How customers pay, and what that rules out

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

Two things follow. It rules out taking money before the food arrives, which some restaurants want and should know now rather than later. And it means no card details exist in the system for anyone to steal. An order's details clear themselves at 120 days, so what is stored shrinks by itself.

Our pricing sits on the pricing page rather than in this guide, because a figure written into an article goes quietly stale. There are 15 days to try it, and no card is asked for. If you want the plain version of what a register does and does not cover, start with our restaurant POS guide, and the QR menu guide covers the table side.

Frequently asked questions

Is Get Menu a cloud point of sale system?

No. It runs no cash drawer, no card terminal and no end of day. It is the ordering, menu, stock and loyalty layer that sits beside the counter system you already have.

Do I still need a counter system?

If people pay you face to face, yes, keep it. This handles the orders that never reach the counter, which in most UAE restaurants is a large part of the evening.

Can customers pay on the website?

No. Payment is cash or your own card machine when the food arrives. It is a deliberate limit, and the benefit is that no card details are stored anywhere in the system.

Does a cloud system keep working if the internet drops?

The counter side depends on the supplier's offline mode, so ask for the limit in hours. The ordering side needs a connection by its nature, because the customer is placing the order from somewhere else.

What happens to my customer list if I stop paying?

It is yours, and you export it on any day, including the last one.