Processed locally
Your input stays in this browser.
A restaurant menu QR code should open the current mobile menu in one scan and be paired with a readable alternative for guests who cannot or do not want to use a phone. Test the menu at a table, including item names, prices, allergens, and the path back to ordering help.
Build the menu for a hungry person, not for a desktop browser
A table code should open the food and drink choices at the first tap, with categories, prices, allergen information where the restaurant provides it, and a visible way to ask staff. A PDF designed for A4 can force a diner to pinch, pan, and lose their place; a mobile menu can expose one course at a time. The QR label should say ‘View today’s menu’ rather than implying that scanning places an order. A printed menu or staff-provided alternative remains necessary for guests who do not use a phone.
Use a 40-table lunch service as the test case
At 12:30, a 40-table dining room has two versions of a soup: regular and vegan, and a lunch special that ends at 14:00. The menu page should show those facts directly, not send every diner to the home page. Put the code on one table tent, scan it from a seated position, and time the route from camera to the main-course list. If a guest needs four taps before seeing food, simplify the destination. When the special changes, update the page at the same stable address rather than printing a new code.
Separate information, ordering, and payment
A menu code is informational unless the destination explicitly offers ordering and the restaurant has designed a table, pickup, or payment workflow around it. Do not let a diner assume an order was sent because a menu page opened. If online ordering is available, show the table-number instruction and the staff fallback beside that action. Do not put a payment credential in a static public QR image. A camera-readable menu is useful even when every order is still taken by a person.
Make allergens and changes legible
The QR image does not make allergen information reliable by itself. State how a diner should confirm ingredients or cross-contact risks with staff, and do not use a stale PDF as a substitute for that conversation. Test the current page after every menu revision: dish names, prices, availability, and the date or meal period. A page that says ‘menu’ but shows last month’s items creates a worse experience than a printed sheet. Keep a dated approval record for the page used by the table tent.
Common table-tent failures
Glossy laminate can throw a reflection across a finder pattern; a code placed under a condiment bottle is not a usable interface; and a code shared with the restroom Wi-Fi or a feedback form makes the guest guess. Test a proof under the actual dining-room light with two phone cameras. Add enough quiet space around the symbol and a short typed address. If the code resolves correctly but the page takes too long or hides prices behind a booking pop-up, fix the page rather than enlarging the square.
Decide what happens after the scan
A menu code is not an ordering system unless the destination explicitly supports ordering and staff can explain that process. A restaurant menu QR code cannot replace a spoken allergy conversation, ensure network coverage at every table, or serve a guest who needs a paper alternative. W3C’s accessibility guidance is available from W3C Web Accessibility Initiative at https://www.w3.org/WAI/tips/designing/. Review scan failures and menu questions after one service; those observations tell the operator whether to improve layout, labels, staff instructions, or the fallback menu.
Measure the path from table to dish
During a 40-table lunch, ask two staff members to scan the tent from a seated position and find the vegan soup, the regular soup and the special that ends at 14:00. Record the number of taps and whether the price, allergen note and staff question are visible before the guest reaches an ordering screen. A useful target is a single landing page with the meal period visible, not a promise that every diner has the same phone or signal. If the special changes at 13:15, change the content at the stable menu address and mark the update time; do not leave a discontinued dish in a cached PDF because the QR image itself cannot tell a guest that the document is stale.
Make the table number an explicit ordering rule
If the restaurant accepts an order from the menu page, state whether a diner must enter a table number, collect from a counter, or wait for staff confirmation. Test table 17 with a deliberately mistyped table 71 and confirm that the workflow shows the mistake before a kitchen ticket is created. A public menu URL should not contain a payment token, a staff login or an unprotected table-management link. For a menu-only code, say so plainly: viewing food is not placing an order. Keep one printed menu at the host stand and a staff script for a diner who cannot use the code. The QR route succeeds only when the service model behind it is as clear as the displayed dishes.
Review a menu change before the next service
Before dinner, compare the live page with the approved kitchen list: 2 soups, 6 mains, 3 desserts, the current prices and any item marked unavailable. Check that a vegetarian label has not been copied to a dish with a changed ingredient, and that the page tells diners how to ask about cross-contact rather than claiming a QR menu can make that judgement. Scan the physical tent after it has been cleaned and moved beside glassware; glare, a folded edge or a condiment holder can change the real result. When repeated questions concern the same item, fix the menu wording or layout. Enlarging the QR code cannot make an ambiguous dish description clearer.
Retire the tent when the menu route is no longer true
At the end of a seasonal menu, scan one retained tent and make sure it opens an honest replacement page rather than a dead PDF, an expired ordering promotion or last year's prices. The replacement can say that the menu has changed and show the current dining route, but it must not imply that an unavailable dish can still be ordered. Remove damaged tents from tables and retain one approved proof with the menu version and test date. This protects a guest from making a choice based on obsolete information and gives staff a clear answer when the QR destination changes.
Leave a human route at the table
A table tent should name a staff route for allergen questions, unavailable dishes and accessibility needs. The QR code speeds up menu discovery; it does not remove the restaurant's duty to answer a diner.
Check the first visible screen
The first mobile screen should show food, service period and a staff question route. A branded splash screen that hides all three adds friction at the exact moment the diner needs a choice. W3C Web Accessibility Initiative is the named source for the current external rule or product behaviour.