For a lot of people QR menus are a pandemic-era annoyance, and honestly, fair enough. But nearly every reason they irritated guests has the same root cause. Behind the code there was a PDF.
A PDF is not a menu, it is a picture of one
On a phone a PDF opens like a poster. You zoom, you drag sideways, you hunt for where the starters went. It loads slowly because it is usually a Word export nobody optimised. And changing the lunch offer on Tuesday means exporting again, uploading again, and hoping the right file went live.
A menu that is an ordinary web page solves all of that at once: it loads in a second, the text reflows to the width of the phone, it is searchable, and changing a price is one field in the back office.
Where to put the code
A table stand is quick and also the thing most likely to get lost, greasy or turned face down. If you already print a paper menu, put the code on its last page. The guest who wants paper has paper; the one who wants today’s lunch scans.
Two practical things it usually fails on: do not put the code under gloss or glass that reflects light, and do not print it smaller than two centimetres, however elegant that looks in the design.
Keep the paper
This is the important one. A QR menu is not a replacement for paper, it is an addition. Some guests will always want paper, and pushing them onto a phone turns dinner into an argument. The saving is not that you stop printing. It is that you stop reprinting every time a price moves.