QR restaurant: what the square has to do after somebody scans it

The code is printed, laminated and sitting on all 14 tables. Guests scan it, look at a photograph of your menu, put the phone face down and wait for somebody with a notepad. Service did not get quicker, the queue at the cash register did not get shorter, and what you actually bought was a laminated card with a pattern on it.

What is a QR restaurant?

A qr restaurant is one where the printed code works as the ordering counter rather than as the menu display. A guest scans, builds a basket on their own phone, and the order reaches the kitchen with nobody retyping a line of it.

The difference is invisible from the guest's side until they try to order something. Two cafes on the same Doha street can print identical squares. Behind one sits a PDF in a cloud drive; behind the other sits a storefront that holds a basket, watches its own stock and writes its own kitchen ticket. The restaurant qr sticker costs the same in either case. What waits at the far end of the link decides whether it ever repays the print run.

A blunt way to judge one: a display code answers questions, an ordering code removes work. If your staff still walk to the table, write, walk to the pass and read it out, the code is decoration.

What has to sit behind the code?

Behind the code there has to be a storefront that can hold a basket, price it against your live menu, and hand it on to the kitchen. Anything less is a menu board with extra steps between the guest and the food.

On Get Menu that storefront is a web address of your own (yourname.getmenu.ae, included with every plan) laid out in whichever of the 12 page layouts suits how your menu reads. A photo style toggle helps kitchens whose dishes photograph badly under fluorescent light. Options and add-ons carry their own prices, required choices stop a shawarma reaching the pass without a sauce decision attached, and the cart takes a name and number before checkout so the ticket has somebody to belong to.

The menu behind it is edited once and arrives everywhere at once. Move a price at four in the afternoon and the code on table nine shows the new price at four in the afternoon, while the card on the table never learns anything happened. Arabic item names sit beside the English ones, which in Doha is not a decoration either.

Where should the codes actually go?

Four places earn a code in a working QR restaurant, and each one asks something different of the storefront: the table, the shopfront window, the delivery bag, and the link in your Instagram bio.

The table code is the strict one: a code generated for every table, so the order carries its own seat number and the runner never has to ask whose food this is. A designer matches the card to your own colours and logo, and the finished pack arrives ready for the printer instead of as a folder of images somebody has to lay out at midnight.

The window code serves the passer-by deciding whether to come in: the same menu with no table attached, opening hours enforced so it politely declines an order twenty minutes after close rather than taking one nobody will cook. The delivery-bag code is the reorder code, and it reaches the customer at the exact moment they liked you most. The bio-link code does acquisition, and it is the only one of the four you can re-aim without printing anything.

What happens in the two minutes after a scan?

Every line is re-priced against your live menu at checkout. Then 3 messages leave inside roughly 2 seconds: a confirmation to the customer the moment they order, a ticket into the managers' WhatsApp group, and a dispatch to the riders' group carrying the pin. None of the three is typed by a person. They ride WhatsApp because that is where a Doha kitchen already looks; Meta's own developer overview describes order updates as exactly the kind of message the platform exists to carry.

Underneath that, a set of small refusals does quiet work. A double tap cannot create a second order. Stock counts per item fall as orders come in, and counts run per option too, so running out of one sauce does not drag the whole dish off the board. A minimum order value keeps the loss-making solo delivery from ever reaching the kitchen at all. The guest gets a status page for their own order with no login needed, which is the cheapest favour you will ever do your phone line.

When the kitchen is buried, an auto-confirm timer answers on your behalf rather than leaving somebody staring at an order nobody has acknowledged.

Does a code work for delivery, or only for tables?

Both, off the same menu. The delivery checkout swaps the table for a GPS pin the customer drops themselves, plus the building and unit picked from a list you maintain. The delivery fee is set per building, with free delivery above whatever threshold you choose.

That list matters more in Doha than in most cities. Qatar runs an official national address system through the Ministry of Interior. Tower names still repeat all the same, entrances face different streets, and a rider phoning from the wrong lobby costs you a quarter of an hour and a cold order. Riders work from a link that needs no account of any kind: one tap marks the run complete, the customer is told, and the link stops working once the job is closed.

What does this cost against a delivery app?

The sums are the whole argument. Marketplace commission across the Gulf generally lands between 25% and 30%: QAR 80,000 of orders in a month at 28% is QAR 22,400 gone before rent, wages or gas. And the number of every customer who ordered stays with the app rather than with you.

A storefront you own inverts that shape. The fee is flat and monthly, commission is 0%, and the customer list belongs to your restaurant to export whenever you want it, including on the day you decide to leave. Current figures sit on the pricing page rather than in an article that would go stale at the next plan change.

"The apps are genuinely excellent at one job, which is finding you a stranger. What we kept watching in Dubai and Doha was restaurants renting that introduction forever. They were paying commission on the eleventh order from someone who would happily have scanned the code on the bag."

— Anzul Aqeel, founder of Get Menu

Marketplaces keep their place for discovery. The question worth asking is what share of your regulars you are renting back each month.

How does one scan become a second visit?

The scan is where retention is cheapest, and it is where most rollouts stop. A guest who ordered from the table has already handed you a name and a number; the work left is giving them a reason to scan again next Thursday.

Stamps count automatically (per order, per riyal spent, or only on the dish you are trying to move) and nobody has to mark an order delivered for one to register. Tiers give regulars an automatic discount they grow into instead of a code they have to remember, and streaks reward the guest who comes back week after week. The card itself drops into the wallet already on the phone, styled through a designer with your own colours: Google Wallet works today, and the Apple version is built and waiting on a certificate. Nothing is installed at any point.

Around that sit the promotions you choose to switch on. Coupons with caps, exclusions and expiry dates; bundles priced as a set; a nudge to the basket somebody abandoned; win-backs for the regular who has gone quiet for a month. Discounts never stack by accident, because the best single one wins.

What does the office get out of it?

Invoices come out in one unbroken sequence, carrying your tax registration number where you hold one. The customer can download the PDF without logging in, and the total is the sum of its printed lines every single time.

Behind them is a sales dashboard by day, item and channel, which is how you find out whether the window code or the bag code is actually earning its ink. An export to a spreadsheet is there whenever your accountant asks. Detailed order contents clear themselves after 120 days while the sales history stays, so the books survive and the personal data does not linger.

Frequently asked questions

Do guests need an app to use a restaurant QR code?

No. The code opens an ordinary web page in the browser already on the phone. Loyalty cards go into the Google Wallet or Apple Wallet that is also already there, so nothing is downloaded and the guest creates no account.

How do customers pay at a QR restaurant?

Cash, or the card machine your staff already carry to the table or the door. There are no online payments in the system, which also means no card details exist anywhere in it for anybody to steal.

Can one code cover both dine-in and delivery?

Not one code, but one menu. The table code adds the seat number and the delivery link adds the pin and the building. Both read the same items, prices and stock, so a dish that sells out vanishes from every entrance at the same moment.

What is the difference between a qr code menu and a QR menu for restaurants that takes orders?

A display menu shows, an ordering menu acts. The display version cannot know the table, cannot run out of a dish and cannot tell the kitchen anything, while the ordering version does all three and needs no reprint when a price moves.

How long does it take to switch a QR restaurant on?

Most kitchens are taking orders the same day, and faster still if the menu already exists in a spreadsheet that can be uploaded in one pass instead of typed item by item. The trial runs 15 days and asks for no card details to begin, which covers two real weekends of service.