The Packaging and Packaging Waste Regulation (EU) 2025/40 and the Digital Product Passport framework under the Ecodesign for Sustainable Products Regulation (ESPR) are two regulations on parallel tracks that converge on one piece of architecture: a data carrier (typically a QR code) carrying structured information about a product or its packaging. For manufacturers, the choice is not between PPWR compliance and DPP compliance. It is whether to build two separate systems or one integrated passport that satisfies both. The integrated path is now the dominant approach for brands serving multi-category catalogues.
What Connects PPWR and the Digital Product Passport?
PPWR mandates a data carrier on packaging from 12 August 2028, linking to information on material composition, recycled content, substances of concern, sorting instructions and reusability. ESPR's Digital Product Passport (DPP) mandates a similar data carrier on covered products, linking to lifecycle, durability, repair, and material data. Both rely on the same EU Digital Product Passport infrastructure being defined under the Commission's DPP implementing acts. The connection is technical and increasingly explicit in Commission guidance.
Side-by-Side: Two Regulations, One Architecture
| Aspect | PPWR (Reg. 2025/40) | DPP under ESPR (Reg. 2024/1781) |
|---|---|---|
| Object covered | The packaging | The product itself |
| Data carrier mandatory from | 12 August 2028 | Category by category, 2027 onwards (textiles, batteries first) |
| Conformity assessment | Internal production control (Annex VII) | Per category implementing act |
| Declaration of Conformity | Yes, from 12 August 2026 | Yes, per ESPR category |
| Data content | Material composition, recycled content, SoC, sorting, reusability | Lifecycle, durability, repair, supply chain, recycled content |
| Sister regulations | — | Battery passport (Reg. 2023/1542) |
Both regulations point to the same technical standards stack: ISO/IEC 18004 for QR codes, GS1 Digital Link for URL syntax, the Asset Administration Shell or W3C Verifiable Credentials for structured data, and the emerging European DPP backbone for registration.
Why Build One Passport, Not Two
A finished product on the EU market in 2030 will often need both. A textile garment sold in 2027 needs a DPP under ESPR. Its packaging from 2028 needs a PPWR data carrier. A battery for an e-bike from February 2027 needs a battery passport under Regulation (EU) 2023/1542, and its retail packaging needs a PPWR data carrier from August 2028. Running two parallel systems creates duplicate supplier data flows, duplicate substance-of-concern tracking, and double the integration cost.
The unified architecture treats the product passport as the master, with the packaging passport linked as a child entity. Material composition data, recycled content claims and supplier declarations flow once, then surface twice via two different QR codes pointing into the same database. The battery passport guide covers the precedent in detail.
What Manufacturers Need to Prepare
The build splits into five workstreams. None is unique to PPWR or to DPP, but the August 2026 PPWR Declaration of Conformity date pulls the timeline forward.
- Master data model. Agree on a single product+packaging data schema covering material composition, recycled content, PFAS test results, substances of concern, end-of-life routing, and reusability status.
- Supplier data flows. Issue supplier questionnaires aligned with PPWR Annex VII and ESPR category-specific requirements at the same time. One supplier-side effort, two regulatory outcomes.
- Identifier strategy. Define GS1 Digital Link URLs or equivalent that resolve to product-level and packaging-level passports. Stable URLs survive packaging redesigns.
- Hosting infrastructure. The passport content needs to be available for a regulatory retention period (5 years single-use, 10 years reusable for PPWR; ESPR-specific for products). Brand-hosted, solution-provider-hosted, or registry-hosted, all are valid options.
- Conformity assessment and Declaration of Conformity. Module A internal production control under PPWR Annex VII, plus the ESPR-category procedure for the product. The DoC guide covers the packaging side.
Data Carrier Placement and Hierarchy
One product, multiple QR codes. The arrangement most converging in industry practice:
| Carrier location | Points to | Required by |
|---|---|---|
| On the product (or on a non-removable label) | Product DPP (lifecycle, durability, repair, supply chain) | ESPR per category |
| On the primary packaging | Packaging passport (material, recycled content, sorting) | PPWR Article 11, from August 2028 |
| On the secondary/transport packaging | Transport packaging passport (empty space, reusability) | PPWR Article 11, from August 2028 |
| On the battery (if applicable) | Battery passport (chemistry, performance, recycled content, EU DID) | Battery Reg. 2023/1542, from February 2027 |
| Behind any QR code: link to the EU DoC | Declaration of Conformity for the relevant regulation | PPWR from August 2026; ESPR per category |
Brands building one passport host the entire graph behind whichever QR code is scanned, with the resolver returning the relevant view. Recyclers scanning the primary packaging see sorting data; consumers scanning the product see durability and repair; market surveillance authorities see the DoC.
What is Not Required (Yet)
PPWR does not, on the face of the regulation, mandate a full Digital Product Passport in the ESPR sense for every packaging item. What it mandates is a data carrier from August 2028 linked to a defined dataset. The Commission has flagged in its 2025 PPWR guidance that the data carrier should interoperate with the broader DPP framework, but the underlying registry, identity, and verification rules are still being negotiated through delegated acts. Manufacturers building today are designing for forward compatibility with the EU DPP infrastructure even though the formal PPWR-side acts will land between 2026 and 2028.
Common Pitfalls in Combined Implementation
Three patterns show up repeatedly in pilot deployments:
| Pitfall | Why it happens | Mitigation |
|---|---|---|
| Two separate data lakes, one for product, one for packaging | Different internal teams own each regulation | Single steering committee, shared data model from day one |
| QR code that 404s after redesign | URL tied to a specific SKU revision | Persistent identifiers, redirect logic at the resolver |
| PFAS data captured for PPWR not surfaced in product DPP | Test reports filed by packaging team only | Substance-of-concern data flows up to product level automatically |
| Recycled content claims inconsistent across PPWR DoC and ESPR DPP | Different verification methods, different definitions | One verification chain, one claim, surfaced in both contexts |
| Hosting provider lock-in | Proprietary passport format | Use open standards (GS1 Digital Link, W3C VC, AAS) and portable storage |
Cross-References and Sister Regulations
The PPWR-DPP integration sits inside a broader EU green compliance stack. The PPWR pillar guide covers the full packaging timeline. The PFAS thresholds explainer shows how substance-of-concern data flows through both regulations. The battery passport guide covers the most mature DPP regime today and the technical precedent for the unified architecture.
Frequently Asked Questions
Does PPWR require a full Digital Product Passport?
Not in the ESPR sense. PPWR mandates a data carrier on packaging from 12 August 2028 linking to defined information (material, recycled content, sorting, reusability, substances of concern). The Commission is steering this toward interoperability with the broader DPP framework, but the formal label of "DPP" is reserved for ESPR-covered products.
Can one QR code serve both PPWR and ESPR DPP?
In principle yes, if the resolver returns the right view to the right scanner. In practice, separate QR codes (one on the product, one on the packaging) are clearer for authorities and recyclers, with both resolving into the same backend database. The unified architecture wins on data flow, not on visible identifiers.
When does PPWR data carrier become mandatory?
12 August 2028. The Declaration of Conformity is mandatory earlier, from 12 August 2026, but the physical QR code on packaging follows the harmonised labelling regime starting in 2028. Manufacturers preparing today are designing for the 2028 carrier even as they sign DoCs in 2026.
What standards underpin the PPWR data carrier?
The technical stack converging in industry practice: ISO/IEC 18004 for the QR code symbology, GS1 Digital Link for URL syntax, and the EU DPP backbone for registry and identity. Formal harmonised standards will be cited in PPWR delegated acts landing through 2027 and 2028.