A guest scanning a menu in a restaurant on Caddebostan’s waterfront may have a small screen, poor reception or an old QR link saved on their phone. Give that link a stable HTML page and test the actions a guest needs at the table: find a dish, read the price and work out what to ask the staff.
Use menu text guests can resize and search
Give each course a heading and put the dish name, short description and price together as text in the page. Keep a print download as a separate choice when staff need one. When a photo accompanies an item, check that guests can still find its name and price with images disabled.
Test the exact link printed on a table card
Scan an existing card on a phone in a signed-out browser. Follow the link over a slow connection and open the second language directly. Check that guests see the right menu, rather than having to find it through the home page. Try the same link after zooming in and verify that dish names and prices still line up.
Rehearse removing a dish during service
In a test copy, mark a mock dish unavailable. Open the link on two phones in both languages and check that the status matches. Keep one person responsible for that update and give the floor team a way to verify what the guest sees from the printed card.
If the kitchen shares dietary information online, ask the responsible staff to verify the wording in both languages and show guests how to raise an ingredient question with staff.
Record what should pass on every table
Save the printed code’s address, expected menu, last update time, person responsible and outcome of a cross-language price check. Reuse the same checks when menus change.
Checklist before publishing
- Printed code opens a stable menu page
- Dish name and price are readable without pictures
- Both languages show the same availability
- Staff can verify the menu shown to a guest