Home / Blog / Scan menu QR code: what happens in the next two seconds

Scan menu QR code: what happens in the next two seconds

The scanning is the easy part. Everything that matters happens after it, and most restaurants have never decided what that should be.

· Founder & Director, Anunzio International FZC · 2 September 2026

A guest sits down, points a phone at a small printed square, and a page opens. That is the whole interaction, and it takes about 2 seconds. This article is about what should be on the other end of it, because the square is not the product. The page it opens is.

Most restaurants get the first half right and stop. They print a code, stick it on the table, and the code opens a picture of the paper menu they already had. The guest pinches and drags to read a price. Then they put the phone down and wait for a waiter, which is exactly where they were before the code existed.

What the code itself is doing

A QR code is a printed pattern that holds a web address. The phone camera reads the pattern and opens the address. Nothing about it is fragile or clever.

It is also more forgiving than people expect. Denso Wave, the Japanese company that invented the format, explains that four error correction levels are available and that level M, which restores roughly 15 percent of a damaged code, is the one chosen most often. In plain terms, a code can carry a coffee ring, a scratch or a corner of grease and still scan.

So the printing rarely fails. The decision behind the code is where restaurants lose money.

Where most scans land, and why that wastes the moment

Point a code at a PDF and you have given the guest a photograph. A photograph cannot tell them the lamb is finished. It cannot add a sauce. It cannot take the order.

Worse, it cannot be changed quickly. When the price of one dish moves, somebody has to open a design file, export it again, and hope every table got the new print. Meanwhile the picture on the guest's screen says something different from the cash register.

A scan should end in a basket, not in a document. That is the difference between a digital menu and a menu that was merely scanned.

The Saudi part of this

The phone half of the problem is already solved here.

The Communications, Space and Technology Commission reported in its Saudi Internet Report 2024 that internet penetration has reached 99 percent, that mobile phones account for 99.4 percent of internet browsing, and that 93.1 percent of online shopping happens on local websites. Every guest at your table already carries the reader. They are already used to buying from local pages.

What they are not used to is a restaurant code that leads somewhere useful. Most of the codes in the country still open pictures.

What a scan should end in

Here is the shape we built, and it starts at the table rather than at the menu.

A code is generated for every table, so the ticket that reaches the kitchen already knows which table ordered. Nobody types a table number and nobody mishears one. There is a designer so the code carries your colours and your logo, and the finished print pack is emailed to you ready for the printer.

The page it opens is your own menu on an address on getmenu.ae, included from the first day, with 12 page layouts so a long list and a short list can read differently. Items carry options and add-ons with their own prices, and a choice can be marked required so nothing reaches the pass half decided.

Stock is the part guests notice most. Counts fall as orders arrive, options carry counts of their own, and a dish greys itself out at zero without anyone watching the screen.

At the end, every line is priced again from your live menu at checkout, so the number on the phone is the number on the bill. When the order is placed, a confirmation reaches the customer the moment they order, a ticket lands in the managers' WhatsApp group, and for a delivery there is a rider link carrying the GPS pin dropped at checkout.

Groups at one table can order from their own phones onto one bill, which removes the slowest ninety seconds of any table service: working out who had what.

"We tested this on my own cafe before the product had a name. The scan was never the problem. Watching a guest scan, look at a picture, and then wave at a waiter anyway is what told us where the work had to start." — Anzul Aqeel, founder of Get Menu

Keeping the guest after they leave

A scan is also the cheapest introduction you will ever get, because the guest arrived at your page rather than an app.

Stamps can be given per order, per riyal spent, or only on the dish you want to move, and regulars grow into tiers that carry their own automatic discount. The card sits in Google Wallet, live and updating itself, with no app to install. Apple Wallet is built and waiting on a certificate, which we say plainly rather than implying both work today.

Coupons carry caps, exclusions and expiry dates, so an offer stops when you meant it to stop. A VAT invoice is produced as a PDF carrying your tax registration number, and the sales dashboard shows what actually sold by day and by item.

What we do not do

There are no online payments. Payment is cash or your card machine at the door, which also means the product holds no card details at all.

We do not sell a receipt printer, a terminal or a screen for the wall. We do not track ingredients by weight. Old order details are removed on a 120 days schedule, so the address a guest typed last spring is not sitting in the system forever.

Printing the code so it survives a real table

Three practical points, learned the boring way.

Print it big enough to read from a seated position, roughly the width of two fingers at minimum. Give it a quiet white border, because a code printed edge to edge against a dark table is harder for a camera to find. And put one code on each table rather than one poster by the door, because the table is the address.

If you want the wider background, scanning a menu barcode covers what the pattern actually is, QR code menus covers the general case, and scan to order covers the ordering step in more detail.

You can try the whole thing for 15 days, and we do not ask for card details at signup.

Frequently asked questions

How do customers scan a menu QR code?

They open the camera app and point it at the code. On any phone sold in the last several years a link appears within a second and they tap it. No separate scanner app is needed, which is why a code beats asking somebody to type a web address.

Can a guest pay online?

No. Payment is cash or your card machine at the door, which is how most tables here settle anyway. Nothing is charged through the page, and no card details exist anywhere in the system for anyone to steal.

What happens if I change a price?

You change it in your menu and the next scan shows the new price. There is nothing to reprint, because the code points at your page rather than at a file. The code on the table can stay there for years.

Does a printed code stop working if it gets dirty?

Usually not. The format carries spare data specifically so a damaged code still reads. A deep tear across the middle will beat it, but grease, scratches and a folded corner normally will not.

Do guests need to install anything?

No. The restaurant menu is a normal web page. The loyalty card goes into the wallet app already on the phone, so there is still nothing to download.

Keep reading

More on this

Your own ordering page, your own customers

Fifteen days with everything switched on. No card, no commission, ever.

Questions from other owners are answered in the community.

Chat with us