A manufacturer has to hold the product data that the delegated act for its product group requires: identification, materials and components, repair and disassembly information, and sustainability performance, linked to a unique identifier and available to authorised parties. The exact fields differ by product, so the first step is reading the relevant act.
Key takeaways
- A digital product passport is a structured record tied to one physical product, and its required fields are set per product group.
- Identification, materials, repair information and sustainability performance are the recurring data groups manufacturers should plan for.
- Persistent identifiers and version history matter as much as the data values themselves.
- Most data already sits in PLM, ERP and supplier systems, so the main effort is integration and validation.
Which regulation requires a digital product passport?
The passport concept comes from the Ecodesign for Sustainable Products Regulation, Regulation (EU) 2024/1781, which sets a framework for product-group requirements and the information that must accompany a product. Read the regulation text on EUR-Lex. Each product group receives its own delegated act, so obligations for one product category can differ substantially from another.
Batteries already have a dedicated regime. Regulation (EU) 2023/1542 requires a battery passport with specified information, and its timing and content are set in its own text. Read the Batteries Regulation on EUR-Lex.
This article is general information and not legal or tax advice. Rui Codex provides technical implementation support only, so the obligations themselves should be checked against the official text and with qualified counsel.
What data does a digital product passport contain?
The data falls into a few recurring groups, although the delegated act for each product group decides which fields are mandatory.
Identification and traceability
This covers a unique product identifier, the manufacturer's identity, model and production information, and the links between a product and its components. Without persistent identifiers, the rest of the record cannot be reliably attached to the physical item.
Materials and substances
Manufacturers need bills of materials detailed enough to show which materials and substances of concern a product contains, including parts sourced from suppliers. Supplier declarations often arrive in inconsistent formats, which can make this the most labour-intensive group to populate.
Repair, reuse and end-of-life
Repairers and recyclers typically need disassembly instructions, spare-part availability and recycling guidance. Adding these to a product designed without disassembly in mind is costly to retrofit, so the requirements belong in design reviews.
Sustainability performance
Some acts ask for performance attributes such as durability or energy use, measured with methods that the act or its referenced standards specify. Record the test method and its version alongside each value, otherwise the number cannot be compared or audited.
Who can see which parts of the data?
Access is tiered: some information is public, some is limited to authorised professionals such as repairers and recyclers, and some is available to market surveillance authorities. Which tier applies to which field is set by the regulation and the delegated act, not by the software you choose.
In practice, a system needs to hold public fields, restricted fields and internal engineering data in separate permission scopes. Mixing them in one table usually leads to either over-exposure or a brittle manual process for releasing data.
Where a record links to an identifiable person, such as a service technician or an owner, GDPR applies to that part of the data. Our notes on security, GDPR and compliance engineering cover access control patterns in more detail.
How should manufacturers structure product data?
Structure the data by product group and by source system first, then add identifiers, versions and access rules. Validate each record before it is published, not after.
- Map every required field for each product group to the system where it is created today, such as PLM, ERP or a supplier portal.
- Assign a persistent identifier to each physical unit or batch, and decide how it is printed or stored on the product.
- Keep version history, so a changed component or supplier does not silently overwrite the record for earlier units.
- Define access scopes for public, restricted and internal fields before building any export.
- Run validation checks for missing mandatory fields and mismatched identifiers before a record is released.
Most manufacturers already hold this data across several systems, so the work is mainly connection and validation. Our system integration services cover linking PLM, ERP and supplier data into one reliable record, and the ERP and CRM integration service covers the business-system side.
Where do passport data projects fail?
Projects usually fail at identifiers, supplier data and version control, not at the publishing step. The table below compares common approaches using qualitative criteria.
| Approach | Works well when | Fails when |
|---|---|---|
| Spreadsheets maintained by hand | Few products and a single owner for the data | Product variants multiply and versions drift between files |
| Stand-alone product information tool | Product data is mostly descriptive and rarely changes | Supplier and engineering data must be kept in sync with it |
| Records linked to existing ERP and PLM data | Source systems already hold the fields and identifiers are controlled | Master data is inconsistent and no one owns the validation rules |
The common failure modes are unverified supplier declarations, identifiers that change when a product is re-labelled, and exports that cannot show what the record looked like at a given date.
Hypothetical examples of passport data gaps
Here are two hypothetical scenarios:
- Scenario A: A manufacturer of household appliances assigns identifiers per model rather than per unit. When a component supplier changes, the team cannot tell which physical units carry the old part, so the material record is either wrong or withdrawn.
- Scenario B: A company that sells industrial equipment stores repair instructions as scanned PDFs. Service partners can open them, but the instructions cannot be linked to the specific variant, so the data is hard to use for the purpose it was meant to serve.
Frequently Asked Questions
Is a digital product passport the same for every product?
No. The passport framework is set by the Ecodesign for Sustainable Products Regulation, but each product group gets a delegated act that defines its required fields, access tiers and timing. Manufacturers should read the act for each product they place on the market rather than assume one template fits all products.
Do manufacturers need a special software product to hold passport data?
Not necessarily. A passport needs persistent identifiers, version history, access control and validation. Those can be built on existing systems or on a dedicated tool, and the right choice depends on how many sources the data comes from and how often it changes.
Who decides which data fields are mandatory?
The delegated act for each product group sets the mandatory fields, so the answer depends on the product. The regulation text is the authoritative source, and questions about how it applies to a specific product should go to the manufacturer and qualified counsel.
Can a passport be built after a product is already on the market?
Often it can, but the gaps are harder to close. Identifiers may need to be applied to existing stock, and historical data about components may be incomplete. Designing the identifier and data flow early is usually cheaper than reconstructing it later.
Conclusion
A digital product passport is a structured record of product data, and its requirements are defined per product group. Manufacturers should start by mapping the fields their acts require, locating the systems that hold them, and assigning persistent identifiers with version history. Rui Codex offers technical implementation support for this kind of integration work. Request a project consultation at ruicodex.com/Contact or email info@ruicodex.com to discuss your project.
Sources
- Regulation (EU) 2024/1781 Ecodesign for Sustainable Products Regulation - EUR-Lex, Publications Office of the European Union
- Regulation (EU) 2023/1542 Batteries Regulation - EUR-Lex, Publications Office of the European Union