QR Codes for Restaurants and Retail: Setup to Analytics
Restaurants got a crash course in QR codes in 2020, and the results were mixed: some replaced menus with codes that worked beautifully, others taped laminated squares to tables that led to a PDF nobody could read on a phone. Retail followed with codes on shelf tags, receipts, and packaging — same split between codes that earn their space and codes that are decoration.
The difference is never the QR code itself. It's three things: what the code points to, whether that destination can be changed after printing, and whether anyone measures the scans. This guide walks through the full lifecycle for restaurants and retail — where to deploy codes, how to build them on short links so they stay editable, the printing specs that determine whether they scan at all, and what to do with the scan data.
The one rule: never encode a raw URL
A QR code is just a URL rendered as pixels. If you encode the destination URL directly — yourpos.com/menu/v2/spring.pdf — the code is frozen. When the menu moves or the ordering vendor changes, every printed code in the building is garbage and you're reprinting table tents at the worst possible time.
Encode a short link instead: the QR code contains yourbrand.link/menu, and that redirects to wherever the menu currently lives. Swap the destination in ten seconds; every printed code updates instantly. This is what people mean by a "dynamic" QR code, and with a shortener it costs nothing extra. You also get scan counting for free, because every scan is a click on the short link.
Create the link on UrlShorter with a readable alias, then generate the code from it with the QR code generator. One editable destination per printed placement — that's the whole architecture. If the redirect mechanics are new to you, what URL shortening is explains them quickly.
Restaurant deployments
Menus
The workhorse. A code on the table tent, window, and host stand pointing to yourbrand.link/menu. The make-or-break detail is the destination: a mobile-formatted menu page scans into a good experience; a print-layout PDF scans into pinch-zoom misery and abandoned scans. If all you have is a PDF, a single mobile web page with the same content is the highest-ROI hour you'll spend on this.
Keep a few paper menus for guests who prefer them — the code should be an option, not a gate.
Table ordering and payment
If you use an order-at-table or pay-at-table system, per-table codes (/table-01 through /table-20) route guests to the right ordering session. Because each code is a distinct short link, you also learn scan volume per table — and when you switch ordering vendors, you re-point twenty links instead of reprinting twenty tents.
Receipts
The post-meal moment is when a review ask converts best. A code on the receipt to yourbrand.link/review, landing directly on your Google review page — not your homepage, not a "choose a platform" page. Every extra tap loses people. The same placement logic drives the broader receipt strategies in short links for small business.
Waitlist, reservations, and specials
A window code for joining the waitlist from the sidewalk; a counter code for the loyalty program; a chalkboard code for this week's specials that you re-point weekly without touching the chalkboard. Each placement gets its own link so the scan counts tell you which locations actually get used.
Retail deployments
Shelf tags and product information
A code beside the price tag linking to specs, sizing guides, comparison info, or demo video — the stuff a good sales associate would say, available when associates are busy. Per-product or per-category links (/sku-4471, /denim-guide) tell you which products make shoppers curious enough to scan, which is merchandising signal you can't get any other way.
Packaging and inserts
Codes printed on packaging or box inserts carry the relationship past the sale: care instructions, warranty registration, reorder, setup video. Packaging runs are long and reprints expensive, which makes the editable-destination rule non-negotiable here — the code printed on ten thousand boxes must be a short link you can re-point for years.
Receipts and bags
Same as restaurants: review requests and loyalty signups convert best right after purchase. Bag stuffers with a discount-for-next-visit code give you a measurable return-visit channel.
Window and in-store signage
After-hours window codes ("browse the catalog / order online") turn closed-store foot traffic into sessions. In-store, codes near fitting rooms ("check other sizes/colors") and endcaps ("see it in use") answer questions at the moment of hesitation. One link per sign location; the scan spread across locations tells you where signage placement works.
Printing specs: why codes fail to scan
Most "QR codes don't work" complaints trace to five physical mistakes:
| Spec | Minimum | Notes |
|---|---|---|
| Size | ~2 × 2 cm (0.8 in) at arm's length | Scale up with distance: rough rule is scan distance ÷ 10 (a code read from 1 m should be ~10 cm wide) |
| Quiet zone | White margin ≥ 4 modules on all sides | Designers love cropping this; cropped margins kill scans |
| Contrast | Dark code on light background | Never invert; low-contrast brand-color-on-brand-color fails on cheap cameras |
| Placement | Flat, eye-to-waist height, glare-free | Curved glasses/bottles and laminated glossy tents under downlights are the classic failures |
| File format | Vector (SVG/PDF) for print | A screenshot PNG scaled to poster size scans poorly |
And two process rules: put a short human-readable call to action next to every code ("Scan for menu"), because a bare square gives no reason to scan; and test every printed placement with a mid-range Android and an older iPhone under real lighting before signing off on the print run.
Measuring scans: from counting to deciding
Because every code is a short link, every scan is logged. The progression from data to decisions:
- Name links by placement, not just purpose.
/menu-table,/menu-window,/review-receipt. Reuse one link across placements and you've thrown away the interesting information. - Establish a baseline for a few weeks. Scans per day per placement, before you judge anything.
- Compare placements. If window scans dwarf table scans, your sidewalk is more valuable than you thought. If shelf codes scan heavily for one category only, that category's shoppers want more information — merchandising insight, free.
- Watch timing and devices. Scan spikes at 6–8 pm confirm the dinner-rush menu code works; a receipts code that only scans on weekends says something about weekend customers. Device split tells you which phones to test with.
- Tie scans to outcomes where possible. Scans of the review code versus reviews actually posted; scans of the reorder code versus reorders. A big gap means the destination page, not the code, is losing people.
- Retire or fix the duds. A placement with near-zero scans after a month either moves, gets a better call to action, or goes away.
The mechanics of reading click data — referrers, geography, device breakdowns — are covered in the link analytics guide, and broader campaign-level QR strategy in the QR code marketing guide.
Trust and upkeep
Two operational notes that outlast launch week.
Sticker fraud is real. Scammers have placed their own QR stickers over legitimate codes on tables and parking meters, redirecting customers to payment-harvesting pages. Print codes into the material where possible rather than as stickers, glance at high-traffic placements during routine cleaning, and brand the area around the code so a foreign sticker looks obviously wrong. The customer-side picture is in our URL shortener security guide.
Destinations rot. The code is permanent; the web behind it isn't. A quarterly fifteen-minute audit — scan every deployed code, confirm each lands where it should — catches the vendor page that moved and the PDF that got deleted before customers do. Keep a simple inventory: placement, alias, destination, last-checked date. Multi-location operations that want each location's codes on the location's own domain should look at the agency white label setup.
Frequently asked questions
Do I need to pay for "dynamic" QR codes?
No. A dynamic QR code is just a code that encodes a redirect you control — which is exactly what a QR code built on a short link is. Create the link, generate the code from it, and you can change the destination whenever you like without touching the print.
What should a restaurant menu code point to — a PDF or a web page?
A mobile-formatted web page, strongly. Print-layout PDFs force pinch-zooming and lose guests. If a PDF is all you have today, deploy it, but treat converting it to a simple mobile page as the next task; the scan-to-abandonment difference is obvious in practice.
How big should a QR code be on a poster across the room?
Rule of thumb: intended scan distance divided by ten. A poster scanned from two meters needs a code roughly twenty centimeters wide. Tabletop codes read at arm's length work at about two centimeters. When in doubt, print a test sheet at several sizes and scan it from the real distance.
Can I tell how many people scanned versus typed the link?
Yes, if you separate them: put one alias in the QR code and a slightly different one in the printed text (/menu and /menu-t, for example). Both point to the same destination; the click counts split scanners from typers. Setup details are in the help center.
Start with one placement
Don't launch fifteen codes at once. Pick the placement with the clearest payoff — menu code for a restaurant, receipt review code for retail — build it on an editable short link, print it to spec, and watch the scans for a month. The habit of measuring one placement well teaches you more than a building full of unmeasured codes ever will, and every code you add after that inherits the same architecture: short link in, editable destination out, scans counted.