What Data Goes into a Digital Product Passport?

A Digital Product Passport connects a physical product with structured digital information. But there is no single universal dataset that applies to every Digital Product Passport.

Under the Ecodesign for Sustainable Products Regulation, the information required for each product category is defined through the applicable delegated act or other sector-specific legislation. This means that the data required for a battery, textile product or piece of furniture may be different.

For textiles and apparel, the final mandatory dataset has not yet been adopted. Companies can nevertheless begin preparing by distinguishing between the information required to operate the DPP system, potential product-specific regulatory data and additional information they may choose to provide.

In short, a Digital Product Passport contains seven key data areas, let’s break these down.

‍

1. Data required to identify and operate the Digital Product Passport

Every Digital Product Passport must connect the physical product with its digital record. The common DPP framework therefore relies on identifiers, data carriers and registration information.

Depending on the applicable legislation, this layer may include:

• a unique product identifier;
• the relevant economic operator identifier;
• facility identifiers where required;
• a data carrier, such as a QR code or another machine-readable medium;
• the applicable product classification or commodity code;
• metadata required to register and discover the passport;
• information needed to manage access rights.

Product data is stored through a decentralised architecture, while the EU DPP Registry records unique identifiers and associated metadata needed for registration, verification and discovery.

‍

2. Product-specific regulatory data

The substantive content of a Digital Product Passport depends on the rules adopted for the relevant product category.

For textiles, areas currently being assessed include information relating to:

• product identity and technical characteristics;
• materials and fibre composition;
• substances of concern;
• durability and care;
• repairability;
• recycled content and recyclability;
• manufacturing and supply-chain stages;
• environmental performance;
• end-of-life information;
• documentation or evidence supporting compliance.

These areas should not be presented as a confirmed mandatory textile dataset. The final delegated act will determine which information is required, at what level of granularity and which users can access it.

Some information may be public, while other data may be accessible only to economic operators, customs or market-surveillance authorities.

‍

3. Where DPP data comes from

The data contained in a DPP rarely comes from one system or department. It may be distributed across internal systems, documents and supply-chain partners.

Typical sources include:

• PLM and PIM systems: product specifications, materials, variants and care information;
• ERP systems: suppliers, production orders, batches and commercial identifiers;
• compliance documentation: declarations, test reports and product-safety information;
• supplier data: manufacturing stages, facilities, materials and supporting documents;
• LCA or environmental systems: product-impact information where required or voluntarily provided;
• e-commerce systems: product content, images and consumer-facing information;
• CRM and service systems: warranties, repairs, ownership registration and post-purchase services.

The first practical step is therefore to map each data point to its source, owner, level of granularity and supporting evidence.

‍

4. Model, batch or individual-item data

DPP information may be associated with a product model, a production batch or an individual item. The applicable granularity will depend on the legislation and the type of information involved.

A company should establish:

• which information is common to an entire model;
• which information changes between batches;
• which identifiers or services require item-level records;
• how updates are managed without duplicating data unnecessarily.

This decision affects identifiers, QR-code generation, production processes, system integrations and the volume of passports that must be maintained.

‍

5. Evidence and data quality

Collecting a value is not the same as demonstrating that it is reliable. Each relevant data point should be connected with the appropriate source or supporting evidence.

Depending on the information, evidence may include:

• supplier declarations;
• invoices and transaction records;
• certificates;
• test reports;
• bills of materials;
• production documents;
• audit results;
• calculation methodologies.

Companies should define who supplies the information, who reviews it, when it must be updated and what evidence must be retained. Third-party verification or certification may be appropriate for certain claims, but should not be described as universally required for every DPP data point.

‍

6. Optional product information and services

A Digital Product Passport can also contain information and services that go beyond the mandatory regulatory dataset.

Depending on the brand and product, these may include:

• product storytelling and manufacturing information;
• care and maintenance guidance;
• repair booking;
• warranty activation;
• authentication;
• ownership registration;
• resale or take-back services;
• recommendations for related products;
• customer registration and post-purchase communication.

These functions can extend the value of the DPP, but they should remain clearly distinguishable from information required for regulatory compliance.

‍

7. How to prepare DPP data

Companies can begin with a structured data-readiness exercise:

1. Identify the products and markets in scope.
2. Map existing product, supplier and compliance information.
3. Record where each data point is stored and who owns it.
4. Identify missing information and supporting evidence.
5. Determine whether data is available at model, batch or item level.
6. Define how suppliers will provide and update information.
7. Connect the relevant internal systems with the DPP process.
8. Establish review, approval and maintenance responsibilities.

This work remains useful even before the final textile dataset is adopted because it creates the governance and technical foundation needed to incorporate the confirmed requirements later.

‍

Ready to Build Your DPP Strategy?

The central question is not simply how much information can be displayed in a Digital Product Passport. Companies need to understand which information is required, where it originates, how it is supported and how it can remain accurate throughout the relevant product lifecycle.

Renoon helps fashion companies define their DPP data model, collect information from internal systems and suppliers, manage supporting evidence and publish scalable Digital Product Passports across collections.

Talk to our team about assessing your Digital Product Passport data readiness.

‍