What the EU Digital Product Passport actually is
A Digital Product Passport (DPP) is a structured digital record attached to a specific product. It holds information about what the product is made of, where it came from, how to repair it, how long it should last, how to recycle it, and how to dispose of it responsibly. You reach that record by scanning a QR code on the product itself or on its packaging.
Think of it as an identity document for a physical object. A passport for a person links a face to verified records held by an authority. A Digital Product Passport links a physical item to verified records held by its manufacturer and made available across the supply chain. The QR code is the page you flip to — the record lives behind it, hosted and maintained, and updated over the life of the product.
The concept is deliberately open about the carrier but specific about the outcome. The regulation calls the scannable mark a "data carrier," and in practice that data carrier is almost always a QR code because phones decode QR natively and consumers already know what to do with one. Scan it and you land on a web page or a structured data record for that exact product, not a generic brochure for the product line.
Two things make a DPP different from the QR code you already put on a poster or a business card. First, it must resolve to data about a unique product or batch, not a static marketing URL. Second, that data has to stay available and accurate over time, which turns the QR from a one-off print job into a long-lived link into a maintained system. That distinction — a durable identifier backed by a real data system — is the whole game, and it is where the engineering lives. If you are new to structured product QR data, our GS1 QR code guide is the companion piece to this one.
Why the EU built it — sustainability, circularity, transparency
The Digital Product Passport is not a standalone idea. It is one instrument inside the Ecodesign for Sustainable Products Regulation (ESPR), Regulation (EU) 2024/1781, which is the EU's framework for making products sold in Europe more durable, more repairable, and easier to recycle. The passport is the transparency layer that makes those goals enforceable and visible.
The policy problem it addresses is information loss. Today, most of what is known about a product — its material composition, its carbon footprint, whether a specific part can be replaced, whether it contains substances that complicate recycling — is scattered across suppliers, or simply never recorded in a place a repairer or recycler can reach. When the product reaches end of life, that knowledge is gone, so the object gets landfilled or downcycled instead of repaired, reused, or properly recycled. The DPP is designed to carry that information with the product, for the product's whole life.
There are three motivations stacked on top of each other. Sustainability: give repairers and recyclers the data to keep materials in use longer. Circularity: make it economically practical to reuse components and recover materials instead of extracting new ones. Transparency: let buyers, regulators, and customs see verifiable claims instead of unverifiable green marketing. A brand that says a jacket is recyclable now has to be able to back that claim with data reachable from the product.
That framing matters for anyone planning a rollout, because it tells you what the passport has to contain and how long it has to survive. This is not a campaign QR you retire after a season. It is closer to the durable, structured product records used by regulated industries — the same instinct that drives QR adoption in energy and utilities, where an asset's data has to remain reachable for years after it ships.
How a QR code carries the passport — the data carrier
The regulation does not say "put a QR code on it" in those words. It says the passport must be accessible through a "data carrier" linked to a unique product identifier. But in every practical implementation the market has settled on, that data carrier is a QR code, for the same reason QR won consumer-facing retail: a phone camera decodes it with no app, and buyers already understand the gesture.
Here is the mechanism, step by step. The product gets a unique identifier — unique to the item, the batch, or the model, depending on the category rules. That identifier is encoded into a QR code as a resolvable web address. When someone scans the QR, their phone opens that address, and a resolver behind the address routes the scan to the correct passport record for that exact product. The record itself is served from a data system the manufacturer or its provider maintains.
The critical piece most explainers skip is the resolver. A DPP QR is not a link straight to a file. It is a link into a lookup system, so that the same printed code can point at up-to-date data even after the product ships, and so that a scan can be routed to the right record no matter which country the buyer is in. That is exactly why the EU is standing up a central registry (covered in the next section): to guarantee a scan resolves to the correct product record across the whole single market.
The QR generation itself is the easy part. Any competent generator can encode a resolvable URL into a durable, scannable code — that is what a URL QR code is. The hard part is everything behind the URL: assigning persistent unique identifiers, running the resolver, and keeping the data accurate for the product's life. When a single QR needs to route to different destinations or records over time, that is the territory of dynamic and multi-URL QR codes plus a backend — not a static print-once code.
The two dates that are locked in
Most coverage of the Digital Product Passport is vague about timing, which is unhelpful when you are trying to plan a product launch. So here are the two dates that are firm, and a clear statement of what is not yet fixed.
19 July 2026 — the central EU DPP Registry goes live. The EU is standing up a central, EU-wide registry so that a product QR scan resolves to the correct product record across the entire single market. This is the routing backbone: it is what lets one scanned code find the right passport regardless of which member state the scan happens in. The registry going live is the infrastructure milestone that the category-specific rules plug into.
18 February 2027 — the Battery Passport QR requirement becomes mandatory. From this date, a QR-code-retrievable Battery Passport is mandatory for EV batteries and industrial batteries above 2 kWh placed on the EU market, regardless of the country of origin. This comes from the Battery Regulation (EU) 2023/1542, a separate regulation from the ESPR, and it is the first hard, product-specific DPP deadline to arrive. If you make or import qualifying batteries, this is the date on your calendar.
What is deliberately not on this list is a fixed all-categories timeline. The ESPR phases the passport in category by category through delegated acts, and those category rules — for textiles, furniture, electronics, and others under discussion — are still being defined. Anyone quoting you a specific year for a specific category beyond batteries is getting ahead of the published rules. Plan against the two firm dates, and track your own product category as its delegated act firms up.
| Milestone | Date | Legal basis | What it means |
|---|---|---|---|
| Central EU DPP Registry goes live | 19 July 2026 | ESPR — Regulation (EU) 2024/1781 | A product QR scan resolves to the correct product record EU-wide. |
| Battery Passport QR becomes mandatory | 18 February 2027 | Battery Regulation (EU) 2023/1542 | QR-retrievable passport required for EV and industrial batteries above 2 kWh sold in the EU, regardless of country of origin. |
| Other product categories | Being defined category by category | ESPR delegated acts | Textiles, furniture, electronics and others are phased in as each category rule is finalized. Watch your specific category. |
Tips
- The two firm dates are 19 July 2026 (registry live) and 18 February 2027 (battery passport QR mandatory). Treat everything beyond those as "category rules still being written."
- The battery deadline applies to products placed on the EU market regardless of where they are manufactured. A battery made outside the EU and sold into it still needs the passport.
- The 2 kWh threshold and the EV/industrial scope matter. A small consumer battery is not the same regulatory object as an EV traction pack.
Who is affected — batteries first, then other categories
The order of the rollout is the practical part. Batteries go first, and they go first with a hard date, so battery makers and importers are the group that has to move now.
Batteries, from 18 February 2027. If you manufacture or import EV batteries or industrial batteries above 2 kWh for the EU market, the Battery Passport QR requirement applies to you on that date, no matter where the battery is made. The passport has to carry the battery-specific data set the Battery Regulation defines and be retrievable by scanning the QR on the product. This is the clearest, nearest, non-negotiable DPP obligation in force.
Everyone else, on a category-by-category schedule. The ESPR is a framework regulation. It sets up the passport mechanism and then delegates the detailed rules for each product category to separate acts. Textiles, furniture, electronics, and other categories are under active discussion, but the specific obligations and dates for each are set when that category's delegated act is finalized. That is why this article does not give you a textiles date or an electronics date — those are not yet fixed, and inventing them would be worse than useless for planning.
The honest way to read your own exposure: if you sell physical products into the EU, a Digital Product Passport is very likely coming to your category eventually, but the timing depends entirely on where your category sits in the delegated-act queue. Consumer-facing sellers in ecommerce, fashion and clothing, and consumer electronics should be watching this closely, because those categories are exactly the ones the EU has signaled as early candidates — without committing to public dates yet. Watch, prepare your data, but do not print a compliance claim you cannot yet substantiate.
What data a Digital Product Passport holds
The exact fields depend on the product category, because each delegated act defines the data set for its category. But the shape is consistent across categories, and it is worth understanding because it tells you why a DPP is a data-system problem, not a printing problem.
A passport is built to answer questions across the whole life of the product: what is it, what is it made of, how do I keep it working, and what happens at the end. The battery passport is the most concrete example available today, and it points toward the pattern the other categories will follow — identity, composition, performance, and end-of-life handling, all reachable from one scan.
The table below is an illustrative view of the categories of information a passport is designed to carry. Treat it as the shape of the data, not a field-by-field spec — the binding list for any given product is its category's own rule.
The reason this matters for planning: none of this data lives in the QR code. A QR code holds a URL, and the URL resolves to a record. All of the substance — composition, provenance, repair instructions, recycling guidance, updates over time — lives in the backend the URL points at. Getting the QR right is a week of work. Getting the data model, the persistent identifiers, and the resolver right is the actual project.
| Category of data | Examples | Why it is in the passport |
|---|---|---|
| Identity | Unique product/batch/model identifier, manufacturer, model | Ties the physical item to its record so a scan finds the right passport. |
| Materials and composition | Material breakdown, substances of concern, recycled content | Enables recyclers to sort and recover, and buyers to verify claims. |
| Origin and supply chain | Country of manufacture, key supply-chain facts | Supports customs, due-diligence, and provenance transparency. |
| Use and repair | Repairability information, spare-parts and maintenance guidance | Extends product life and supports the right-to-repair goal. |
| Performance and durability | Expected lifespan, performance and, for batteries, state-of-health data | Lets buyers and second-life users judge condition and value. |
| End of life | Recycling, disposal, and take-back guidance | Keeps materials in circulation instead of landfill. |
GS1 Digital Link — the encoding layer behind most DPPs
If a DPP QR is a resolvable URL, the obvious question is: a URL in what format? The answer that most serious implementations are converging on is GS1 Digital Link, and it is worth understanding why, because it connects the DPP to standards that already exist rather than inventing a new silo.
GS1 Digital Link is a way of writing a product URL so that the same code carries a structured product identifier and can be resolved to different data for different audiences. A supply-chain scanner reads it as structured identity data; a consumer phone opens it as a web page. That is precisely the dual-audience behavior a Digital Product Passport needs — a customs officer, a recycler, and a shopper all scan the same printed code and each gets routed to what is relevant to them.
The practical appeal is that GS1 Digital Link builds on identifiers and infrastructure that global retail and supply chains already use, rather than requiring a brand-new numbering system. If your products already carry GS1 identifiers for retail — the world our GS1 QR guide covers in depth — the DPP resolver can plug into the same identity backbone. For a brand shipping into mainstream retail, that reuse is a large part of why Digital Link keeps coming up in DPP discussions.
None of this changes the honest split we keep returning to. Constructing a Digital Link URI and encoding it into a QR is straightforward, and a standard URL QR code does that job. Running the resolver that maps the URI to a live, maintained, category-compliant passport record is enterprise infrastructure — a PIM system, a GS1-certified provider, or a purpose-built DPP platform. The QR is the visible tip; the resolver and the data system are the iceberg.
What a business should do now
The right first move depends entirely on which of two situations you are in, and confusing them is the most expensive mistake available.
If you make or import qualifying batteries. You have a hard date — 18 February 2027 — and a specific data set defined by the Battery Regulation (EU) 2023/1542. This is enterprise compliance work. Engage a DPP or battery-passport solution provider, assign persistent unique identifiers, stand up the data backend and resolver, and plan the QR placement on the product. Do not treat this as a QR-generator task; treat it as a product-data-system task with a QR at the end of it.
If you sell other physical products into the EU. Your category's rules are still being written, so the smart posture is preparation, not premature compliance. Start collecting the data a passport will need — material composition, sourcing, repairability, recyclability — because that inventory is the long pole regardless of the eventual date. Watch your category's delegated act. And do not print a "DPP-compliant" claim before your category rule exists, because an unverifiable claim is exactly what the transparency regime is designed to catch.
For everyone. Separate the two jobs cleanly. The passport backend — identifiers, resolver, maintained data — is the regulated capability, and it belongs with an enterprise DPP platform or a GS1-certified provider. The everyday QR codes around your product and its launch — the PDF spec sheet, the landing page, the packaging insert, the retail display — are ordinary marketing and information QR codes, and those are a solved, cheap problem. Knowing which bucket a given code falls into is most of the clarity you need. Businesses in supply-chain-heavy categories like logistics and freight forwarding and food brands are already fluent in this split — regulated structured data on one track, consumer QR on the other.
Tips
- Do not confuse generating a QR with building a passport. The QR is a week; the identifier scheme, resolver, and maintained data backend are the real project.
- Battery makers and importers: 18 February 2027 is a hard date, not a target. Start the enterprise-provider conversation now.
- Everyone else: collect your product data (materials, sourcing, repairability, recyclability) now. It is the slow part, and it is useful regardless of your eventual category date.
Where EZQR fits — and where it does not
Let us be direct about this, because the point of an honest explainer is not to sell you the wrong tool.
EZQR is not a Digital Product Passport compliance platform. We do not assign the persistent unique identifiers a DPP requires, we do not run the EU-registry resolver, and we do not host or maintain the regulated product-data records behind a passport. For a battery passport under the Battery Regulation, or any future category obligation under the ESPR, the right tools are a dedicated DPP platform, a GS1-certified solution provider, or your own product-data infrastructure. If someone sells you a consumer QR generator as "DPP compliance," walk away.
What EZQR is good at is every other QR code in the same product's life. The URL QR code that points at a launch page. The PDF QR code on a spec sheet or a care guide. The multi-URL code on packaging that you want to re-point later without a reprint. The codes on your flyers, your retail displays, your trade-show booth, your invoices. That is the everyday QR work around a product, and it is a genuinely different job from the regulated passport itself.
There is also a real reason durability matters here even for the non-regulated codes: a QR printed on physical product packaging should not silently break if a subscription lapses. EZQR codes keep redirecting even if you stop paying us, which is the property you want on anything that ships on a physical good with a long shelf life. Our Pro tier handles bulk generation and scan analytics across large SKU counts, which is useful when you are printing the surrounding informational codes at scale.
So the honest summary: learn the Digital Product Passport, plan it as the enterprise data project it is, and pick a DPP-specific provider for the regulated passport. Then use a straightforward QR code generator like EZQR for the everyday codes around it. Two different jobs, two different tools — and knowing the difference is the whole value of understanding what a DPP really is.
