QR codes for a product launch

QR codes for a product launch earn their keep after ship day, when the how-to copy changes and the carton cannot. Day-seven copy without new cartons needs a hosted hop. Formed pack not flat proof is the scan test. Confirm the first week of shelf with a test scan of a unit from the line.

How QR codes for a product launch should change after ship day

Cartons live longer than landing pages. If you encode a static URL, day-seven copy requires new ink. If you encode a SmartQRCode hop, the 302 target can move while the panel stays.

Use a website type when scanners should leave for a storefront. Use a PDF or other landing type when they should stay on a page you designed. Wi-Fi on a launch carton is a static credential; a passphrase rotation reprints the run.

A Canva one-off is right for a launch-night poster that will never be counted. It is wrong for product-launch packaging you cannot call back.

Provider resolution is the trade. If the hop must work with no vendor, the payload has to be static.

Sequence launch codes before the first carton

1. Freeze the day-one destination and list the day-seven changes you already expect (URL, video, PDF).
2. Create a hosted code per SKU you must measure separately. Sharing one hop across three flavours averages them.
3. Put UTM on the hosted destination (content = SKU). Do not stuff the query into static modules.
4. Export SVG for flexo. Dark modules as one ink. Quiet zone inside the panel, not around a curve that will warp.
5. Plate a small live run. Form the pack. Fill it. Shrink it if the line shrinks.
6. Test-scan the formed unit at arm length under shelf lighting, on iOS and Android.
7. Keep a control unit from that live run in the lab. After you edit the destination, scan that unit.
8. Decide pause versus archive for delist. Pause stops the hop. Archive still scans.
9. If you must split panel art, create two hops. Restyling one static URL is not a test.

If step 6 fails, stop the line. Destination edits will not unscrew a warped module.

Packaging scans the formed pack not the flat proof

Flexo, shrink, and curves distort modules. A proofing press on a flat sheet is a different object. Test-scan the formed pack.

Metallic inks and foil need a white patch under the symbol. Uncoated fibre spreads. Size for the shopper's arm, not for a billboard.

Hosted hops do not repair distortion. They only repair the URL.

Landing pages versus a URL hop for launch content

A how-to video and a gallery belong on landing types you can edit. A store locator might be a URL 302. Pick one primary action per panel. Two codes on one small carton fight in the camera.

Scans are not people and not units sold. Do not brief finance with scan totals as sell-through.

Failure modes in the first week of shelf

CMS 404 after a midnight publish. A 301 from a marketing short link freezing the teaser page. Staff scanning every SKU onto one demo phone. Preview screenshots that encoded /qr-preview on an insert. Wi-Fi on the same panel as the product hop.

Walk stores with the control unit's twin. Type the URL as well as scanning.

Outdoor shippers chalk. Plan a reprint cycle for corrugated that lives in sun. The hop can change; the faded pattern cannot.

How to keep SKU hops from collapsing into one dashboard row

First week of shelf failures include a 404 after a CDN purge, a teaser URL that 301s to a sold-out page, and a warehouse that applied flavour-B labels to flavour-A packs. Scan a unit from each flavour in a real store, not in the plant canteen lighting.

Landing page versus URL hop should be frozen on the brief before die-lines lock. Changing type after plates exist means new modules. Changing a hosted destination does not.

Formed pack not flat proof remains true for shippers and counter displays. A shipper that scans in the studio can fail in fluorescent retail lighting because of gloss. Matte the symbol area. Test-scan on the shop floor during week one, then again after the first destination edit using the lab control unit.

Do not put a Wi-Fi join on the carton you cannot reprint. Passphrase rotation would recall the run. If the unboxing needs a network, put Wi-Fi on a throwaway card inside the box. Confirm both scans: carton hop opens the product page, card join hits the SSID, and they are not in the same camera frame on the kitchen table.

If legal requires a static URL on-pack for the life of the lot, that panel is not your editable how-to. Put the hosted hop on the insert. Confirm both: on-pack static still opens the frozen URL, insert hop opens the page you will edit. Do not try to make one 15 mm mark do both jobs.

Day-seven copy without new cartons is the reason to host the how-to hop. Formed pack not flat proof is the reason to delay the celebration until a filled bottle scans under shelf lights. Landing page versus URL hop is the reason to freeze type before dies lock. First week of shelf failures are 404s, 301 teasers, and mislabelled flavours. Scan a unit of each SKU in a real store. Keep a lab control unit for destination edits. Pause on delist; archive still scans. A static regulatory URL on-pack can coexist with a hosted insert. They are two quantities and two encoding classes. A Canva one-off is the launch-night poster that will never be counted, not the carton you cannot call back. Provider resolution remains the trade on every hosted panel.

Shrink wrap and curves on a launch bottle can pass a flat proof and fail in a fridge door. Test-scan a cold, formed unit, because condensation is a contrast problem that studio photos hide. If it fails wet, matte the symbol and enlarge. Destination edits will not dry the plastic.

When a launch insert is a static PDF and hosting is wasted

A regulatory insert that cannot change for the life of the lot, with no need to count scans. Print static at a size that survives the fold. A free static generator is the honest tool.

When the insert is a recipe you will swap, print a hosted PDF type, keep the carton hop separate if you need two metrics, and test-scan both after every content save. Do not encode two jobs in one 15 mm mark.