QR Codes for Events, Packaging, and Retail: A Practical Playbook

A QR code on a screen is easy. A QR code in the physical world has to survive bad lighting, awkward angles, laminate glare, a two-metre standing distance, and a person who has about three seconds of curiosity before they walk away.

Most physical QR codes fail for boring, fixable reasons. This playbook covers the three highest-volume contexts — events, packaging, and retail — and what changes between them.

The rule that applies everywhere: size by distance

The single most common failure is a code that is physically too small for where it is placed. The working rule is that the printed code should be roughly one tenth of the scanning distance.

Round up. Nobody has ever complained that a QR code was too easy to scan.

Two more rules that never change:

• Quiet zone. Leave clear space around the code equal to at least four modules — roughly the width of four of the small squares. Text or artwork crowding the edge is a frequent cause of scan failure.
• Contrast and polarity. Dark code on a light background. Inverted codes fail on many older scanners, and light-on-dark is a gamble that buys you nothing.

Events

At an event, the scan is competing with noise, crowds, and someone's dwindling phone battery. Optimise for speed.

Where codes actually get scanned

• Registration and check-in signage
• Table tents at seated sessions
• The last slide of a talk, held for at least thirty seconds
• Badges and lanyards, for peer-to-peer contact sharing
• Roll-up banners at booth entrances, at chest height rather than floor level

What to put behind the code

Not your homepage. An event scan should land on something short and immediately relevant: the session slides, a schedule, a booth-specific offer, or a three-field lead form. If someone scans during a talk and gets a generic marketing site, you have wasted the only moment of intent you will get.

Wording matters more than design

"Scan me" earns almost nothing. State the payoff:

• "Scan for the slides from this talk"
• "Scan to book a 15-minute demo"
• "Scan for the floor plan"

Practical event details

• Assume the venue Wi-Fi is bad. Keep the destination page light and avoid heavy video on the landing screen.
• Print codes on matte stock. Gloss and lamination throw glare under event lighting and kill scans from an angle.
• Place codes between waist and eye height. Codes near the floor go unscanned.
• Use a different short link per placement — one for the banner, one for the table tents, one for the closing slide. A single code across the whole event tells you nothing about which placement worked.

Post-event, repoint the destination. A week later, the same printed codes can point to a recording, a follow-up offer, or next year's registration. That only works if you used a short link you control rather than a hardcoded URL baked into the code image.

Packaging

Packaging is the opposite problem. The scan happens close up, in the hand, often at home, sometimes weeks or years after printing.

Design constraints

• Minimum 2 cm, and 3 cm is safer once you account for curved surfaces and shrink wrap.
• Curved surfaces distort the code. On bottles and cylinders, keep the code narrow relative to the diameter, or place it on a flat panel or the label's flat section.
• Avoid printing across a fold, seam, or perforation.
• Small print sizes need more error correction, but remember that higher error correction makes the pattern denser — so increase physical size alongside it rather than instead of it.

What belongs behind a packaging code

Packaging codes have the longest life of any code you will print, so the destination should be something you can maintain:

• Instructions, assembly guides, or care information
• Ingredient, sourcing, or compliance detail that will not fit on the box
• Registration, warranty, or activation
• Reorder or subscription flow
• Recycling and disposal guidance

Avoid time-limited promotions on packaging unless you are willing to repoint the link when the promotion ends. A code that leads to an expired offer is worse than no code.

Longevity planning

Products sit in warehouses and cupboards for years. Assume the destination URL will change at least once during the product's life. Use a short link on your own domain so you can repoint it, and never delete it — repoint an obsolete campaign to a relevant evergreen page instead.

Retail

Retail sits between the two: close-range scanning, but with a short attention window and heavy competition from everything else on the shelf.

High-value placements

• Shelf-edge labels for extended product detail and reviews
• Window displays for out-of-hours browsing and ordering
• Fitting rooms for size and stock availability
• Point of sale for loyalty sign-up and receipt-free returns
• Out-of-stock cards, so the sale moves online instead of disappearing

What retail codes should do

The strongest retail use is bridging the gap between what the shelf can hold and what the customer wants to know. Reviews, sizing, full specifications, video demonstrations, and stock at other locations are all things the physical space cannot show.

The second strongest is rescuing a lost sale. An out-of-stock card with "Scan to order this for delivery" converts a wasted trip into revenue.

Retail specifics

• Shelf-edge codes need to work at about 40 cm, so 4 cm minimum, and larger if the aisle is narrow and people scan at an angle.
• Window codes are scanned through glass at 1–2 m, often with reflections. Go large — 15 cm or more — and keep the code high enough to avoid street-level glare.
• Check the mobile signal in-store. If coverage is poor at the back of the shop, the landing page needs to be lightweight, and guest Wi-Fi signage should sit nearby.
• Give every store, and ideally every fixture type, its own short link. That is the only way you will learn that window codes outperform shelf codes four to one, or that one branch's placement is broken.

Measuring what happened

Physical QR campaigns are measurable, but only if you set them up that way before printing.

1. One short link per physical placement. Per banner, per SKU, per store, per fixture.
2. UTM parameters on the destination, so scans show up in your web analytics alongside everything else. utm_source=qr, utm_medium=print, utm_campaign=spring-instore.
3. A naming convention you can sort. qr-store-manchester-window beats qr7 when you have forty of them.
4. A review date. Physical placements have long tails — check at one week, one month, and one quarter.

What to look for: scan volume by placement tells you where to put more codes. Scan time-of-day tells you when your physical audience engages. Repeat scan rate on packaging tells you whether the destination is genuinely useful or a one-time curiosity.

The pre-print checklist

Before anything goes to print, run through this. Reprints are expensive and recalls are worse.

• Scanned successfully from the actual final printed proof, not from a screen
• Tested on both an older Android phone and a recent iPhone
• Tested at the real distance, at an angle, and in the actual lighting
• Quiet zone intact, no artwork intruding
• Dark on light, sufficient contrast
• Destination is a short link you control and can repoint later
• Destination page loads fast on mobile data and is mobile-first
• Call to action states the payoff, not "scan me"
• Unique link per placement so results are attributable
• Someone other than the designer has tested it

Skipping the last item is how codes ship broken. The person who made it knows exactly where to point the camera.

Getting started

Pick one placement, not twenty. Generate a code, print a single proof, and test it in the actual environment before committing to a run. You can create a QR code with the free generator, and if you want the design side covered too, the guide on printing QR codes that actually scan goes deeper on materials and pre-press.