Most instructions for how to create a QR code menu stop at step three: paste a link, download a square, done. That is the easy part, and it is free everywhere. What nobody mentions is that a generator hands you a code, not a menu — and if it burns your menu's web address into the pattern, every code you print lasts exactly as long as that address does. Here is the full process instead, from the dishes in your head to a laminated code that still works next spring.
Step 1: Collect the menu before you open any tool
The bottleneck is never the technology. The bottleneck is that the current menu exists in four places: a Word file from last year, the chalkboard, the kitchen's memory, and a sheet of paper where somebody corrected the prices. Get one authoritative version first. Then the build takes twenty minutes instead of three evenings.
- Every section in the order guests should read it — starters, mains, sides, desserts, drinks.
- Every dish with its actual current price, not the price you meant to change.
- One line of description per dish, in the words your floor staff already use at the table.
- Allergens and diet notes per dish. The kitchen knows these; write them down while someone has a minute.
- Mark anything seasonal or frequently sold out. You will need that in step seven.
If you already have a decent PDF or a photo of the printed card, you do not have to retype anything. Tools that read an existing menu and draft the sections, dishes, prices and descriptions get you to a reviewable version in minutes — yourmenu.app does this from a photo or a PDF upload, and you correct what the extraction misread instead of starting from a blank page.
Step 2: Two ways to create a QR code menu — and the generator trap
Search for a qr code menu generator and you will find hundreds of them, nearly all free. They all do the same thing, and they do it honestly: you give them a web address, they give you a square. What they do not give you is the address. That is the trap, and it comes in two versions.
- No menu page. A generator encodes a link. If you do not have a mobile menu page yet, the only thing left to link to is a PDF in some cloud folder — which guests then pinch-zoom on a phone. Precisely the experience a QR menu was supposed to replace.
- A URL baked into the code. Most free generators write the destination straight into the pattern. Rename the menu, rebuild the website, move to your own domain later, and every printed code points at a page that no longer exists. The square is fine. The address inside it is dead, and the fix is called a reprint.
A menu platform closes both gaps: it hosts the mobile page and it keeps control of the link behind the code. yourmenu.app encodes a permanent short link rather than the menu URL, so a printed code survives renames, a redesign and a later move to a custom domain (Premium). Whichever route you take, ask this one question before anything goes to print: if my menu's address changes next year, do these codes still work?
Step 3: Build the sections, dishes and allergens
Now you type — or review the extracted draft. Two rules separate a menu that gets read from one people scroll past. Keep sections short enough for a phone screen: twenty-two items in one block is a wall, and splitting it into two named sections costs nothing. And put the information a guest needs on the dish itself, not in a footnote at the bottom.
Allergens belong squarely in that second rule. In the EU, information on the fourteen mandatory allergens has to reach the guest for non-prepacked food, restaurant dishes included, and a badge on the dish does that job better than a legend nobody scrolls to. On yourmenu.app all fourteen EU allergens and the dietary badges sit on the individual dish — and they are part of the free plan, not a paid extra.
Step 4: Generate the code, once
This step really does take seconds. Download the code your platform gives you, then check three things before it goes near a printer.
- A vector file. Ask for SVG, EPS or PDF. A small PNG stretched to poster size becomes a blurry square that phone cameras give up on.
- Real black on real white — dark code, light background. Never inverted, never pastel on pastel.
- The quiet zone left intact: the empty margin around the pattern, roughly four modules wide. Crop it off and scanners lose the edge of the code.
One code is usually enough. Per-table codes only pay off if you need them for something specific; for a menu every guest sees anyway, the same square everywhere keeps life simple.
Step 5: Print specs that actually scan
Print size follows scanning distance, not aesthetics. The widely used rule of thumb is ten to one: a code read from a metre away wants to be around ten centimetres across. On a table, where the phone comes within thirty centimetres, two to three centimetres is the practical floor and three to four is comfortable for older eyes and older cameras. Too big has never been the problem.
- Table tents and stickers: matte laminate. Gloss throws the ceiling light straight back into the camera, the scan fails, and the guest assumes it is their fault.
- Window and terrace: UV-stable print, and think about where the sun sits during the hours you actually serve.
- Anything wiped down forty times a day: laminate or acrylic, never paper.
- Add one short human line next to the code, along the lines of Scan for our menu, in your languages. A bare square gets overlooked.
Step 6: Place it, then test it like a guest
The code belongs where a seated guest's hand already goes: the table, the edge of the bar, the door for people still deciding whether to come in. Then test it properly, not from the office on your own phone. Sit at a table. Use an old Android and a current iPhone. Try it in the evening light you actually work in, and once at midday on the terrace. Check that the page loads on mobile data, not just the staff Wi-Fi. And read the first screen like a stranger: is it obvious that this is the menu, and is the first price visible without scrolling?
Step 7: The update workflow, where it all pays off
Everything so far was setup. This is the return. Prices change from your phone between services and the next scan shows the new number. A dish runs out at eight, you mark it sold out, and it greys out live instead of being explained twenty times. The seasonal changeover becomes ten minutes of typing rather than a print job. Nothing about the printed code changes — which is exactly what step two was for.
Two habits keep it healthy. Update the menu at the moment the kitchen decides, not on Sunday when everyone has forgotten. And once a month, walk the room and scan every code yourself: laminate scratches, stickers peel, and a code nobody has tested since June is a code nobody has tested.
That is the whole process: collect, choose, build, generate, print, place, test, then keep it current. The only step you cannot undo is the printing, which is why what sits behind the square matters more than the square. You can build a complete menu with allergen badges and a permanent QR code on the free plan at yourmenu.app — one menu, no credit card, and within an afternoon you will know whether it fits your room.