Answer in brief
EU law establishes the passport framework, but textile-specific requirements are still being developed. Fashion teams can prepare stable product identity, evidence-backed material data and governed supplier records without treating future fields as final.
Start with what the law actually fixes today
Fashion teams face an awkward planning problem: the Digital Product Passport is no longer a policy concept, but the textile rulebook is not yet complete. Regulation (EU) 2024/1781, the Ecodesign for Sustainable Products Regulation, establishes the framework under which products can be required to carry a passport. It sets architecture-level requirements such as a persistent product identifier, a data carrier and controlled access to the relevant passport information. It does not by itself mean that every garment sold today must carry the same finished set of fields. Under the regulation, product-specific delegated acts define the information and requirements for the covered product group.
The European Commission currently treats textiles and apparel as a priority under the ESPR working program and is developing the textile-specific delegated act. Its DPP implementation pages publish an indicative schedule, including a planned adoption window in 2027, but the Commission also cautions that the timeline can evolve. That distinction matters for product teams. Build the data foundations that will remain useful under almost any final rule, but label anticipated fields as readiness assumptions rather than legal requirements. A system designed around a draft spreadsheet can become expensive technical debt if the final delegated act changes granularity, access rights or evidence expectations.
Product identity is the record's load-bearing layer
A passport is only useful if everyone knows which product the data describes. Fashion makes that harder than it sounds because a commercial style can branch into colors, sizes, seasons, factories, material substitutions and later production runs. Decide which identifier represents the model, which represents a sellable variant and, where a future requirement or business case calls for it, which represents an individual physical item or batch. Keep those relationships explicit. A composition record attached to 'Jacket A' is unreliable if a later colorway uses a different lining and the system cannot distinguish them.
ESPR requires the passport to be associated with a persistent unique product identifier in accordance with the applicable rules, and the data carrier must connect the physical product, its packaging or accompanying documentation to that record as specified. The practical lesson is broader than QR placement: identity has to survive catalog redesigns, e-commerce migrations and supplier changes. Do not use a mutable product title as the primary key. If the business adopts standards such as GS1 identifiers, use them consistently rather than inventing parallel identifiers in every department. Standards can support interoperability, but their use should be distinguished from whatever the final delegated act legally requires.
Materials need evidence, not descriptive prose
The material section should be built as structured evidence. For each component, record what it is, where it is used, the declared composition, the unit or percentage basis, the supplier that supplied the information, the document or test supporting it, the date received and the person or system responsible for acceptance. A garment can contain shell fabric, lining, interlining, thread, elastic, coating, trims and hardware; flattening all of that into one marketing sentence makes later verification difficult. If a supplier changes a fiber blend, the data model should expose which finished products and production lots are affected.
The Commission's current textile DPP material indicates that product identity, characteristics and fiber composition are among the types of information being considered for the sector. That is directionally useful, but it should not be treated as the final mandatory schema before the delegated act is adopted. Build the internal record at a finer level than the public display. The consumer view may ultimately show a concise composition, while an authority or business process may need the underlying source and version. This separation lets a company correct a claim without destroying its evidence trail and makes supplier declarations testable rather than decorative.
Supplier provenance should be a graph, not a single country field
A useful passport system needs to know where a claim came from even when the final public interface does not reveal every commercial relationship. At minimum, connect material records to supplier identities and, when available and appropriate, the relevant production or processing facilities. Keep the supplier's own identifier, the business's internal identifier and any standardized location identifier as separate mapped fields. Then record the evidence relationship: who declared the fiber composition, who supplied a certification, which facility was within its scope, and when that evidence expires or changes. Provenance is more valuable than a generic 'made in' field because it allows a claim to be traced back to its source.
Supplier data also needs change control. Fashion collections routinely substitute materials because of availability, cost or performance. A procurement change that is harmless commercially can invalidate an environmental or composition statement if the passport still references the old input. Contracts and onboarding should therefore require suppliers to notify defined changes and provide data in an agreed structure. This is a recommended operating practice, not a claim that ESPR imposes one universal supplier-contract template. The objective is to make the future compliance task auditable: when a field becomes mandatory, the company can identify its authoritative source instead of emailing factories months later to reconstruct evidence.
Care and repair data should change what a person can do
A care field is useful when it helps the owner preserve the actual item, not when it merely repeats generic sustainability language. Record validated washing, drying, ironing and specialist-care instructions at the correct product variant. If a finish, print or membrane needs different treatment, that difference belongs in the data. Repair information can be similarly concrete: construction details relevant to replacing a button, zip, lining or other serviceable component; compatible spare-part references where the company supports them; repair channels; and instructions that can be safely provided. If a repair step requires professional equipment, say so rather than publishing an oversimplified procedure.
This is also where product teams can create value beyond minimum disclosure. A passport can become a durable service surface for updated care guidance, repair documentation or verified spare-part references, provided that updates remain governed and the record makes version changes clear. The future textile delegated act will determine which sustainability and circularity information must be included, so teams should keep required and optional fields separate. A useful internal taxonomy might mark each field as legal, anticipated, service, or evidence-only. That prevents a product manager from accidentally presenting a voluntary repair feature as a statutory passport requirement.
Ownership and lifecycle events require a privacy boundary
Fashion discussions often jump from product passports to resale histories, repairs and ownership transfers. Those services can be valuable, but they are not the same thing as the core regulatory product record. A garment's identity can remain persistent without storing the owner's name, address or purchase history in the public passport. If a resale or warranty service needs ownership information, keep that personal data in a purpose-built system or logically separated layer with its own lawful basis, retention rules and access controls. The product record should not become a permanent public dossier on the people who possessed the item.
Lifecycle events can still be modeled without exposing a person. A verified repair could append an event type, date, service-provider reference and changed component to the product history if that serves a defined purpose and is compatible with the final rules. Authentication or resale systems could reference the item identifier without publishing customer information. This distinction is important because ESPR's DPP architecture is about product information and role-based access, not a license to centralize unlimited behavioral data. Treat privacy minimization as a design requirement from the beginning; removing unnecessary personal data later is much harder once external partners depend on it.
One passport can have several legitimate views
Do not model the passport as a single web page with every field visible to everyone. ESPR anticipates access rights that depend on the data and actor, and product-specific rules will specify relevant access. Design a data service in which a public consumer view, a repair view, an economic-operator view and an authority view can draw from the same governed record without receiving identical information. A fiber composition might be public; a supplier evidence document may be restricted; an internal quality note may never belong in the passport at all. This also reduces the temptation to publish commercially sensitive material simply because it is useful for compliance teams.
Interoperability matters because the record has to survive beyond one brand's current software stack. CIRPASS describes the passport concept as a structured collection of product-related data connected to a unique identity and governed access, while GS1 proposes standards-based identifiers and event mechanisms as one route to interoperable implementation. Those sources are useful implementation context, not substitutes for the regulation. Keep the regulatory field model, identifier standard, storage architecture and consumer interface as separable layers. Then a future legal change can alter one layer without requiring the business to rebuild every product page and supplier integration.
Build a readiness backlog that can survive the delegated act
A sensible 2026 program starts with data quality, not a glossy passport front end. Inventory current identifiers; map style, variant, batch and item relationships; identify the systems that own composition, supplier, care and certification data; and flag fields that exist only in spreadsheets or PDFs. Choose a common evidence pattern that records source, date, scope, owner and version. Pilot it on a small number of products with intentionally messy supply chains, because the cleanest hero style will not reveal the gaps. Test how a material substitution propagates and whether the public record can be corrected without losing the previous evidence.
Then maintain a legal-delta register. When the Commission publishes draft or final textile requirements, compare them against the internal schema and mark each requirement as already supported, partially supported or missing. Avoid freezing current indicative assumptions into supplier contracts as if they were permanent law; instead require the ability to provide defined product data and evidence in updateable formats. The best digital product passport fashion program before the delegated act is one that increases traceability now while preserving the ability to change. Readiness means the company can map final legal fields to trustworthy data quickly—not that it guessed every future field years in advance.
Practical checklist
- Create stable identifiers for product models, variants and physical items where item-level identity is required by the future use case.
- Map every material and composition claim to a named evidence source and responsible supplier.
- Separate public consumer fields from supplier-confidential and authority-access fields.
- Version care, repair and material records so a correction does not erase history.
- Define how supplier changes, substitutions and production-lot changes trigger data updates.
- Track the Commission's textile delegated-act process rather than freezing today's indicative field list into a permanent schema.
Questions and answers
Are digital product passports already mandatory for all fashion products in the EU?
No. The Ecodesign for Sustainable Products Regulation, or ESPR, is already in force and establishes the legal framework for digital product passports, but a passport becomes mandatory for a particular product group through the applicable product-specific rules. The European Commission currently lists textiles and apparel as a priority group and is developing the relevant delegated act. Its published implementation timeline is indicative, not a substitute for the final legal text. Fashion companies should therefore prepare data and systems now while avoiding claims that today's anticipated textile fields or dates are already fixed obligations.
What information should a fashion company collect first for a future product passport?
Start with information that is both foundational and difficult to reconstruct later: stable product and variant identifiers, fiber and material composition, supplier and facility references where available, the evidence behind composition or sustainability claims, care instructions, repair-relevant construction information and controlled links to certifications or test records. Keep a source, date, owner and version for each material claim. This creates a useful evidence spine even if the final delegated act changes the exact mandatory field set. Do not collect personal ownership data by default; that is a different data-governance problem and should have a defined purpose and lawful basis.
Does a digital product passport need to expose all supplier information publicly?
Not necessarily. ESPR's passport framework supports differentiated access rights, and the information made available depends on the applicable delegated act and the user's role. A consumer may need product identity, care, repair or environmental information, while authorities or authorized supply-chain actors may require different evidence. Commercially sensitive supplier details should not be published simply because they exist in the underlying system. Build an access model that separates the public presentation from restricted evidence, and retain the provenance needed to support claims. The final textile-specific rules will determine which fields and access levels are legally required.