QR Code for a Restaurant Table

Never point it at a PDF

A PDF menu on a phone is a bad experience and it shows in the numbers: guests zoom, lose their place, and end up asking the server what is on it anyway. You paid for a QR code and got a slower version of a paper menu.

Point the code at a mobile menu page instead — categories the guest can tap, prices in readable type, photos where they help, allergen tags where they are required. It loads in a second and works with one thumb.

A proper menu page also lets you do things paper cannot: mark a dish sold out at 8pm, run a lunch menu that switches itself off, or show the same menu in two languages for a tourist crowd.

Make it dynamic, or plan on reprinting

A static QR code has the menu address baked into the printed square. That is fine only if the address never changes and the menu behind it is fully editable.

The safer setup is a dynamic code: the printed square points at a short link you own, and the link points at the current menu. Change supplier, change season, move the menu, redesign the whole thing — the table cards stay valid.

This is what makes the difference between a QR menu you set up once and a QR menu you argue about with the printer every quarter.

One code for everything, or one per table?

For most restaurants, one code for the whole room is right: it is cheaper to print, simpler to replace, and the menu is the same wherever the guest sits.

Use per-table codes when the table number matters — order-at-table, table-side payment, or feedback you want attributed to a section. Then each code carries its own link, and you can also see which sections scan most.

A middle option that works well in larger venues: one code per zone — terrace, bar, dining room — so you can run a different drinks list outside without printing forty variants.

Size, angle and placement

On a table, the code is read from roughly 30 to 50 cm, so 3 to 4 cm square is comfortable. Anything under 2 cm starts failing for guests with older phones or in low evening light.

Angle beats size. A code lying flat on a table forces the guest to lean over it and shadow it with their own head; a table tent or a small stand at 60 to 70 degrees is read instantly. This one change fixes most 'the code does not work' complaints.

Avoid the middle of the table, where it ends up under a bread basket by the time the guest wants it. The edge nearest the seat, or the condiment stand, keeps it reachable through the meal.

Surviving the dining room

Table cards get wet, greasy and dropped. Laminate them or print on coated board, and print more than you need — treat them as consumables, not signage.

Matte lamination scans better than gloss under downlights, because gloss throws a highlight straight into the camera. If your room is lit with spots, this is not a detail.

Print vector exports rather than a scaled-up screenshot, keep the quiet zone intact, and always keep a couple of paper menus behind the bar. Some guests will not scan, and refusing them a menu costs more than the printing.

Give the guest a reason and a fallback

Caption the code: 'Scan for the menu', plus the short link written out underneath in small type. The written link is the fallback for a dead phone, a broken camera, or a guest who simply prefers typing.

If the menu is available in more than one language, say so on the card. Tourists scan far more readily when they can see they will not have to translate.

Add one line about what else is behind the code if there is anything — allergen information, the wine list, the takeaway ordering page. A guest who knows the code leads somewhere useful scans it earlier in the meal.

What the scan data tells a restaurant

Scan counts by day and hour show real service patterns: whether the lunch crowd uses the menu at all, how quickly scans fall off once regulars know the menu, and whether a new table card in the terrace changed anything.

Device and OS breakdowns matter more here than elsewhere. If a third of your guests are on older Android phones, that is an argument for a simpler menu page and larger codes.

Compare zones if you use per-zone codes. A terrace that scans half as much as the dining room usually means the code is badly placed or badly lit, not that terrace guests are less curious.

Step by step

1. 1Build a mobile menu pageCreate a tappable menu with categories, prices and allergen tags — not a PDF — so it reads well on a phone.
2. 2Give it a short link you ownPoint the printed code at a short link rather than the menu address directly, so you can move or replace the menu later.
3. 3Generate the code and caption itCreate the QR code, add a frame reading 'Scan for the menu', and print the short link underneath as a fallback.
4. 4Print at 3 to 4 cm on an angled standExport vector, print on coated or laminated board, and use table tents rather than flat stickers so the code is not shadowed.
5. 5Review scans after two weeksCheck scans by day, hour and zone, and move or resize the cards that underperform.

Frequently asked questions