Most restaurant QR menus are a print menu exported as a PDF. The diner scans, waits, and gets an A4 page shrunk onto a phone, which they then pinch and drag around while their table waits to order.
It works, barely. It is also a wasted opportunity, because a menu on a screen can do several things a printed one never could, and one of them has become a legal requirement in a lot of places.
First: this is not an ordering system
Worth being clear, because the two get conflated and they are different products.
An online ordering system takes orders and payment, manages tables and pushes tickets to the kitchen. If you need that, you need ordering software, and a menu display will not substitute for it.
This is about displaying a menu well: on the wall, on the table, on your website, in a listing. Many restaurants need both, and plenty need only this.
What matters
Legibility on a phone, over a poor connection
This is the whole game and most menus fail it.
Restaurants often have thick walls and bad mobile signal, and diners are scanning on whatever data they have. A print-resolution PDF that takes fifteen seconds to appear has already lost. Compress the images, and display one page at a time on narrow screens rather than a shrunken two-page spread.
If you design the menu specifically for screens rather than reusing the print file, better still: a portrait page close to phone proportions with larger type reads immediately.
Allergen and dietary information
The most useful thing a clickable menu does, and the reason it is worth more than a PDF.
A printed menu has nowhere to put full allergen detail without becoming unreadable, so most restaurants use a symbol key or a separate sheet, and staff get asked constantly. A clickable region over each dish can open the full ingredient and allergen detail on request: visible to the people who need it, invisible to everyone else.
One important caveat: allergen information carries real legal obligations that vary by country, and they are strict. Displaying it in a pop-up may not satisfy a requirement to have it available in a particular form, and getting it wrong has consequences far beyond a bad review. Treat this as something to confirm with whoever advises you on food safety compliance, not as a feature to switch on.
Changing prices without a reprint
Ingredient costs move. Printed menus mean either absorbing the change or a reprint, so most restaurants absorb it for longer than they should.
A digital menu is a file replacement. Same QR code, same link, updated menu, including marking dishes unavailable rather than having servers explain it at every table.
Photographs where they help
Not on every dish. that reads as fast food and clutters the menu. But a clickable region opening a photograph of the dishes people hesitate over is useful, particularly for unfamiliar or regional items.
Other languages
For anywhere with tourist trade, offering the menu in two or three languages costs nothing to distribute once produced. Read-aloud is also worth considering: for diners with poor eyesight, in dim restaurant lighting, it can be the difference between reading the menu and asking someone to read it to them.
Hosting it on your own site
Put the menu on your own website rather than a third-party menu service, for two reasons.
The practical one: your QR codes are printed on table cards, windows and flyers. If the service changes its pricing or closes, every one of those codes points somewhere broken and you are reprinting all of them.
The second: your menu is full of dish names, cuisine terms and local language that people search for. On your own domain that content works for you. Inside an embed pointing elsewhere, it does not.
Also write the menu out as text on the page around it. Someone searching for a dish you serve should be able to find you, and text in an image cannot do that.
Practical setup
- One permanent URL for the menu, so QR codes never need reprinting.
- Separate menus, separate pages: lunch, dinner, wine, set menu. One long file that diners scroll through is worse than a short one they can read.
- Test the QR code in the restaurant, on the actual signal, at a real table. Not on office wifi.
- Keep some printed menus. Not every diner has a phone, a charged phone, or the willingness to use one. Several jurisdictions also require a non-digital option.
- Decide who updates it before you launch. A digital menu showing last season’s prices is worse than a printed one, because diners assume it is current.
On WordPress, TNC FlipBook 3D handles the clickable regions, mobile single-page display, multiple languages and read-aloud described here, with the menu hosted on your own site. There is a free version to test with your current menu file.
Frequently asked questions
Do I need a special plugin for a QR menu?
Not strictly: a QR code can point at any page, including a PDF. A viewer is worth adding when you want clickable allergen detail, phone-friendly display and photographs on request.
Can diners order from it?
Not directly. A menu display shows the menu; taking orders and payment needs ordering software. You can link from the menu to an ordering system if you use one.
How do I show allergen information properly?
Technically, clickable regions per dish work well. Legally, requirements vary by country and are strict about how the information must be available. Confirm your obligations before relying on a digital format alone.
Will I need to reprint QR codes when the menu changes?
Not if the URL stays the same. Point the code at a permanent page and replace the menu file behind it.
Should I still have printed menus?
Yes. Some diners cannot or will not use a phone, and some jurisdictions require a non-digital option. Treat digital as the default rather than the only choice.
Does a digital menu help my restaurant show up in search?
It can, if the menu is on your own site and the dish names exist as text rather than only inside an image. People do search for specific dishes locally.
