What to check before launching your QR menu

1. Establish a single source for the current menu

Start by comparing your current PDF, the price list at the register, and the product names used in the kitchen. If they differ, the business needs to decide which information goes into the digital menu. Transferring an old file in full does not mean you have created an accurate menu. Keep the final list approved for publication, along with its date and the name of the person responsible.

For every item, check its name, category, price, portion details, and whether it is available that day. If two coffees with the same name come in different sizes, add the size to the title or a clearly visible options field. Do not expect customers to work it out from the description. Confirm ingredient information with the kitchen as well; do not fill unknown fields with assumptions.

2. Read the draft as a customer would

Content that looks well organized in the management panel may be perceived in a different order on a phone. Browse the categories in the preview and inspect long titles and price alignment. Choose three tasks for someone seeing the menu for the first time: finding a drink, checking what is in a dish, and comparing two similar products.

Ask the reviewer to record the product name and the change needed, rather than broad comments. For example, ‘cold coffees are listed under hot drinks; they need their own heading’ gives you something to act on, whereas ‘the menu is confusing’ does not. Also prevent different staff members from changing prices simultaneously before the draft has been approved.

3. Test the QR code where it will be used

Scanning the digital image of the code is not enough. Make a sample using your chosen paper, finish, and table stand. Try opening it in daylight, under evening lighting, and from a normal seated distance. Glare, creases, or the angle of the stand can make it difficult for customers to point their camera at the code.

Open the link using both the venue’s Wi-Fi and a phone’s mobile connection. Confirm that it shows the correct business name, menu, and language. Since the menu requires an internet connection, decide how staff will help customers who cannot connect. Keeping a physical alternative available can make service run more smoothly.

4. Test the launch process with a small pilot

Before distributing printed codes to every table, run a short pilot on a few tables. Have one employee observe the visitor screen and another note the questions customers ask. The aim is not to ask customers to complete a long survey, but to notice which information sends them back to staff. A product that repeatedly needs explaining is a good candidate for a content update.

• Does the code open the business’s published menu?
• Has the visitor view been checked after a price change?
• Is it clear who updates products that sell out during the day?
• Is an alternative ready for anyone who has trouble accessing the menu?

5. Assign responsibility for the menu after launch

The work does not end with the first publication. Write down who will prepare changes to prices, descriptions, and availability, and who will carry out the final check. At the end of the first shift, consolidate feedback and fix the issues that actually make it harder for customers to choose. Changing every visual preference on the same day makes it harder to understand which adjustment helped.

You can make preparation and publication in Orvunai part of your team’s routine. Even so, do not treat a notification in the panel as the only proof that the launch succeeded. Opening the menu again through the actual code on a table completes the final check between the content and physical access to it.