EN Standards for DPP Explained: From Regulation to Real Use Cases

Most of the Digital Product Passport conversation right now is about deadlines. This is the other conversation, the practical one: what the new technical standards actually solve, read from a supply-chain seat rather than a legal one.

Read as a set, the six published EN standards point at one job: making product data usable across many systems without building a custom connection every time. That is an integration problem before it is a compliance one. A large manufacturer with an in-house integration team can absorb it. A growing brand or a lean wholesaler feels it. Closing that gap is the reason Repass exists.

Harmonized standards for the Ecodesign for Sustainable Products Regulation (ESPR) and the Digital Product Passport (DPP)

From standards to concrete use cases

Here is the plain-language map, one standard at a time, with examples of the kind of supply chain each one shows up in, and what it means if you do not have an integration team in the building.

1. Data exchange protocols (EN 18216:2026): moving data between systems

What it does

The average manufacturer already exchanges data. The challenge is that every supplier, customer, technology provider, and DPP platform may use different systems and data structures.

EN 18216 establishes common mechanisms for exchanging DPP-relevant information between systems so that information can move through the value chain without requiring bespoke integrations every time a new partner joins the ecosystem.

Use case 1: sports and outdoor

A performance apparel brand sources:

• recycled polyester from Taiwan
• membranes from Japan
• trims from Germany
• garment assembly in Eastern Europe

Each supplier maintains product information in different enterprise systems. The strategic challenge is not obtaining data. The strategic challenge is exchanging information between systems in a way that remains scalable as the supplier network grows. Without common exchange protocols, every new supplier creates a new integration project—exactly the kind of situation that we are in now.

With EN 18216, the ecosystem can exchange DPP information using common technical principles rather than continuously building one-off connections.

Use case 2: multi-brand electronics retail

A Nordic retailer carries hundreds of electronics brands. 

Manufacturers continuously update product information through their own platforms and service providers. The retailer cannot realistically support a different exchange method for every brand.

The standard enables information exchange across many organizations without requiring retailers to manage hundreds of proprietary data formats.

Use case 3: workwear value chain

A workwear manufacturer collaborates with:

• textile suppliers
• garment producers
• logistics providers
• industrial laundries

Each actor manages operational data within different systems.

The standard provides a basis for moving DPP information across organizational boundaries while preserving interoperability throughout the value chain.

What this means for you

If you onboard suppliers or retail partners often, this is the standard that decides whether each new relationship costs you a fresh integration. Get your data exchange onto common rails early and growth stops being a run of one-off IT projects.

2. Unique identifiers (EN 18219:2026): one identity for every product

What it does 

Digital systems cannot exchange trusted information unless they are talking about exactly the same product, facility, or economic operator.

EN 18219 establishes the identity layer of the DPP ecosystem through globally unique and persistent identifiers.

Use case 1: outdoor footwear portfolio

A global outdoor brand sells hiking boots in multiple markets. The same model may exist in multiple sizes, multiple colors, and multiple production batches. 

All stakeholders need to reference the correct product consistently.

The standard ensures that products can be uniquely identified and resolved across systems throughout the EU ecosystem.

Use case 2: office consumer goods distribution

A distributor manages thousands of products from hundreds of manufacturers.

Different suppliers may use similar naming conventions for products.

The standard provides a persistent identification framework that removes ambiguity when products move between systems, partners and markets.

What this means for you

Clean, unique identifiers are the foundation everything else sits on. Get every model, variant and batch identified consistently and the passport, the carrier and the handoffs between partners all get easier. Skip it and every later step inherits the mess.

3. Data carriers (EN 18220:2026): the link from physical to digital product

What it does 

A passport is only valuable if people and systems can reliably access it.

EN 18220 governs the physical-to-digital connection through technologies such as QR codes, RFID, and NFC. It focuses on requirements for the data carrier itself, including symbology characteristics, encoding methods, error correction, printing and production quality, durability, machine readability, data carrier placement, recognition of DPP carriers, and maintaining the link between the physical product and its digital representation. 

Use case 1: industrial workwear/sports and outdoor

Protective garments experience:

• repeated washing
• industrial processing
• wear and tear
• harsh operating environments

The physical carrier is exposed to significant stress—the same can be applied on many within a sports and outdoor product portfolio. 

The standard addresses requirements around the carrier itself so that the passport remains accessible throughout product use.

Use case 2: building products

Doors/wooden panels or the whole air conditioning system (including all components  installed in a commercial building) may remain in service for decades.

Over time:

• parts are replaced
• maintenance is performed
• ownership changes
• documentation is needed long after installation

The physical carrier must remain discoverable and readable/usable by all relevant stakeholders (from service and maintenance to demolition contractors at the end) long after the original installation.

EN 18220 addresses requirements for maintaining the connection between the physical product and its digital information throughout its intended use

What this means for you

The carrier is a design and durability decision you make early, not a label you add at the end. Choose the wrong one and the passport becomes unreachable exactly when a customer, repairer or recycler needs it. This is where your physical product choices and your data choices meet.

4. Data storage, archiving, and persistence (EN 18221:2026): data that stays accurate for years

What it does 

Organizations change systems, providers merge, platforms disappear, and data infrastructures evolve. The DPP must remain accessible regardless of these events.

EN 18221 addresses storage, persistence, versioning, and archiving requirements. It addresses how Digital Product Passport information can remain available, reliable, and traceable over time (even when systems, organizations and technology providers change).

A combined use case: kitchen appliances/consumer electronics, and anything in between

A refrigerator placed on the market in 2028 may remain in use for 15 years or more.

During that period:

• the manufacturer may replace ERP systems multiple times
• product master data may be migrated between platforms
• warranty and service providers may change
• spare parts information may be updated
• technical documentation may be archived and restructured
• distributors, wholesalers, and retail partners may require access to product information long after the original sale

The challenge is not creating product information. The challenge is ensuring that the information remains accessible, consistent, and traceable years after the systems that originally created it have been replaced.

EN 18221 addresses requirements related to storage, persistence, versioning and archiving so that Digital Product Passport information can remain available despite technological and organizational change.

What this means for you

The real test is not launch day, it is year ten. Ask any DPP setup where the data lives after you have changed core systems twice, and who keeps it accurate. A passport that is not built to persist becomes a liability at the first audit or resale.

5. APIs for lifecycle management and searchability (EN 18222:2026): reaching and updating the passport

What it does

Information only becomes useful when systems can create, update, retrieve, and search it efficiently. Until now, product data has largely sat in silos—barely connected to the wholesale and retail partners who need it, and almost never to the circular economy of repair, resale, and recycling.

EN 18222 focuses on the API specifications that enable Digital Product Passports to be searchable and support the interactions needed throughout the lifecycle of a product's DPP.

Use case: sports and outdoor brand portfolio

A global sports and outdoor company manages multiple brands, thousands of SKUs, numerous seasonal collections, and a broad network of suppliers, manufacturers, distributors, wholesalers, and retailers.

Digital Product Passport information does not remain static throughout a product's lifecycle.

As products move through manufacturing, wholesale distribution, retail, consumer use, repair, resale, sorting, and recycling, different stakeholders may need to search for and interact with the same passport information for different purposes.

The challenge is not creating the passport itself. The challenge is ensuring that passport information remains searchable and can support interactions throughout the product lifecycle, from the first sale to repair, second-life markets, and end-of-life treatment.

EN 18222 focuses on standardizing the API specifications that support the lifecycle management of Digital Product Passports and facilitate their searchability throughout the lifecycle of a product's DPP.

What this means for you

The passport is not written once and filed. It has to stay reachable and updatable as the product moves through repair, resale and recycling. If you plan to do anything real with circularity, this is the layer that makes it work rather than stay aspirational.

6. System interoperability (EN 18223:2026): systems that understand each other

What it does

Systems may successfully exchange data while still failing to understand one another. Interoperability requires alignment at technical, semantic, and organizational levels. In an even more direct manner—let's say today—nearly every system claims an open API and possibility for integration. What is provided, however, is somehow an impractical huge bulk of data that’s not immediately usable. 

EN 18223 focuses on the semantic description of products, common information models, metadata structures, data dictionaries, and the technical and organizational interoperability needed to support a Digital Product Passport ecosystem.

Use case 1: fashion and apparel

A fashion brand works with:

• fiber producers, textile mills, dye houses, garment manufacturers
• distributors, wholesalers, and retailers (as well as all the interconnected ecommerce ecosystem)
• resale platforms and repair ecosystems 
• textile sorters and recyclers

Each stakeholder may describe product information differently.

For example, fiber composition, recycled content, country of origin, product category, care instructions, or end-of-life information may be structured and represented differently across systems and organizations.

The challenge is not simply exchanging information but in ensuring that product information is described, represented and interpreted consistently across multiple stakeholders throughout the product lifecycle.

EN 18223 addresses this through common information models, metadata structures, data dictionaries, and technical and organizational interoperability principles that support a shared understanding of product information across the DPP ecosystem.

Use case 2: wood-based construction materials

A construction product may involve:

• forest owners and their ecosystems
• sawmills, wood processors, component manufacturers
• building material distributors, wholesalers, and retailers
• contractors, building owners
• renovation companies, demolition and recycling operators

The same product information may be needed by different stakeholders for different purposes throughout the building lifecycle (add to that tender and B2B processes demanding access to the same data, as well as requesting traceable circularity, etc.) 

Product attributes such as material specifications, certification information, dimensions, treatment methods, environmental characteristics, and end-of-life considerations may need to be understood consistently across multiple organizations and digital systems.

The challenge is not simply making information available but in ensuring that stakeholders across the construction value chain can interpret product information consistently over long lifecycles and across different systems.

EN 18223 addresses this through common information models, metadata models, data dictionaries, and technical and organizational interoperability requirements that support a consistent understanding of product information across the DPP ecosystem.

What this means for you

For you, this is the line between a passport that technically exists and one your partners can actually act on. If the same data reads differently at each stage, you get compliance on paper and friction in practice. This standard is what decides whether your DPP is a filing exercise or something the whole ecosystem can use.

Where Repass fits

From data exchange to unique identifiers, data carriers, storage and interoperability, a DPP solution provider owns the technical infrastructure so you do not have to build it. That is our job: the identifiers, the physical-to-digital link, the storage and lifecycle, and the integrations with the systems you already run, so the passport is something you have rather than something you engineer.

If you want to work through what these standards mean for your own product range, our upcoming Regulation to Action sessions take one sector or use case at a time. Stay tuned, and get in touch if you want to request coverage of a specific topic.

Background and sources

The Digital Product Passport is built on a set of harmonized European (EN) standards that define its technical backbone: how product data is identified, carried, stored, exchanged, and kept interoperable across systems. Eight standards make up the full set. The first six are now published; the remaining two, covering security and data authentication, are expected to follow.

The European Commission cited the first six through Commission Implementing Decision (EU) 2026/1736 (14 July 2026), giving companies a presumption of conformity with the DPP requirements under the Ecodesign for Sustainable Products Regulation (ESPR), Regulation (EU) 2024/1781. The standards are developed by the CEN and CENELEC joint technical committee for the DPP (CEN-CLC/JTC 24).

Sources: European Commission, harmonised standards for the DPP; Commission Implementing Decision (EU) 2026/1736, Official Journal.