Why DPP Standards Matter for Businesses

A Digital Product Passport program involves many stakeholders: product compliance teams, sustainability teams, IT departments, suppliers, manufacturers, importers and market access specialists. Without common standards, each party may describe store or exchange product information differently.

This creates risks such as fragmented product data, inconsistent identifiers, inaccessible records, weak traceability and limited interoperability between systems.

The standards shown in the toolkit help businesses avoid these issues by creating a more consistent structure for DPP data. They support a common approach to product identity, digital access, data exchange, lifecycle management, long-term availability and system-to-system alignment.

For companies preparing for DPP requirements, the key question is not only:
“What data do we need?”

It is also:
“How will this data be identified, accessed, exchanged and preserved?”

1. EN 18219: Build the Identity Foundation

The first step in the toolkit is EN 18219: Unique identifiers.

This standard focuses on creating globally usable identifiers for products, operators and facilities. In practical terms, this means that companies need a clear way to distinguish products at the correct level of detail, such as model, batch or item granularity.

A strong identification structure is the foundation of any DPP program. Without it, product information may be difficult to connect, retrieve or validate across supply chains.

For businesses, this stage should answer questions such as:

• What product level needs a DPP?
• Which identifiers are already used internally?
• Are identifiers consistent across suppliers, facilities and systems?
• Can identifiers support future traceability and compliance needs?

Getting this stage right helps prevent confusion later in the DPP process.

2. EN 18220: Create the Physical-to-Digital Link

The second step is EN 18220: Data carriers.

Data carriers are the physical or printed elements that make DPP information accessible from the product. This may include technologies such as QR codes or other carrier formats, depending on the product and applicable requirements.

This standard helps companies think about how users, authorities, supply chain partners or other stakeholders will access the digital information connected to a product.

For businesses, this means considering:

• Where the data carrier will appear on the product or packaging
• Whether the carrier remains readable during the product lifecycle
• How the carrier connects to the right digital record
• How product design, packaging and compliance teams coordinate the implementation

This step is essential because a DPP must be accessible in a practical and reliable way.

3. EN 18216: Enable Secure Data Exchange

The third step is EN 18216: Data exchange protocols.

Once a product can be identified and linked to digital information, companies need a secure and interoperable way to exchange DPP data across platforms. This is where exchange protocols become important.

DPP data may need to move between manufacturers, suppliers, compliance systems, market surveillance authorities, customers, recyclers or other stakeholders. If every system exchanges information differently, the value of the DPP is reduced.

This standard supports the exchange layer by helping define protocols and formats for sharing DPP data.

For companies, this stage should focus on:

• How DPP data will be shared
• Which platforms need to exchange information
• What security and access considerations apply
• How data formats can support interoperability

This step helps move the DPP from a static record to a usable digital compliance and transparency tool.

4. EN 18222: Manage DPP Data Through APIs

The fourth step is EN 18222: APIs for lifecycle management and searchability.

DPP information is not always static. Product data may need to be searched, retrieved, updated or managed during the product lifecycle. APIs help support these operations through standardized digital interfaces.

This standard is especially relevant for companies managing large product portfolios, multiple suppliers or complex compliance data.

APIs can support:

• Searchability of DPP records
• Retrieval of product information
• Updates to lifecycle data
• Integration with internal or external systems
• More efficient data management workflows

For business teams, this stage is where compliance, IT and data governance need to work closely together. The objective is to make DPP data usable, maintainable and accessible through structured processes.

5. EN 18221: Preserve Data Over Time

The fifth step is EN 18221: Data storage, archiving and data persistence.

A DPP program must consider what happens to product information over time. Products may remain in use for many years. Operators may change. Systems may be upgraded. Business relationships may evolve.

This standard focuses on making sure DPP information can remain archived, replicated and available over time.

For companies, this means asking:

• Where will DPP information be stored?
• How long must records remain available?
• What happens if a supplier, operator or system changes?
• How will archived information remain accessible?
• How will the company manage data continuity?

This step is important for long-term compliance readiness and product lifecycle transparency.

6. EN 18223: Prepare for System Interoperability

The sixth step is EN 18223: System interoperability.

A DPP program becomes more valuable when different systems can work together. This requires more than technical connectivity. It also requires alignment of semantics, metadata and interoperability rules.

In simple terms, systems need to understand each other.

This standard supports the ecosystem layer by helping DPP systems align in a way that enables cooperation across platforms and stakeholders.

For businesses, interoperability helps support:

• Better data exchange between systems
• More consistent product information
• Reduced duplication of work
• Stronger supply chain coordination
• Improved readiness for future DPP-related requirements

This final step connects the previous five layers into a broader DPP ecosystem.

Recommended Kick-Off Order for DPP Readiness

The toolkit presents a practical order for launching a DPP program:

This sequence is useful because it helps companies avoid starting too late in the process. For example, building APIs before defining reliable product identifiers may create rework. Similarly, planning interoperability without clear data storage and persistence rules can create long-term gaps.

A strong DPP program should start with the product identity foundation and then build toward broader data exchange and ecosystem interoperability.

Business Benefits of a Standards-Aligned DPP Approach

Following a standards-based DPP structure can help companies improve both compliance readiness and operational efficiency.

Key business benefits include:

Better product traceability

Unique identifiers and reliable data carriers help connect product records to the right product, batch or item.

More consistent compliance data

Structured data exchange and lifecycle management reduce fragmentation across teams and systems.

Improved supply chain collaboration

Standardized protocols and interoperability rules make it easier for stakeholders to share and understand product information.

Stronger long-term record availability

Storage, archiving and persistence support access to DPP information over time.

More scalable digital compliance processes

A structured DPP foundation can help companies manage larger product portfolios more efficiently.

For companies operating in complex markets, this is not only a technical topic. It is a business readiness topic that affects compliance, market access, supplier coordination and customer trust.

How ComplyMarket Can Support Your DPP Readiness

ComplyMarket supports companies in navigating product compliance and global market access challenges with a practical, structured and business-focused approach.

For organizations preparing for Digital Product Passport implementation, ComplyMarket can support by helping teams:

• Understand the role of DPP-related standards in product compliance planning
• Map product data requirements against internal systems and supplier information
• Structure product identification and documentation workflows
• Improve readiness for data exchange, lifecycle management and traceability
• Identify gaps in product compliance information and supporting records
• Coordinate compliance, sustainability, product and supply chain teams around a clearer DPP roadmap

A successful DPP program requires more than a digital record. It requires reliable product data, clear responsibilities, structured workflows and a long-term approach to information management.

ComplyMarket helps businesses move from uncertainty to action by supporting the practical steps needed to prepare for Digital Product Passport requirements and future market access expectations.

Conclusion

The DPP Standards Kick-Off Toolkit provides a clear starting point for companies preparing to launch a Digital Product Passport program. By following the six-step sequence — Identify, Link, Exchange, Manage, Preserve and Interoperate — businesses can build a stronger foundation for product data, compliance readiness and system interoperability.

Digital Product Passports will require coordination across departments, suppliers and systems. Companies that begin with a standards-aligned approach will be better positioned to manage product information with clarity, consistency and confidence.

For businesses preparing for the next stage of digital product compliance, now is the time to assess data structures, close documentation gaps and build a practical roadmap for DPP readiness.