QR code menu examples: what a good digital menu looks like on a phone
By the Menulta editorial team · Facts checked 15 October 2026 · Updated 15 October 2026
The short answer
A good QR code menu opens in a second or two, shows the restaurant's name and the menu sections straight away, uses large readable text, puts photos and allergens on each dish, and follows the guest's phone language. Weak examples are PDFs that need zooming, menus behind pop-ups or sign-ups, and long lists without sections or photos. The fastest way to judge is to scan a live example on your own phone.
Anatomy of a good QR menu
Most effective QR menus share the same structure.
- Header: restaurant name and logo, opening hours if useful, language selector.
- Section tabs or a sticky index: starters, mains, desserts, drinks, so guests can jump.
- Dish cards: name, short description, price, photo where useful.
- Allergen information on each dish, in words, with optional icons.
- Dietary labels where accurate: vegetarian, vegan, gluten-free (only if the kitchen can meet the rules).
- Clear 'sold out' or 'unavailable' marking instead of hidden dishes.
- A footer with contact details and how to ask staff about allergies.
Example layouts by venue
| Venue | What works | Why |
|---|---|---|
| Café | Short list, photos of pastries, drinks first | Guests decide quickly; drinks are the main order |
| Cocktail bar | Photo-led cards, ingredients listed, spirit filters | Guests choose by look and base spirit |
| Family restaurant | Clear sections, kids' menu, allergen labels prominent | Parents check allergens before ordering |
| Fine dining | Tasting menu as a sequence, wine pairings, minimal photos | The experience is the story, not a catalogue |
| Beach club | Large text, high contrast, drinks and snacks at the top | Bright sun and short attention |
| Pizzeria | Base and topping filters, sizes, photos of each pizza | Many similar items need visual difference |
Common mistakes
- A scanned PDF of the printed menu, with tiny text and no structure.
- Cookie banners, pop-ups or 'download our app' screens before the menu.
- Photos that do not match the real dish, which disappoint guests and can mislead under EU rules.
- Machine translations that turn local dish names into nonsense.
- Allergens only in a footnote.
- Out-of-date prices because updating is inconvenient.
Photos: real dishes, not stock images
Photos sell dishes, but only if they show the real plate. Stock images and AI-generated food photos often look better than the real dish, which disappoints guests and can breach the fair-information rules in Article 7 of Regulation 1169/2011. The best results come from photographing your own dishes and improving the light and background without changing the food.
See a live example
The quickest way to judge a QR menu is to use one. Menulta has a live example menu you can open on your phone: switch your phone's language and watch the menu follow, tap a dish to see its allergens, and compare it with the printed menus you have seen. If it suits your restaurant, the price is EUR 39.90 a month plus EUR 149 setup with printed table stickers.
Writing dish descriptions that work on a phone
On a small screen, short descriptions win. Lead with the main ingredients and the cooking method, keep it to one or two lines, and avoid long stories that push the price off screen. Put allergens in their own field rather than buried in the description, so guests can find them at a glance and every language shows them the same way.
Sources
This guide is general information, not medical or legal advice. Guests with an allergy should follow their doctor's advice. Operators should confirm their own setup with their food safety adviser or local authority.