What Is a Digital Product Passport for Fashion?
A Digital Product Passport (DPP) is a structured digital set of product information connected, through a data carrier, to a persistent unique product identifier. Under the EU Ecodesign for Sustainable Products Regulation (ESPR), product-specific delegated acts determine which information must be included, who can access it, who may update it, and whether the passport applies at model, batch or item level.
For fashion businesses, the important point is that a DPP is not simply a QR code or a digital label. The code is an access mechanism. The passport depends on structured product information, reliable identifiers and data that can remain accurate and up to date over the relevant product lifecycle.
Why the Digital Product Passport matters to fashion
Textile apparel is one of the priority product groups identified in the ESPR Working Plan 2025–2030. The European Commission currently indicates Q4 2027 as the planned adoption period for the delegated act covering textile apparel. The detailed textile-specific DPP requirements are still being developed, so businesses should distinguish between requirements already established by the ESPR framework and requirements that will only become clear through the future textile delegated act.
This distinction matters. Preparing for DPP does not mean guessing a final list of mandatory textile fields today. It means understanding the data foundations that will be needed to respond efficiently when the product-specific rules are finalised.
A DPP is more than a QR code
A QR code can point a user to information, but the DPP framework goes further. The ESPR requires the passport to be connected through a data carrier to a persistent unique product identifier. The regulation also establishes requirements around interoperability, structured and machine-readable information, access rights and the ability to keep DPP data accurate, complete and up to date.
The applicable delegated act will determine details such as:
- which data must be included;
- which data carrier or carriers must be used;
- where the data carrier must appear;
- whether the DPP operates at model, batch or item level;
- which actors can access which information;
- which actors can create or update particular data;
- how long the passport must remain available.
This is why a DPP implementation should not be reduced to generating a page and attaching a QR code to it.
What information can a Digital Product Passport contain?
The exact requirements for textile apparel are not final as of September 2026. The ESPR nevertheless defines the framework within which product-specific requirements will be established.
Depending on the applicable delegated act, the DPP can include information associated with product identification, relevant sustainability or circularity requirements, actors and facilities, compliance information and other data required for the specific product group.
For fashion companies, practical preparation therefore begins by understanding where reliable information already exists across product master data, materials and components, suppliers, operations and traceability records.
The goal is not to place every internal business field into a public passport. Different actors may receive different access rights, and product-specific rules will determine what is required. The goal is to know where the relevant information originates and whether it can be maintained reliably.
DPP, product data and traceability
Three concepts are closely related but should not be treated as interchangeable.
Product data describes the product: its identity, variants, components, materials and other structured characteristics.
Traceability connects products, materials, processes and evidence through explicit relationships and provenance.
The Digital Product Passport makes required product information accessible according to the applicable rules and access rights.
A robust DPP therefore depends on more than presentation. If displayed information cannot be connected to reliable sources, kept current or related correctly to the product it describes, the passport risks becoming another disconnected information layer.
Why provenance matters
Knowing a value is useful. Knowing where that value came from is often more useful.
For traceability and DPP-related evidence, Floonexa’s product model distinguishes the recorded value from its provenance: source, actor or system, time and relationship to the relevant product, material or process.
This distinction is particularly important when information originates from multiple systems, suppliers or operational activities. A field that says a material has a particular characteristic is not automatically equivalent to verified evidence supporting that statement.
A practical DPP data architecture should therefore preserve the relationship between information and its authoritative source whenever that relationship matters.
How does a Digital Product Passport work?
At a simplified level, a DPP can be understood as a sequence:
- Relevant product information is gathered.
- The product is associated with a persistent identifier.
- The DPP is created and registered where required.
- Required information remains available through the applicable data carrier and access mechanisms.
- Authorised actors update data when the applicable rules allow or require it.
- The DPP remains available for the period required by the relevant legislation.
The European Commission’s DPP Registry became operational in July 2026. Product data remains stored in a decentralised manner, while economic operators register each DPP in the Registry, which stores unique product identifiers and associated metadata. Registration is available through a secure user interface or API. This does not mean that textile-specific obligations are already final: the sector-specific rules for textile apparel still depend on the future delegated act.
What should fashion companies do now?
The most useful preparation is not to predict every future field. It is to improve data readiness.
Fashion businesses can start by asking:
- Do we have a clear product identity model?
- Can we distinguish styles, variants, batches and individual items where relevant?
- Are materials and components represented consistently?
- Can important information be traced back to its source?
- Do supplier-provided data and evidence have clear ownership and provenance?
- Can we update information without losing historical evidence?
- Can relevant information be shared without exposing data that should remain private?
- Are our systems capable of exchanging structured data rather than relying only on manual documents?
These questions are useful even before the final textile-specific DPP requirements are published because they address durable information-management problems.
DPP should not become a disconnected data island
One of the main implementation risks is treating the DPP as a separate database populated only for compliance.
That approach may create duplicated information, unclear ownership and expensive maintenance. A more sustainable architecture connects the passport to the product and operational sources that already own the relevant information.
In Floonexa, DPP is a separately activatable capability. It can consume canonical product information and traceability evidence without forcing DPP-specific processes into every operational workflow. This keeps the passport connected to the wider supply-chain context while preserving clear ownership of the underlying data.
Digital Product Passport and the wider fashion supply chain
The immediate commercial reason for implementing a DPP may be regulatory preparation. But the work required to create reliable passports exposes a broader question: how well is product and supply-chain information structured today?
The same foundations that support DPP can improve product-data consistency, supplier collaboration, traceability and the ability to understand what happened during production and logistics.
This is where DPP can become more than a compliance project. It can become a practical reason to improve the quality and connectivity of product and supply-chain data.
Frequently asked questions
Is a Digital Product Passport mandatory for fashion in 2027?
Not as a blanket rule from 1 January 2027. As of September 2026, the European Commission indicates Q4 2027 as the planned adoption period for the ESPR delegated act covering textile apparel. The final act will define the sector-specific requirements and applicable implementation arrangements.
Is a DPP just a QR code?
No. A QR code can be used as a data carrier, but the DPP is the structured product-information system connected to a persistent unique product identifier and governed by requirements for interoperability, access and data maintenance.
What data will fashion companies have to include?
The final textile-specific data set is not yet established. The applicable delegated act will determine which data must be included, the required level of granularity, access rights and update responsibilities. Companies can prepare now by improving product identity, structured product data, provenance and interoperability.
Key takeaways
- A Digital Product Passport is not simply a QR code.
- The ESPR establishes the horizontal DPP framework, while textile-specific requirements will be defined through a future delegated act.
- The European Commission currently indicates Q4 2027 for planned adoption of the textile delegated act.
- DPP data must ultimately be connected to reliable product information, identifiers and appropriate sources.
Traceability and provenance help establish where information comes from and how it relates to the product. - Fashion companies can prepare now by improving product-data structure, evidence provenance and interoperability rather than guessing the final textile data set.
- In Floonexa, DPP is a separately activatable capability connected to product data and traceability rather than a replacement for the wider supply-chain platform.
Want to see how Floonexa connects product data, traceability and Digital Product Passport readiness across fashion supply-chain operations?
Dario Corbelli
25 years of experience in information technology, software development, technology governance and management. At Floonexa, he focuses on the technological direction of the platform and on translating complex operational requirements into scalable digital solutions.

