.png)
Many organisations already manage large amounts of product information. Material composition, supplier data, product specifications, environmental information, repair instructions and certifications are often stored across different systems within the organisation.
Digital Product Passport implementation introduces a new question: is that existing data ready to function as Digital Product Passport data?
The Ecodesign for Sustainable Products Regulation (ESPR) establishes Digital Product Passports as a way of making product information available digitally. To support data exchange across the European Union, Digital Product Passports are designed around structured, machine-readable and interoperable product information.
New technical documentation published by the European Commission now provides a more concrete view of how DPP data will be structured, interpreted, validated and exchanged across systems.
Most companies already hold much of the information that will eventually populate a Digital Product Passport. The challenge is not always collecting additional data, but preparing existing information so that it can be exchanged, interpreted and maintained consistently throughout the product lifecycle.
A product specification stored as a PDF is digital. A spreadsheet containing supplier information is digital. Product information stored in an ERP or PLM system is digital too. However, digital information is not automatically Digital Product Passport-ready.
Preparing product information for a passport involves more than converting papers into digital files. Information also needs to be organised using consistent data models, identifiers, language and definitions so that different systems can process it reliably and exchange it without ambiguity.
Two companies may already be able to exchange product information electronically. That alone does not guarantee that their systems interpret the information in the same way.
Imagine a product identifier stored as “Model” in one system and “Style” in another. Both may refer to the same information, but unless those fields are mapped to a shared definition, software cannot automatically determine that they represent the same product attribute.
The same principle applies when information is prepared for the Digital Product Passport Registry. Data needs to match the expected structure, field definitions and formats so that it can be interpreted consistently across systems rather than simply transferred.
Semantic interoperability ensures that product information carries the same meaning wherever it is used. As Digital Product Passports connect manufacturers, suppliers, service providers and the future Registry, this shared understanding becomes essential for making product data reusable across the value chain.
Digital Product Passport interoperability operates at different levels.
EN 18222:2026 covers the APIs used to search, retrieve and manage Digital Product Passports throughout their lifecycle. EN 18223:2026 addresses system interoperability and the common data model that allows different DPP systems to work with compatible product information.
The European Commission made this framework more concrete on 30 October 2026 by publishing its first technical guidance for integrating economic operators’ systems with the DPP Registry. The resources include API specifications and guidance covering authentication, registration submissions, processing outcomes and error handling.
These technical connections allow systems to exchange information. Semantic interoperability addresses the next question: whether the receiving system can understand that information in the intended way.
Otherwise, two systems may successfully exchange a value while interpreting it differently.
On 30 October 2026, the European Commission published the first version of the DPP Registry Semantic Data Guide, together with the corresponding semantic artifacts.
The framework is organised across three layers:
The framework connects several types of semantic and technical resources:
These resources are versioned so systems can identify which definitions and validation rules were used for a particular Digital Product Passport.
The Semantic Data Guide is aligned with EN 18223:2026 and explains how the same underlying data model can be represented consistently across JSON, JSON-LD, XML and RDF. The Registry registration process will use JSON as the mandatory exchange format referenced by EN 18216:2026.
This framework does not determine the final product information required for textiles or other categories. Those data requirements will still be established through the applicable product legislation and delegated acts. Instead, it provides the structure through which those requirements can be expressed, validated and exchanged consistently.
Alongside the Commission’s Registry resources, CIRPASS-2 has published its own ontology documentation and a proposal for an EU DPP Core Ontology.
The CIRPASS-2 model separates concepts that can apply across product groups from sector-specific extensions. Its Core Ontology covers areas including products, passports, actors, identifiers, materials, substances of concern, compliance, lifecycle events and LCA information.
Sectoral ontologies then extend this common foundation. The candidate Textile Ontology 2.0.0, aligned with the October 2026 CIRPASS-2 Core baseline, includes modules covering textile composition and structure, manufacturing processes, durability, assessments, repairability, recyclability and substances of concern.
These resources help illustrate how common and sector-specific product information could be modelled without redefining the same concepts in every system.
However, the CIRPASS-2 ontologies must be distinguished from the Commission’s semantic resources. They are exploratory, remain under development and do not represent an official or legally binding EU DPP ontology.
The new technical resources do not require companies to build their own ontology or redesign every internal system. They do, however, reinforce the need for a product-data model that can be mapped to shared definitions and adapted as official requirements evolve.
Companies can begin by:
DPP readiness depends not only on having the required information, but on ensuring that different systems can exchange, interpret and update it consistently.
Renoon supports companies in structuring and connecting product data across internal systems, suppliers and Digital Product Passport infrastructure.
Speak with our team about preparing your product data for Digital Product Passports.