Scan QR code for menu: what has to work, and who fixes it

A guest sits down, lifts a phone and expects food to be choosable within a few seconds. If it is not, they put the phone down and wait for a waiter, and the code on your table has quietly become decoration.

Three separate things decide how that goes. The phone in their hand, the printed card on your table, and the page the code opens. You control two of them completely. This is a plain guide to all three, written for the person who has to buy the cards and answer for them later.

The phone side, which is already solved

You do not need to tell anyone to download a scanner. On an iPhone, Apple's own instructions are to open the Camera app, hold the device so the code appears, and tap the link that pops up. Android phones built in the last several years behave the same way from the camera or from the built-in lens button.

So the honest answer to "how do I scan a QR code for menu access" is: point the normal camera at it. That is the whole instruction, and it is worth printing on the card in both English and Arabic, because a guest who is not sure will simply not try.

What still goes wrong on the phone side is small and predictable. A cracked screen protector scatters the focus. A very dim corner table gives the camera nothing to read. An older handset with the camera app replaced by something unusual may not offer the tap. None of these are common, and all of them are fixed by a waiter who knows the menu can also be handed over on paper.

The card side, which is entirely yours

This is where most failures actually live, and they are physical rather than technical.

Size. A code on a table tent needs to be big enough to read from a seated arm's length. Small codes work at 10 centimetres and fail at 50, and a guest will not lean in.

Contrast. Dark code on a light background. Coloured ink on a coloured card looks lovely on a screen and reads badly under warm restaurant lighting.

Quiet space. The plain margin around the square is part of the code. Designers who crop it tight to fit a logo break the thing they are decorating.

Damage tolerance. Every QR code is printed with an error correction level, and it matters more in a dining room than people expect. Denso Wave, the company that created the format, explains that raising the level improves the code's ability to survive damage but also makes the code larger, and that Level M, at 15 percent, is the one most frequently selected. A table code lives in an environment closer to a workshop than an office: olive oil, thumbprints, a candle mark, a wipe with a wet cloth 40 times a week. A higher level and a slightly bigger square is usually the right trade for a restaurant table.

Placement. One code per table, fixed where a plate cannot cover it. Codes on a wall at the door are read once by the first person through it and by nobody else.

If you want to print a set today without buying anything, a free restaurant menu QR code covers the generator side and its traps.

The page side, where the decision actually is

Here is the part the printing shop cannot advise on. Two codes can look identical and behave completely differently.

One opens a photograph of a laminated menu. The guest pinches to zoom, reads sideways, gives up on the small print, and calls a waiter. Nothing has been saved.

The other opens a menu built for a thumb, at the right size, with prices that are correct because they came from the same place your kitchen changes them, and with an order button at the bottom. That second one is a different product wearing the same square of ink.

Ours is the second kind, and the piece that makes it worth doing is the table number.

What the scan starts, once it is pointed at a real menu

Every table gets its own code, generated for you. The table is the address. The guest types no number and picks nothing from a list, and the ticket that reaches the kitchen already says which table it belongs to.

A designer for the code itself. Colours and a logo, checked so the printed result still scans, then a print pack sent to you as a file the printer can use.

The menu reads properly on a phone. Categories and items reordered by dragging when the kitchen changes its mind. Options and add-ons carry their own prices, and required choices mean nobody sends through a burger with no doneness chosen.

Stock that is honest at the table. Counts per item fall as orders come in, counts per option too, so running out of one sauce does not take the whole dish off. At zero it greys itself out, and no guest reads about a dish you cannot make.

Everyone at the table can order. Four phones, one bill, no shouting an order across a full table to whoever is holding the only menu.

The kitchen finds out immediately. A confirmation goes to the guest, a ticket to the managers' group, and your team reads it in the app they already have open rather than a new screen nobody watches.

The second visit is set up on the first. Stamps per order, a card that lives in the guest's Google Wallet with no app to install, and rewards for scanning again on the next visit. Apple Wallet is built and waiting on a certificate, so today it is Google only.

Offers that stop by themselves. Coupons with caps, exclusions and expiry dates, so a Ramadan deal is not still running in June because nobody remembered.

The paperwork afterwards. VAT invoices carrying your registration number as a PDF, and a sales dashboard by day and item so you can see which table code is actually used.

"We watched a service in a cafe where the code worked perfectly and nobody scanned it. The stand was behind the napkin holder. We did not fix a single line of software that week. We moved 18 pieces of acrylic."

— Agha Shah Zaman, co-founder of Get Menu

The limits, said early

The guest scans, chooses and confirms, and then pays your team in cash or on your own card machine at the table. There are no online payments in the product, which also means there are no card details in it for anyone to steal.

There is no scheduled ordering, so nobody can scan today and book a table order for tomorrow evening. Orders are for the meal happening now, inside the opening hours you set.

And we are not a cash register. If your problem is the counter, the drawer and the receipt printer, this is not the thing to buy, and scanning a QR code to order explains where the line sits between the two.

A first week that will not embarrass you

Print two cards before you print for all 20 tables. Put them where you can watch from the counter. Run a full service and count how many guests scan without being prompted.

Then fix whatever you saw. It is almost always the stand, the lighting or the wording on the card, and almost never the code.

Only after that, print the set for every table. A QR code menu covers the wider setup for a whole dining room.

The trial gives you 15 days to do exactly this, asks for no card details to begin, and takes 0% of what the tables spend, so the only real cost is the printing and one attentive service.

Frequently asked questions

Is a scan qr code menu the same thing as a digital menu?

Usually, yes. Both mean the menu lives on the guest's phone. The difference that matters is whether the page can take the order or only show pictures of one.

Do guests need an app to scan a QR code for menu viewing?

No. The normal camera on any recent iPhone or Android phone reads the code and offers a link. The menu then opens as an ordinary web page.

What if a guest cannot scan it?

Keep two paper menus behind the counter. A staff member can also take the order in the usual way, and the guest is not made to feel stupid for asking.

Can the code tell the kitchen which table the order came from?

Yes. Each table has its own code, so the table number arrives with the order and nobody has to type it.

Can customers pay after scanning?

No. Payment is cash or your own card machine at the table or the door. Nothing card-related is stored in the system.

Will the code still work after we change prices?

Yes. The printed square points at your live menu, so changing a price changes what the next scan shows. You never reprint a code because of a price.