Scan QR for menu: the six steps that have to work

When somebody points a phone at the square on your table, six separate things have to work in a row. If any one of them fails, the customer puts the phone down and asks a member of staff, and you never hear about it.

This guide walks through the six steps from the customer's side, names what breaks each one, and ends with a test you can run yourself in ten minutes.

Step one: the camera has to notice the code

On an iPhone this is built in. Apple's own instructions are to open the Camera app or Code Scanner, hold the device so the code appears, then tap the link that comes up. Android phones behave the same way through the camera or the built-in lens tool.

What breaks it: a code printed too small, a code cropped so tightly that its white border is gone, a glossy laminate throwing back the ceiling light, or a code stuck flat under a glass tabletop at an angle nobody can hold a phone at.

The fix is physical, not technical. Print bigger, leave the border, and put the code where a seated person can lift it.

Step two: the page has to open

The code holds a web address, so the phone needs a connection to reach it. In a basement dining room or a shop with thick walls, that is a real problem, which is why the wifi name belongs on the same card as the code.

The other thing that breaks this step is the address itself. If your code was made by a free tool that routes visitors through its own address first, then that company sits between your customer and your menu. When the free plan changes or the account lapses, every printed card in the room stops working at once.

Step three: the page has to fit the screen

This one is invisible until you see it happen. Phones make an assumption about pages that were never built for them. As Mozilla's documentation explains, a mobile browser may render a page in a virtual viewport of 980 pixels and shrink it down to fit a 640 pixel screen, unless the page tells it to match the device width instead.

That shrinking is why some menus arrive as a wall of tiny grey text. The customer pinches, zooms, loses their place in the price column, and gives up. A menu built for phones does not do this, and a photograph of a printed page always will.

Step four: the menu has to be true

Now they can read it. The next failure is quieter: the page shows a price you changed last month, or a dish that finished at nine.

A menu that is a file cannot know. A menu that is connected can. Stock counts should fall as orders come in, run per option as well as per item, and grey a dish out at zero without anybody watching. That is what stops a customer choosing something they cannot have.

Step five: there has to be something to press

This is where most qr scan menu setups stop, and it is the most expensive place to stop.

The customer has read, decided, and is holding a device. If the only next move is to wave at somebody, the scan has saved nobody any time. A menu that takes the order needs options and add-ons with their own prices, a required choice where the kitchen needs one, and a price recalculated at checkout from your live menu so the number on screen is the number charged.

Step six: the order has to reach a human

The last step is the one customers never see and owners feel every night. An order in a dashboard nobody is watching is not an order.

In Get Menu, about 2 seconds after the customer confirms, 3 messages go out. The customer gets a confirmation and a link to follow their order. Your managers group gets the ticket, carrying the table number when the scan came from a table code, or the map pin the customer dropped when it is going out for delivery. Your riders group gets the dispatch note. Every message is logged with whether it arrived, and an SMS can go from your own SIM when WhatsApp cannot deliver.

"Teaching taught me that people do not report the step where they got stuck. They just stop and blame themselves. A menu scan is the same. Nobody tells the manager the page would not load, so you have to go and find the broken step yourself." — Tanzeel ur Rehman, co-founder of Get Menu

Test it like a stranger

Ten minutes, once a season, and it finds nearly everything.

1. Use a phone that has never opened your menu, ideally an older one.
2. Turn off your restaurant wifi on that phone and scan the code from a normal sitting position.
3. Time how long it takes for the first line of the menu to be readable.
4. Read the price of the fourth item without zooming. If you cannot, neither can your customers.
5. Order the cheapest item, with one option chosen, and see how far you get.
6. Check that the order arrived where your staff will actually see it.
7. Repeat at the table furthest from the window, in the evening, with the lights low.

Ask a friend who has never seen your menu to do steps two to five while you watch and say nothing. The places they hesitate are your list.

What sits behind a scan in Get Menu

Your menu lives at your own address on getmenu.ae, included from the first day, built to be read on a phone held in one hand. There are 12 page layouts, colour themes and a font picker, and photos are compressed automatically so pages stay quick to open. Arabic item names sit beside the English ones.

Codes are produced for you, with a code generated for every table, a designer so the square looks like your brand, and a print pack emailed to you ready for the printer. A group at one table can order from their own phones onto one bill.

For delivery, the customer picks a building and unit number from a list you control, and you set the fee per building. For regulars, stamps and tiers your regulars grow into feed a loyalty card that sits in Google Wallet and updates itself, with the Apple version built and waiting on a certificate. Coupons carry caps, exclusions and expiry dates.

Invoices carry your tax registration number as a PDF the customer downloads without logging in, and old order details are cleared automatically after 120 days. Payment is cash or your own card machine at the door, so there are no online payments and no card details in the system.

If you want the neighbouring guides, scan menu barcode covers what the square actually contains, scan qr to order follows the ordering flow, and qr code menu is the general introduction. Fifteen days to try it, and no card is asked for at any point.

Frequently asked questions

How does a customer scan a QR code for a menu?

They open the camera, point it at the square, and tap the link that appears. On most modern phones there is nothing to install.

Why will my menu code not scan?

Usually the code is too small, printed without its white border, covered by glare, or placed where a phone cannot be held square to it. Reprinting larger fixes most cases.

Do customers need wifi to scan qr menu cards?

They need some connection, because the code is only a link to a page. Putting the wifi name on the same card removes the problem.

What should happen after they scan the code?

They should see a readable menu with current prices, choose what they want, and send the order. Anything less means a member of staff still has to take it.

Can they pay after scanning?

No. They order from the phone and pay in cash or on your card machine when the food arrives, so no card details are held.