QR Codes and Data Carriers: The Pack's Digital Layer

A data carrier on packaging - in practice a QR code - is the regulation's channel for everything the printed face cannot hold: reusability status and the system behind it, substance-of-concern information, detailed sorting and return instructions, and the recycled-content basis. The framework treats the destination as regulatory content: it must be accurate, maintained, and reachable for as long as the pack circulates. That makes the QR an information-architecture commitment, not a graphic element - the code is printed in an afternoon, and its destination must be governed for years.

This guide covers the architecture that honours the commitment: durable addressing, versioned content, ownership, and the separation between the regulatory layer and the marketing layer that may sit alongside it but never instead of it.

Print the identifier, not the destination. Mature practice (the GS1 Digital Link pattern is the working model) encodes a stable identifier in the code and resolves it through a maintained resolver to the current content - so a reorganisation of your website never orphans a million printed packs. The resolver's rules are the governance: regulatory content served without marketing interstitials, language following the market of sale, availability treated as an operational SLA rather than a web team's aspiration. Businesses printing codes before their resolver discipline exists are manufacturing future findings at production speed. The artwork approval gate should therefore include a resolver test: scan the proof, reach the governed content, in the market's language, with no campaign in between.

The content behind the code inherits the technical file's disciplines. Versioned, with validity periods matching the placing they describe (a 2029 pack's scan should not silently present a 2032 formulation's data as its own); updated on the same triggers as the file (specification, substance and system changes); and archived in superseded versions, as the disclosure guide in the substances station prescribed. Ownership sits with regulatory or product stewardship, with the digital team as publisher - the reverse arrangement produces beautiful pages of unverifiable vintage. Accessibility and low-connectivity behaviour belong in the specification too: the consumer at the bin, on one bar of signal, is the user this system exists for.

Nothing prevents the same code from offering brand content beyond the regulatory layer - recipes, loyalty, story - provided the regulatory content is reached first, completely, and without the brand layer's consent walls, app installs or data capture standing in front of it. The boundary failures are recognisable: the code that resolves to a campaign that ended; the code captured by a regional marketing redirect; the code whose regulatory page sits three taps behind a promotion. Each is a governance failure before it is a design choice, and each is preventable by the resolver rules above. Print the code once; govern it forever; let marketing visit under licence.

A code that does not scan is a label that does not exist. Print specifications for data carriers belong in the packaging specification proper: minimum size and quiet zones, contrast on the actual substrate (metallic and dark grounds defeat naive artwork), print-process capability (flexo versus digital tolerances), and scan testing on production samples as a release criterion - including after the pack is filled, chilled, condensed upon or abraded, in the states the consumer actually meets it. Include the failure data in the specification's review: a carrier family with a known scan-failure pattern on one substrate is a corrective action, not a statistic.

Close the infrastructure guide with the metric that keeps it honest: scan analytics, reviewed like any service. Resolution success rate, time to content, language match, content currency per family - a carrier fleet reporting 80 percent successful resolution has a compliance defect with a number on it, and the number is the management tool. Few businesses instrument their printed codes today; the ones that do discover their failures (dead resolver rules, regional redirect errors, content rot) while they are still cheap. The code is the only part of the technical file the public can audit continuously; run it like you know that.