How to use packaging and shelf QR codes for a new product launch

Packaging and shelf QR codes need different launch plans. Packaging may travel through several Retailers and remain useful after purchase; shelf material belongs to a specific placement and retail context. Give each code a clear purpose, maintained destination and tested print specification, then map reporting only to information the route actually carries.

Separate the two jobs

A shelf code might help someone compare the models on a particular bay. A packaging code might explain box contents before purchase and setup afterwards. Avoid assuming a universal packaging code can identify the selling Retailer or current store without an additional, supported source of context.

| Decision | Packaging QR | Shelf QR | | --- | --- | --- | | Main context | Product pack before and after purchase | A particular retail placement | | Production dependency | Packaging artwork and supply chain | POS print and installation | | Useful destination | Product information with relevant pre- and post-purchase paths | Named model or comparison for that Retailer | | Reporting scope | Encoded Product or batch context | Encoded placement, cohort or store context | | Long-term ownership | Product lifecycle owner | Campaign or retail account owner |

Agree Brand and Retailer destination rules before production. For shared packaging, use an appropriate neutral Product companion and clear Retailer choices where needed. Do not silently claim to know where a pack was bought.

Prepare print and destination together

Write a benefit-led prompt, such as “See what is in the box” or “Compare these models”. Encode a stable, owned route if the destination must change later. Keep the mapping between artwork, Product, batch and landing Experience in a controlled register.

Preserve the code’s clear border and test the actual print proof. DENSO WAVE specifies a quiet zone four modules wide around a standard QR Code; final size also depends on the symbol and print requirements. See its QR code area guidance. Test curvature, finish, glare and scanning distance on the final carrier rather than prescribing one universal centimetre size.

Use this destination register

| Field | Entry to complete | | --- | --- | | Carrier and artwork version | Pack panel, barker or shelf position | | Product and local model code | Approved identifier | | Retailer and location scope | Named store, cohort, or not identifiable | | Managed route and owner | URL and responsible team | | Opening question | What the prompt promises | | Pre-launch and live states | Approved destinations and release condition | | End-of-campaign path | Continued Product information or replacement |

Keep embargoed details unavailable until the approved release. A useful early-scan page should explain the available next step without exposing restricted information or returning a broken destination.

Test the whole Shopper journey

Scan from a physical proof on representative phones, over likely connections and at the intended shelf position. Verify the exact Product, language and Retailer destination. Check navigation, accessibility, required privacy choices and fallback information.

A link to a stock checker lets someone check availability; it does not mean your Experience has live stock data. Label any availability claim according to the actual integration and update process.

Read the results at the supported scope

Define QR access Events and QR-origin Sessions separately. Exclude known tests using documented rules. Report at store level only when a reliable store-specific mapping exists. A universal pack code or shared cohort code cannot provide that detail by itself.

Use recorded activity to understand which information participants opened. Do not equate scans with distinct Shoppers, verified physical compliance or completed purchases.

QR launch checklist

• Packaging and shelf tasks specified separately
• Clear prompt matched to the opening Experience
• Owned destinations and lifecycle responsibilities recorded
• Quiet zone and final print performance checked
• Embargo, live and retirement states tested
• Reporting scope matches the actual encoded context

Connect printed material to useful Product information

MyPlayer supports Experiences accessed through QR and other Touchpoints. Scope the Product journey and location mapping with the teams responsible for packaging, print and retail execution. Discuss your QR launch Experience.