QR codes for product packs on flexo
SmartQRCode editorial · Updated October 2026
QR codes for product packs belong on a panel that stays readable after fill and shrink, not on a flat dieline that never leaves prepress. Host the recipe PDF so a legal line does not replate the run. A Canva one-off is enough for a carton mockup that will never ship.
What QR codes for product packs should survive on press
Packaging is flexo, shrink, and curves. Those distort modules. Test-scan the formed pack, not the flat proof. Put the symbol on the flattest panel you can spare. Size at least 2 cm for a phone at about 30 cm on a shelf at arm length. A floor stack read from the aisle needs more.
Host a website QR code, a PDF QR code for the recipe, or an images QR code for a pack gallery. Those stay editable. Flexo pack distortion does not. Spot-colour dark modules should be 100 percent of one ink, not a four-colour build that can fringing-register. Offset and flexo want vector.
This job does not apply to a pitch mockup that will never reach a converter. Canva or another free static generator is enough then. Hosted codes last as long as the provider resolves them.
Converters still want vector, not a screenshot of the on-screen preview. Specify spot-colour dark modules as 100 percent of one ink. After fill, scan the formed pack. A pouch gusset can fold a finder the dieline never showed. Move the mark to the front panel or the lid before you plate.
A recipe that legal still edits belongs on a hosted PDF. A SKU that is the product of record forever can stay in the modules as static ink. Do not plate both decisions as one file.
See QR codes for ecommerce inserts, QR codes for retail shelf tags, QR codes for manufacturing, and packaging QR use cases.
Plate a pack mark the converter can run
- Host the destination. Do not encode a long static URL with UTMs into a small pack mark. More payload densifies the pattern at the same millimetre size. A hosted symbol's density is the short URL.
- Set error correction to H for scuff and a small logo. H restores about 30 percent and densifies the pattern, so keep size honest.
- Leave four empty modules on a solid printed patch. Do not bleed into a photo.
- Export SVG or a PDF with vectors. Vinyl and laser cutters need paths. A PNG sent to a cutter is traced and produces broken corners.
- Specify spot-colour dark modules as 100 percent of one ink.
- Run a formed-pack proof after fill and a shrink-wrap curve scan on the real bottle or pouch.
- Do not screenshot the on-screen preview.
- Paid options are $1.99, $29, $97, or $197.
A pouch gusset is a curve the dieline never showed. After fill, the gusset folds a finder. Move the mark to the front panel or the lid, not the gusset. Shrink-wrap curve scan from a phone at arm length then has a chance. A floor stack read from the aisle still needs more millimetres than a shelf-facing.
Registration on flexo can fringe a four-colour black into grey finders. Spot-colour dark modules as 100 percent of one ink. That is a press instruction, not a brand preference. A PNG sent to a cutter traces broken corners. Vector paths only.
Do not run the first store as the test. The formed-pack proof is the test. If legal still edits the recipe, host the PDF. If the SKU is frozen forever and you will never count scans, a Canva carton mockup is honest for the pitch. It is not a substitute for the converter file.
Why a flat pack proof still fails on the shelf
The curve after fill is the pack-specific failure. Modules that were square on the dieline become wedges. A shrink-wrap curve scan from a phone at arm length then misses a finder. Move the mark to a flatter shoulder or enlarge it.
Gloss varnish under aisle lights can glare. Matte the symbol area if the rest of the pack must stay glossy.
A busy photograph as the light modules fails the same way a street behind glass fails. Print the symbol on a solid light patch.
Line Wi-Fi, if anyone posts it on a case, is static. It is not editable after printing and not trackable.
Can you change the recipe PDF after flexo plates
Yes, when the modules encode a hosted website or PDF. Swap allergens, a film, or a promo without replating. Redirects use 302 so a 301 cache does not freeze the first recipe.
A static URL in the ink cannot move. Honest for a SKU that is the product of record forever. Wrong for a recipe that legal still edits.
Analytics on hosted types count scans, not shoppers. Country comes from headers. They cannot see a name.
A paused hosted code stops resolving. Archived codes keep scanning. If the brand cannot depend on a provider, print static payloads and accept reprint.
When pack codes fail after shrink but pass on the dieline
The formed-pack proof is the required check. Skip it and the first store scan is the test. That is late.
Foil in the modules scatters. White patch first. Dirt in the quiet zone on a filling line is as bad as dirt on the modules.
Do not flatten a photograph of a filled pack and reprint that photograph as artwork. Each generation adds blur.
A pouch gusset folds a finder after fill. Move the mark to the front panel or the lid. Gloss varnish under aisle lights can glare. Matte the symbol area if the rest of the pack must stay glossy. A busy photograph as the light modules fails. Print on a solid light patch. Registration fringe on four-colour black greys finders. Specify 100 percent of one ink. Line Wi-Fi on a case, if anyone posts it, is still not trackable.
When a Canva carton mockup is the honest file
A Canva one-off or other free static generator is the right tool for a mockup that will never ship, never be edited, and never be counted. Hosting that mockup on SmartQRCode wastes a paid option. Using a static file for a live recipe wastes a replate.
ISO/IEC 18004 still governs the modules. The converter RIP does not rewrite that spec.
A pitch dieline that never reaches a press can stay a Canva file. A SKU that will ship next month cannot, unless the destination is frozen forever and you will never count scans. Flexo pack distortion still happens even if the payload is hosted. Hosting does not flatten a pouch gusset. Move the mark off the gusset. Run a formed-pack proof after fill. Run a shrink-wrap curve scan on the real bottle.
Spot-colour dark modules as 100 percent of one ink so register fringe does not grey the finders. Vector to the converter. A PNG sent to a cutter traces broken corners. If legal still edits the recipe, host the PDF type. If the identifier is the product of record and will not move, a static SKU in the modules is honest. Those two decisions look similar in a brand deck and they plate differently.
Questions this raises
Flexo pack distortion, shrink-wrap curve scan issues, and fill all warp modules. A formed-pack proof on the real pack beats a flat dieline. That is a packaging constraint.
Yes if the modules encode a hosted website or PDF. Swap the recipe without replating. A static URL in the ink cannot move.
A Canva one-off or other free static generator is enough for a mockup that will never ship, never be edited, and never be counted. Live packs need a hosted code or a frozen static SKU you accept as uneditable.
No for flexo and offset. Spot-colour dark modules should be 100 percent of one ink so register fringe does not grey the finders.
Vector. Do not send a screenshot of the on-screen preview. A PNG sent to a cutter is traced and breaks corners.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.