For restaurants and cafés
Restaurant QR code generator
The failure mode of dining-room codes is never the code — it is the workflow behind it. A kitchen changes the fish on Thursday, the laminated card on table six still points at last month's PDF, and the first a manager hears of it is a complaint. The fix is structural: encode a link to a page you control, keep every edit on that page, and the printed square on the table never needs to change. The studio above is set up for exactly that pattern. Type the address of whatever you already maintain — a page on your site, a hosted PDF, an ordering platform listing — and print the result once. From that day on, updating what diners see is a job for whoever edits the website, not for whoever owns the laminator.
Generated on your device. Nothing you type is sent anywhere.
This is the Menu QR code generator with its fields preset for restaurants and cafés — the tool page has worked examples, pitfalls and the full format detail.
Scenarios
Where it earns its place
Table service without the reprint cycle
A code on each table tent or placemat sends diners to today's dishes while staff pour water instead of reciting specials. Because the square encodes an address rather than the dishes themselves, an 86'd item disappears from every table the moment the page is edited. Restaurants that laminate prices into their table cards buy themselves a reprint every time the supplier raises the cost of beef.
The takeaway bag that sells the second order
A sticker on the bag or box is the cheapest repeat-business channel a kitchen has. The customer already bought once; the square in their kitchen at home is the shortcut back. Point it at the ordering page, not the homepage — every extra tap between hunger and checkout loses a percentage of the people who scanned.
Window traffic after closing
A code in the front window works the hours the room does not. Someone walking past at ten at night cannot eat, but they can read tomorrow's lunch offer and book. Size it for pavement distance — a person will not press their face to your glass — and check it under the window's evening reflections before committing to vinyl.
Counter cards for the lunchtime queue
When the till queue is eight deep, a counter card pointing at the day's list lets people decide before they reach the front. Orders speed up and the queue shortens without anyone being rushed. This only pays off if the linked page loads fast on a phone on mobile data — test it on the worst connection in the room, which is usually beside the coffee machine.
Workflow
From setup to first scan
Put the day's dishes at a stable address
The link you encode must never change, even as its content changes daily. A page on your own site is ideal; a hosted PDF works if you overwrite the same file rather than uploading a new one with a new name.
Paste that address into the studio above
The preview updates as you type. Everything happens in this browser tab — the address is not sent anywhere, and there is no account between you and the finished file.
Raise the error correction before printing
Dining rooms are hostile to print: sauce, condensation, sun-faded window vinyl. A higher correction level lets a partly damaged square keep scanning. The studio exposes this as a single dropdown.
Download the SVG for anything bigger than a receipt
Table tents, window vinyl and A-boards should all be printed from the SVG, which stays sharp at any size. The PNG is for screens and for the odd flyer run on the office printer.
Scan-test from a chair, not from your hand
Sit where a customer sits, in the room's real lighting, with more than one phone. A square that scans at arm's length on a designer's desk can fail at table distance under warm evening bulbs.
Print once, then stop touching it
From here, every change happens on the linked page. If a table card ever does need replacing, regenerate with the same address and the pattern comes out identical — the same input always produces the same square.
Deployment
Printing, placement and materials
Matte laminate beats gloss in every dining room: gloss catches pendant lights and turns the code into a mirror at exactly the angle a seated person scans from. For table tents, print the square at least 3 cm across; for window vinyl meant to be read from the pavement, treat 10 cm as the floor and test from across the street. Keep a quiet margin around the pattern — designers love tucking it into a corner over a photograph of the dish, and every pixel of texture bleeding into that margin costs scans. Position matters as much as size: eye height on the window, upper third of the table tent, and never flat under the cutlery where glassware shadows it. Takeaway stickers should go on the flattest face of the bag or box, because a square wrapped around a corner will not resolve. Replace any card that has started to peel or bubble; a lifted laminate edge distorts the grid underneath it more than a coffee stain does.
Compliance notes
If the linked page shows dishes and prices, keep it as accurate as the printed card it replaced — consumer-protection rules on displayed pricing apply to a page reached by scanning at the table just as they do to paper. Allergen information duties in most jurisdictions also follow the content, not the medium: if the fourteen major allergens must be declared to diners, the page the code opens is where that declaration now lives, so give it the same review the kitchen gives the specials board.
Common questions
What should the code on the table actually link to?
The page you already keep current. For most kitchens that is a simple page on the restaurant's own site; for others it is a hosted PDF that gets overwritten each morning, or a listing on the ordering platform they use. What matters is that the address stays fixed while the content moves. If you link to a file whose name changes with each upload — specials-june-v2.pdf — the printed square dies with the old filename.
Do I need a new code when the dishes or prices change?
No, and that is the entire point of encoding an address instead of the content. The square on the table is only a pointer; edit the page it points at and every table, window and bag sticker updates at once. You only regenerate if the address itself changes — a new domain, a different platform — which is a decision made once a year, not once a service.
Is there a monthly fee or an account behind this?
There is nothing behind it at all. The square is generated in your browser and encodes your address directly, so no service sits in the middle collecting a subscription for keeping it alive. Commercial dynamic-code platforms charge because they host a redirect; this tool produces static codes that need nobody's server, which is why a card printed today still works in five years.
How big should a code be on a table tent?
Three centimetres is a sensible floor for something scanned at arm's length, and going to four costs almost nothing on an A6 tent. The real constraint is the link length: shorter addresses produce coarser, easier squares. If your ordering platform hands you a two-hundred-character link, put a short redirect on your own domain in front of it and encode that instead.
Why do diners get a login page instead of the dishes?
Because the linked page sits behind the ordering platform's login or a region gate, which the kitchen's own phones never see because they are already signed in. Test the link in a private browsing window before printing — that shows you what a first-time diner sees. If a login appears, link to the public listing page instead of the management view.
Should the takeaway sticker use the same code as the tables?
Use the same destination but consider a separate link with a tracking parameter for each placement — ?from=bag on the sticker, ?from=window on the vinyl. The squares will look different but behave identically, and your analytics will tell you which placement actually brings orders back. That is the honest, self-hosted version of the scan counts that dynamic-code platforms sell.
Read before you print
- How big should a printed QR code be?Sizing a code is one ratio and three constraints. This guide gives the distance rule, the minimum sizes that survive real printing, and the reason a code that looks fine in the design file fails on the press.
- Why a QR code won't scanFailures cluster into six causes, and they are not equally likely. This guide puts them in diagnostic order so you test the cheap explanations first and stop guessing at the expensive ones.
Related use cases
Browsing more broadly? The Business QR codes hub groups every generator this kind of work leans on.