Menu page on the restaurant's own site
The recommended setup — a normal web page that reflows on a phone and can be edited whenever the kitchen changes something.
Encoded as
https://example.com/menuPut the menu on the table without reprinting it every time a price changes.
Generated on your device. Nothing you type is sent anywhere.
A menu QR code opens your menu on the customer's own phone. The appeal is obvious for anything that changes — specials, seasonal dishes, prices that move with supply — because updating the page updates every table at once with no reprinting. The part worth thinking about carefully is what the code opens. A web page and a PDF are very different experiences on a phone held at a table, and the choice between them determines whether the menu is genuinely usable or merely present. Error correction here defaults to Q rather than M, because table codes get spilled on.
Update the page and every table shows the new menu immediately. For a kitchen adjusting to supplier prices, that removes a recurring printing cost and the delay that comes with it.
A printed menu has no space for full allergen information. A page has as much room as you need, which makes it easier to answer questions that would otherwise interrupt service.
Dishes can carry photographs and longer descriptions without making the menu unwieldy to hold. That tends to help most with unfamiliar items, which otherwise go unordered simply because nobody knows what they are.
A code on a table tent does not need wiping down between every customer the way a laminated card does, which is one fewer task during a turn.
The recommended setup — a normal web page that reflows on a phone and can be edited whenever the kitchen changes something.
Encoded as
https://example.com/menuA second code for the bar list, so guests reach the right list directly rather than scrolling past food to find wine.
Encoded as
https://example.com/drinksA dedicated page for in-room dining, distinct from the restaurant menu downstairs, placed on the desk or bedside table.
Encoded as
https://example.com/room-servicePut the menu on your website as an ordinary page. Paste that address into Link to your menu. A page reflows to fit a phone screen, which a PDF laid out for print does not.
Open it on a handset and read it the way a customer would — held in one hand, in the lighting your room actually has. Small type that is fine on a laptop is often unreadable in a dim dining room.
Table codes are scanned in low light by people at odd angles, sometimes after a drink. Three centimetres square is a sensible minimum, and four is better on a table tent than on a card lying flat.
A menu code lives on a table where things get spilled. A damaged code stops scanning long before it looks unusable, so protect it and replace it on a schedule rather than waiting for complaints.
This is the defining mistake with menu codes. A PDF laid out for A4 print opens on a phone as a page the customer must pinch and drag around, with type too small to read without zooming into each section. A web page reflows to the screen. If a PDF is the only option, produce a single-column phone version rather than linking the print file.
Dining rooms are dim and the code is often scanned by someone leaning across a table. A code sized for a business card frequently fails in those conditions even though it scans fine under office lighting. Three centimetres is a floor, not a target.
Table codes meet water, oil, candle wax and cleaning products. Damage that is barely visible can stop a scan working, and staff usually learn about it from a frustrated customer. Laminate them and check them periodically as part of a normal shift routine.
A phone-only menu excludes people with a flat battery, no camera, poor eyesight, or simply no wish to use a phone at dinner. Several jurisdictions also treat menu access as an accessibility obligation. Keep a few printed copies behind the bar regardless.
A code pointing at your site's front page makes every customer hunt for the menu through a navigation bar designed for desktop. Link the menu page directly — the extra step loses more people than it sounds like it should.
The payload is an ordinary link, so every scanner opens it and no app is needed. The practical constraints are environmental rather than technical. Restaurant Wi-Fi is frequently poor and basements often have no mobile signal at all, so a heavy menu page with large images can be slow to load precisely where it is most needed — keep the page light. Phones show the domain before opening, so a recognisable address gets scanned more readily than an unfamiliar one. Older handsets without automatic camera scanning still need a scanner app, which is worth remembering for venues with an older clientele.
Error correction defaults to Q here rather than the M used elsewhere on this site. Q recovers from around a quarter of the pattern being obscured, which suits a code that will meet grease and water. The pattern is slightly denser as a result, which is why the printing advice on this page is a little more conservative.
A web page, almost always. A PDF laid out for print forces the customer to pinch and pan around a document while holding a phone at a table, and the type is usually too small to read without zooming into each section. A web page reflows to fit the screen. If you must use a PDF, make a single-column version specifically for phones.
At least three centimetres square, and four is better on a table tent. Dining rooms are dimly lit and the code is often scanned at an angle from across a table, which is much harder than the office conditions people usually test in. Codes sized like a business card fail regularly in real rooms.
Yes — that is the main reason to use one. Change the page and every table shows the new menu immediately. Keep the address itself fixed, such as /menu rather than /spring-menu-2026, so you never have to reprint the codes when the content changes.
Keep some. A phone-only menu excludes customers with a flat battery, poor eyesight, an older handset, or no wish to use a phone over dinner. Several jurisdictions also treat menu access as an accessibility requirement, so a small stack of printed copies is both courteous and prudent.
Physical damage, almost always. Grease, water, candle wax and cleaning products degrade the printed surface, and a code can stop scanning while still looking broadly intact. Laminating helps considerably, and checking them as part of a normal shift routine catches failures before customers do.
No. The code is generated in your browser from the address you type, and nothing is transmitted. There is also no account, no subscription and no redirect service in the middle — the code points straight at your own page, so nothing here can ever stop it working.
This generator is part of business QR codes — see the whole group, and what to decide before you generate one.