One mark on a pack can be asked to do several different things.
A square symbol does not explain its job. A product may need a retail identifier for sale, a consumer route to ingredients or instructions, a code for a campaign, or a serial or batch reference for a process outside the print itself. Those are different jobs. A code can look perfectly scannable and still carry the wrong data, point to an old destination or sit in the wrong part of the pack.
Write one plain-language sentence for each code: “This is the code a checkout must recognise,” “this opens the current product page,” or “this identifies a batch in our own system.” That sentence gives the brand owner, designer and packaging contact a shared reason for the mark before anyone decides on its appearance.
Do not remove a retail barcode simply because a QR code works on a phone.
Retail systems are changing at different speeds. A brand may need a traditional linear barcode and a 2D code to coexist while its channels, retailers and scanners are confirmed. A phone-camera test proves only that one path works in one moment. It does not confirm that a retailer can sell the item, that a data service recognises the identifier, or that the intended consumer journey is the one being opened.
Keep the decision with the people who own the product data and the sales channel. They should confirm the identifier format, any GS1 requirement, retailer expectations and whether two codes are required on the same pack. Printing begins after that decision is expressed in the approved artwork.
Give every code an owner and a source.
A code should not be copied from an old label, a screen grab or a last-minute message. Record where it came from, who can approve it and what it is allowed to change. For a connected pack, that record may include the approved GTIN or product identifier, the exact destination URL, the organisation that controls the destination, the product or market it belongs to, and the date or version checked.
If a marketing team owns the landing page but a product team owns the product data, name both responsibilities. If a code is generated from a database or supplier system, retain the source export and a human-readable reference. That makes it possible to spot when a code belongs to last season’s SKU rather than the pack currently on the table.
Code placement is a packaging decision, not a last-minute graphic detail.
A flat dieline can make every panel look equally safe. Once the carton is folded, a code can land near a tuck, crease, glue area, curve, reflective finish, opening edge or another barcode. It may be hard for a customer to find or easy for a scanner to confuse with a nearby symbol. Leave the quiet space required by the code specification and use the confirmed packaging template, not a generic measurement copied from another carton.
Also consider the person holding the object. A retail code may need an easy, consistent position. A consumer-facing route may deserve a panel that is visible after purchase. If the same product has several language, market or pack-size versions, check that the right code travels with the right physical version.
Test the pack someone will handle, not only an image on screen.
Test the current destination and the intended scanning route using the actual artwork at the proposed size. A phone scan is a practical usability check; it is not a substitute for a relevant retail or standards verification route. Where a retail channel or standards body has a test or verification requirement, follow that route as well. Look at the assembled sample: can the person find the code, is its quiet area intact, does the correct product information open, and is another barcode likely to be read first? Record what was tested and who accepted the result.
That final check matters most when a code carries a price, batch reference, safety information, regulated copy or an after-sales route. The print proof can help confirm the approved artwork version; it does not transfer responsibility for the brand’s product data, retailer readiness or digital destination.
Hand over the code brief with the packaging brief.
Bring code artwork or the approved generation source, its purpose, the product/version it belongs to, the owner of the data, the proposed panel, any human-readable text, the final dieline, material/finish direction and the person who can approve the printed version. If any point is still open, mark it as open. It is safer to quote a decision that needs checking than to turn an unfinished code choice into a silent production assumption.