QR Codes for Restaurants: Digital Menus and Scan Tracking
How restaurants use QR codes for digital menus, packaging, and training: upload the menu once, print the code, update anytime, and measure scans at every table.
The QR code survived the pandemic because it solved a permanent problem, not a temporary one. Restaurants that printed table codes for contactless menus kept them because guests liked them, menus updated faster, and — quietly — the numbers turned out to be useful. A menu QR code is the only part of a restaurant's marketing that reports exactly how many people used it.
This guide covers how restaurants can run QR codes well: digital menus that update instantly, codes that survive menu changes, packaging that answers questions, and scan tracking that tells you what's working.
Why restaurants use QR codes
The reasons stack up quickly:
-
Instant updates — a menu change is an upload, not a reprint. Replace the PDF at the same address and every table code shows the new menu.
-
No app required — guests open the menu in the phone's camera and browser. Zero friction.
-
Full menus without space — table tents and signs can be small when the menu lives behind the code.
-
Measurable — every scan is a data point about which placement and which day drives usage.
-
Hygiene and language — guests control their own screen, and multilingual menus are one upload away.
The same code that prints on a table tent can live on packaging, receipts, and delivery inserts.
The digital menu workflow
A restaurant menu QR code is a file problem with a simple answer: upload the menu once, print the code, update the file whenever prices or dishes change.
-
Upload the menu PDF. The file gets a public page with preview and download controls.
-
Generate the QR code. The upload produces QR PNG and SVG assets automatically.
-
Print the code. Use the SVG on table tents, signage, and packaging — it stays sharp at any size.
-
Update freely. When the menu changes, replace the PDF at the same address. Every printed code now points at the new menu.
Because the code points at an address rather than a copy of the file, there is never a version mismatch between the table tent and the menu. The PDF to URL guide covers this workflow in detail.
Packaging, receipts, and delivery
The same QR code principle extends beyond tables:
-
Packaging — takeout boxes and bags carry codes for allergen sheets, reheat instructions, and the full menu.
-
Receipts and delivery inserts — a code turns the takeaway moment into a return visit.
-
Loyalty and events — printed codes link to specials, reservations, and tasting menus.
Every placement can use its own uploaded file, so each one reports its own scan count. That's how you learn whether the bag insert or the table tent actually drives scans.
Tracking scans at every table
The quiet advantage of a restaurant QR code is measurement. When each menu upload tracks scans separately from views and downloads, a restaurant can see:
-
How many guests scanned the menu — a proxy for how many used the code rather than asking for a paper menu.
-
Which days scans peak — weekend versus weekday behavior, useful for staffing and specials.
-
Which placements work — table tents versus packaging versus signage, each reporting independently.
No other restaurant marketing channel reports this. A printed flyer is a guess; a QR menu is a count. The scan numbers convert that count into decisions — which specials to run, where to place codes, and how to price menu updates.
Training and compliance behind codes
The same infrastructure carries staff content that guests should never see:
-
Training videos — new menu items and service standards behind an internal code.
-
Allergen and nutrition sheets — updated centrally and instantly available.
-
Health and safety documents — posted and replaced without reprinting.
Because access is by link, an internal code can be shared only with staff, while the public menu code stays guest-facing. Both use the same upload, QR, and tracking mechanics.
Getting started in an afternoon
A restaurant can go from zero to table codes in one afternoon:
-
Export the menu as a PDF.
-
Upload it to ShareKit and copy the QR SVG.
-
Print table tents with the code and a one-line prompt ("Scan for the menu").
-
Test with your own phone before printing the run.
-
Check the scan counts after the first weekend and adjust placement.
The cost is a PDF and a print run; the return is a menu that updates instantly and a channel that measures itself. Our QR code guide covers placement best practices — size, quiet space, and testing — that make the difference between a scanned code and an ignored one.
Codes guests actually scan
The difference between a QR code that works and one that gets ignored is usually placement and copy. Put the code where the phone already is: a table tent propped toward the guest, a sticker at the edge of the tray, a code on the bag handle rather than the side. Pair it with a verb — "Scan for the menu", "View today's specials" — so guests know what happens next. Keep the code 2-3 cm with quiet space, print from the SVG for sharpness, and test with your own phone before the print run. Restaurants that follow these rules see scans; restaurants that print tiny codes in a corner collect dust. The scan counts will tell you which category you're in within a week.
FAQ
How do I create a QR code for a restaurant menu?
Upload the menu PDF and download the generated QR SVG. Print it on table tents, signage, or packaging.
Can I update the menu without reprinting codes?
Yes. Replace the PDF at the same address; every printed code points at the new version automatically.
Do guests need an app to scan the menu code?
No. Modern phone cameras scan QR codes natively and open the menu in the browser.
Can I track how many guests use the menu code?
Yes. Each menu upload reports scans separately from views and downloads.
What file should the menu code open?
A PDF of the menu. The hosted page previews it with a download option, and prints cleanly for staff.
Can I use QR codes on takeaway packaging?
Yes. Upload allergen sheets, reheat instructions, or the full menu and print the code on boxes and bags.
Do multilingual menus work with QR codes?
Yes. Upload one PDF per language; each gets its own code, or one code can open a page that links to all languages.
How quickly will I see scan data?
Scans are recorded in real time, and after the first weekend of table codes you'll have enough numbers to compare placements.
A Saturday service, with numbers
Picture a 48-seat room, twelve four-tops, and one QR on each table tent. The menu PDF is six pages: drinks, small plates, mains, desserts. You export it at breakfast, upload it, and print the SVG at 25 mm wide with a quiet zone at least as wide as four modules of the code. The call to action under the mark is seven words: "Scan for today's menu and allergens."
You do not need a scan from every seat to learn something. If Saturday night does 90 covers and the upload reports 54 QR scans, 61 page views, and 9 downloads, the useful reading is directional. Most people who scanned opened the page. Few saved a copy. The gap between covers and scans is not failure; many guests already know the dish they want, or they asked a server. Compare that Saturday with the next one after you move the tent from the condiment caddy to the edge nearest the guest. If scans move from 54 to 71 while covers stay near 90, placement changed the behavior. If scans stay flat, the code is probably hard to see, the prompt is vague, or guests prefer the paper menu you still leave on the table.
Keep the comparison to one change at a time. Do not reprint the tent, swap the PDF, and move the tent on the same night and then credit one of those changes for the whole difference. Write the date, the cover count, and the three ShareKit numbers in a shared note. Two weekends is enough to decide whether a placement stays.
What belongs in the PDF, and what does not
The hosted page previews the PDF and offers a download. It is a public address. Anyone with the link can open it, and the link is what the QR encodes after the scan redirect. Do not put staff wages, supplier invoices, reservation lists, or a guest's personal data in that file. Allergen matrices, prices, and hours are appropriate. A wine list with bin numbers is appropriate. A spreadsheet of customer phone numbers is not.
Build the PDF for a phone held in one hand. Body text at a size you can read without pinching, prices in a consistent column, and the revision date on the first page in plain language such as "Menu revised 18 October 2026." That date is how a server confirms the tent is showing tonight's file before the first seating. If breakfast and dinner differ, use two uploads and two codes, or one PDF whose first screen says which service is current. A single code that opens the wrong service at 8 a.m. trains guests to ignore it.
ShareKit does not password-protect the public page. If a training video or a health-inspection binder must stay off the guest path, upload it as its own file and do not print that QR on the table. Staff can open the staff link from a bookmark. Guest tents stay on the guest menu only.
Replacement is how prices change without a new print run. A signed-in owner can replace the file at the same address up to five times. The share URL and the QR image stay put. Replacement does not, by itself, move the stored expiry date. Guest uploads are stored with a 7-day date. Files saved to an account are stored with a 30-day date. Keep One File, the one-time purchase on the pricing page, moves that date out by at least a year for one specific upload, its URL, and its QR. When the stored date passes, the public page stops serving the file. Delete the upload when the page should stop sooner, and keep your own copy. A reminder email can be sent before the stored date. Plan the print lifetime around a file you are willing to leave online, not around an assumption that the code dies on day 31.
A one-afternoon setup that survives Monday
Block ninety minutes, not a week.
- Export the approved PDF. A second person checks three prices, one allergen line, and the revision date. This takes ten minutes and prevents a reprint of the tent copy.
- Upload the PDF on PDF to URL. Files under 20MB have no credit cost. A menu PDF is usually well under that. Copy the QR SVG, not a screenshot of the PNG.
- In the design file, place the SVG at 25 mm or larger for a table tent viewed from about 30 cm. Leave quiet space on all four sides. The prompt sits under the code, not across it.
- Print one proof. Scan it with a phone that is not signed in to ShareKit. Confirm the preview shows tonight's prices. Scan again from the doorway, under the pendant light you actually use at dinner.
- Print the run only after that proof scan works. Note which tent design points at which upload if the bar and the dining room use different files.
- On Monday, open the upload and read views, downloads, and QR scans as three separate counts. They are not unique people, and they are not sales.
The same pattern covers takeaway. A 20 mm code on a bag handle, with "Reheat and allergens" as the prompt, can point at a one-page PDF. Give that insert its own upload if you want its scans separate from the table tents. Packaging codes fail when they are glossy, creased across the matrix, or smaller than the distance allows. Matte stock and a flat panel beat a curved lid.
If you later change a dish photo or a price, replace the PDF and scan one live tent before service. Do not generate a new QR unless you are ready to replace the printed piece. The longer guide on updating a printed menu QR walks through that handoff. Placement size and materials are covered in the QR code guide.
Questions operators actually ask after the first week
The code scans in the office and fails on table 12. What changed?
Usually contrast or curvature. A dark pattern behind the modules, a laminate glare under a spotlight, or a tent that bends the code will fail even when the file is correct. Move the proof to that table and scan before you touch the PDF.
Can I see which guest scanned?
No. ShareKit reports aggregate views, downloads, and QR scans for the upload. It does not identify the person, the device owner, or whether they ordered.
We have two languages. One code or two?
Two uploads give you two scan counts, which tells you whether the English or the second-language tent is the one guests use. One PDF with both languages is simpler to print and weaker as a measurement. Pick the one your floor can maintain.
Does a new PDF mean a new QR?
Not when you replace the file on the existing upload, within the five-replacement limit, while you still control that address. A brand-new upload is a new address and needs a new code in print.