Fashion is one of the first industries the EU is targeting with the Digital Product Passport, and the reason is simple: textiles generate more waste per euro of revenue than almost any other consumer category, and today almost none of that waste is tracked. A garment's fiber blend, its chemical treatments, and its repair options are locked away in supplier paperwork that never reaches the retailer, let alone the customer. The Digital Product Passport (DPP) is the EU's attempt to fix that by attaching a structured, machine-readable data record to every garment sold in the bloc. For textile brands, this is not a distant compliance exercise. It is a data architecture problem that needs to start now, well before the final technical requirements are locked in.
A Digital Product Passport is a structured, digitally accessible record tied to a specific product or batch. For textiles, it captures information across the full lifecycle: what the garment is made of, how it was produced, how durable and repairable it is, and what happens to it at end of life. The data lives in a digital registry and is accessed through a unique identifier, typically a QR code, printed on or attached to the product.
Textiles were named a priority product category under the EU's Ecodesign for Sustainable Products Regulation (ESPR) for a specific reason: the sector combines high volume, short product lifecycles, and deeply fragmented supply chains. A single T-shirt can pass through a cotton grower, a spinning mill, a dye house, and a cut-and-sew facility across four different countries before it reaches a retailer. Today, almost none of that chain is captured in a format a brand, regulator, or recycler can actually use.
The DPP is designed to close that gap. Instead of a label that goes out of date the moment a garment is resold or repaired, the DPP is a living record that can be updated and queried throughout the product's life, from first sale through resale, repair, and recycling.
For brands, the shift is not cosmetic. Supply chain data that used to sit privately in spreadsheets and supplier emails now has to be structured, standardized, and, in part, publicly accessible. That changes how procurement, quality, and sustainability teams need to work together, because the data one team collects now has to be usable by regulators, resale platforms, and recyclers it was never built for.
The DPP does not replace the physical care label sewn into a garment. Legal minimums like fiber content and care instructions will still need to appear on the garment itself. What changes is the depth and durability of the information behind it.
| Aspect | Physical label | Digital product passport |
|---|---|---|
| Data depth | Fixed, limited to a few printed data points | Dozens of structured data fields per product or batch |
| Updates after sale | None, printed at manufacture | Can be updated across the product lifecycle |
| Verification | Not independently verifiable | Linked to certifications and supply chain records |
| Access | Visible only on the physical garment | Accessible via QR code from anywhere in the supply chain |
| Audience | Consumer only | Consumers, regulators, recyclers, and resale platforms |
A useful way to think about it: the physical label tells you what the garment is. The DPP tells you where it came from, how it was made, and what to do with it next.
The legal basis for the textile DPP is the Ecodesign for Sustainable Products Regulation, which entered into force on July 18, 2024. ESPR is a framework regulation. It does not itself specify the exact data fields for textiles. Those come through product-specific delegated acts, which are currently being developed with technical input from the EU Joint Research Centre.
For brands, the practical timeline looks like this: delegated acts for textiles are expected to be adopted over the next one to two years, followed by a transition period of at least 18 months before the requirements become mandatory. Based on current EU planning, that points to enforcement landing somewhere in the 2027 to 2028 window, though the exact date depends on when the delegated act is formally adopted.
Two details matter more than the exact date. First, the obligation applies at the product level, not based on company size or revenue, so smaller brands selling into the EU are in scope on the same terms as large groups. Second, the requirement applies to any company placing textile products on the EU market, regardless of where that company is headquartered.
The exact field list is still being finalized through the delegated act process, but the direction is already clear from the JRC's technical studies. Expect the textile DPP to require:
None of this is exotic data. Most of it already exists somewhere in a brand's supply chain. The challenge is that it is scattered across suppliers, formats, and systems that were never built to feed a single structured record.
Repairability sits at the center of the textile DPP because it connects directly to the EU's circular economy goals: garments that can be repaired stay in use longer and out of landfill or incineration. The current technical proposals treat repairability through two fields: a robustness score that reflects how well a garment holds up over repeated washing, and a set of repair instructions with contact information for repair services offered by the brand.
This is different from a single, simplified repairability index like the one already used in some national markets for other product categories. The EU textile approach is closer to structured, verifiable data than a single consumer-facing score, at least under the current draft. Brands should not wait for the final scoring methodology before acting. The underlying capability, being able to state accurately how a garment performs after repeated wear and where it can be repaired, needs to exist in the product data model regardless of the exact scoring formula the EU lands on.
Textile supply chains are structurally different from the other product categories already covered by DPP requirements, such as batteries or electronics. A battery has one bill of materials and one manufacturer of record. A garment often has none of that certainty.
Fashion supply chains are long and multi-tiered, frequently running from raw fiber through spinning, weaving or knitting, dyeing, and cut-and-sew, often across several countries and multiple subcontractors at each stage. Getting consistent, verifiable data out of that chain means engaging suppliers who may have never been asked for structured data before, and who have no direct commercial relationship with the brand.
Product turnover compounds the problem. A battery or an appliance might stay in a catalog for years. A fashion brand can run through thousands of SKUs a season, each with its own fiber blend, dye lot, and supplier mix. Attaching a durable, accurate data record to that volume of short-lived products is a fundamentally different engineering problem than doing the same for a small number of long-lived electronics products.
Certification patchwork adds a third layer of difficulty. Textile supply chains already carry a mix of overlapping certifications, GOTS, OEKO-TEX, and others, each with its own scope and audit cycle. None of them was designed to map cleanly onto the DPP's data fields, so brands need a data model that can absorb multiple certification schemes without treating each one as a one-off integration.
A textile DPP program has to solve four problems at once: identifying each product uniquely, collecting data from a fragmented supplier base, storing and versioning that data over the product's life, and exposing it through a QR code linked to the EU's digital registry.
In practice, this points toward an architecture built around four layers. A unique identifier layer assigns a persistent ID to each product or batch, usually encoded in a QR code or, for higher-value items, an RFID tag. A data collection layer brings supplier data in through APIs, EDI, or structured supplier portals, since manual data entry does not scale to fashion's SKU volumes. A central data layer, often built on or alongside an existing product information management (PIM) system, stores and versions the record so it can be updated after repairs, resale, or recycling events. A publishing layer exposes the required subset of that data to the EU registry and to the QR code a consumer or recycler scans.
None of this needs to be built as a single monolithic system. Most brands already have fragments of it: a PIM system for product data, supplier onboarding tools, and certification records held somewhere in procurement. The work is less about buying new software and more about defining a shared data model that all of those fragments feed into consistently.
One design decision matters more than the others: whether the passport is defined at the product level or the batch level. A garment made from a consistent, single-origin material can carry a stable, reusable data record across a full production run. A garment blending fibers from multiple suppliers or dye lots may need batch-level granularity, since composition and environmental footprint can shift between runs. Deciding this early shapes how much supplier data you need to collect, and how often you need to refresh it.
Brands do not need to wait for the final delegated act to start preparing. Three actions matter most in the next 12 months:
Brands that treat this as a last-minute compliance sprint will end up retrofitting data collection onto systems that were never designed for it. Brands that start building the data foundation now will be able to absorb the final delegated act requirements as a configuration change rather than a rebuild.
Mimacom works with manufacturing and retail clients on exactly this kind of problem: connecting fragmented supplier data into a single, reliable architecture that can serve both internal operations and external regulatory requirements. Our engineering teams have built supplier integration layers, PIM-centered data models, and traceability systems for clients managing complex, multi-tier supply chains. For textile brands facing DPP, that experience translates directly into faster, lower-risk architecture decisions, because the data model gets defined once, correctly, instead of being patched category by category as new EU requirements land.
It is tempting to treat the textile DPP as a labeling problem: pick a QR code vendor, print a new tag, done. The actual work is upstream of that. The QR code is just a pointer. What matters is whether the data behind it is accurate, current, and structured well enough to survive a repair, a resale, or a recycling event. Brands that get the underlying data architecture right will meet the EU's requirements as a byproduct of running a better-managed supply chain, not as a separate compliance layer bolted on at the end.
There is no fixed date yet. The legal basis, ESPR, has applied since July 18, 2024, but the textile-specific requirements depend on a delegated act that is still in development, followed by a transition period of at least 18 months. Based on current EU planning, enforcement is expected to land in the 2027 to 2028 range, but brands should treat this as a moving target until the delegated act is formally adopted.
No. The physical label sewn into the garment, covering fiber content and care instructions, remains a separate legal requirement. The DPP adds a much deeper, updatable data layer accessed via QR code, but it does not remove the obligation to print the required minimums on the product itself.
Do not wait for the final field list before starting. Build the underlying data model and supplier collection process now, focused on the categories that are already clear from the JRC's technical studies: material composition, durability, chemical substances, certifications, and repair information. A well-structured data foundation absorbs the final delegated act as a configuration change rather than a redesign.
Whether you are prioritizing your first product category or scaling data collection across a full textile portfolio, Mimacom can assess where your supply chain data stands today and design the architecture to close the gap.