The Digital Product Passport needs a data carrier. A QR code is the obvious one.

OpenQR

The Digital Product Passport needs a data carrier. A QR code is the obvious one.

Most sustainability deadlines stay abstract until they do not. The first Digital Product Passport date is fixed and close: from 18 February 2027, batteries sold in the EU must carry a QR code giving access to prescribed information, with a full passport for EV, light-means-of-transport and larger industrial batteries. The rest of the product landscape follows through the EU's ecodesign regulation, category by category, over the coming years. For a packaging team, the passport itself is a data project. The part that lands on your artwork is a data carrier, and the carrier is the cheap half. This page is about getting the carrier onto the pack in a way that survives whatever the final rules say.

The dates that are actually fixed, with the hedge stated

Battery Regulation (EU) 2023/1542: from 18 February 2027 every battery placed on the EU market carries a QR code linking to required information, and EV, light-means-of-transport and industrial batteries over 2kWh also need a full battery passport. The framework regulation for everything else, ESPR (EU) 2024/1781, phases products in category by category through delegated acts, each carrying a transition period of at least 18 months, with an EU product registry live since July 2026. Which categories follow, and exactly when, is still being settled act by act. OpenQR generates codes and hosts redirects; it does not advise on whether your product is in scope. Check your category's timetable with a source that tracks EU product regulation.

What the passport actually asks of the pack

A passport is structured product data: identity, materials, chemistry where relevant, repair and disassembly information, end-of-life handling. Some of it is for consumers, some for recyclers and regulators. None of it lives on the pack. What the pack needs is a data carrier that anyone, with any phone, can scan to reach that data for the specific product in their hand. That is a narrower requirement than it sounds, and it is the only part of the regulation that packaging artwork has to satisfy. The project that matters, building and maintaining the data behind the link, belongs to the product and compliance teams, and it is where the real effort and the real deadlines live.

Why the QR code is the carrier that won

The regulation does not mandate a symbology, but the arguments resolve quickly in one direction. Every phone in the world already reads QR codes natively from its camera, which no other 2D symbology can claim. Capacity is ample for a URL carrying structured identifiers. And retail is moving its own tills to 2D barcodes anyway, on GS1's timetable for the end of 2027, so the same printed square that serves a regulator can also serve checkout and the shopper. That convergence is why most compliance guidance treats the QR code as the default answer rather than one option among several. See the GS1 Digital Link page for how the identifier itself is structured.

The move that is not wasted, whatever the final rules say

Whatever your category's eventual delegated act says about the data, the pack-side move is the same and it is useful today: one QR code per SKU, printed on the pack, pointing at a product page you control, generated as a dynamic code so the destination can change without a reprint. Today that code serves marketing and customer information. When the category's passport requirements land, the destination is repointed at whatever passport data page the rules require, and no artwork changes. The code that was a product link becomes the compliance carrier by editing a URL. A static code cannot do that, and a pack that sits on a shelf for two years does not care that the regulation moved after it was printed.

What not to do

Three failure patterns are already visible. Printing a code that points at nothing but a marketing landing page and calling the pack passport-ready: it is not, and the gap will be found by whoever enforces it. Waiting for complete certainty before any code goes on the pack: certainty arrives act by act, and the reprint cycle means the pack in front of you was designed a year ago. And minting a separate compliance code alongside the marketing one: two codes on one pack is confusing artwork, twice the proofs and twice the quiet-zone fights, when one well-chosen destination behind one code does both jobs. Decide the destination architecture once, per product family, rather than per deadline.

A 2026 readiness sequence that costs almost nothing

  1. 1

    List the SKUs that sell into the EU

    By product family, not by variant, because the artwork architecture follows the family.

  2. 2

    Check each family's timetable

    Batteries are fixed for February 2027. For everything else, find your category's delegated act status before promising anyone a date.

  3. 3

    Stand up the product pages

    A stable page per SKU that you control, which is worth having regardless of regulation.

  4. 4

    Mint dynamic codes per SKU into the next artwork round

    Bulk generator, one row per SKU, SVG at the die-line size. No separate compliance code.

  5. 5

    Keep the register

    The CSV and manifest are the audit trail of which pack carries which code. Reprints read from it, not from archaeology.

On cost, because it is usually the first question in the meeting: the codes themselves are the trivial line. Static codes are free and unlimited; dynamic codes are free for three and then Pro at £9 a month, which is rounding error next to the artwork change it rides on. The compliance cost is the data page and the product information behind it, and that is a project regardless of which carrier is chosen. Choosing the QR carrier does not add meaningful cost to it; it is the only carrier that does not.

Compliance is a property of the product data and the pack, not of the code generator. OpenQR produces the carrier: the QR code on the pack and the redirect behind it. Whether your product is in scope, by when, and what the linked data must contain are questions for a source that tracks EU product regulation.
Part of Product packaging

Related