A Digital Product Passport (DPP) is a structured data record tied to a physical product. You scan a QR code, and you get the product's materials, origin, care rules, and end-of-life instructions. For fashion, this stops being a nice-to-have once the EU adopts its textile rules. The exact date is not fixed yet. The data work behind the passport is what takes time, and that work is what decides which software you actually need.
This guide is written for the people who tend to get told about the DPP last: suppliers, wholesalers, and retailers in the fashion trade. The software market for the Digital Product Passport in fashion is young and noisy. Picking a tool is less about features on a slide and more about whether your product data is clean enough to comply.
Key Takeaways
- The textile DPP is not law yet. The rules are expected around 2027, with mandatory compliance likely landing in 2028 or 2029.
- The data is the hard part. Choosing software is really a data-management decision, so judge tools on how well they capture and clean product data.
- Retailers carry legal duties too. They have to check that the stock they sell has a valid passport.
- A PIM system is the practical foundation. DPP platforms and data-governance tools sit on top of it, not instead of it.
- Fix your data gaps now. The 18-month transition window is not enough time to repair scattered data under deadline pressure.
What The Digital Product Passport Means For Fashion
Textiles were put near the front of the queue for a reason. Each person in the EU consumed on average 19 kg of clothing, footwear, and household textiles in 2022, up from 17 kg in 2019. About 12 kg per person gets thrown away each year, less than 1% of used clothes are recycled into new clothes, and between 4% and 9% of textile products put on the market are destroyed before anyone wears them, according to the European Parliament.
The passport is the EU's chosen fix. A garment that carries its own material and recycling data can be sorted, resold, or recycled. One that carries nothing usually ends up incinerated.
One obligation is already live and worth knowing about. Under the Ecodesign for Sustainable Products Regulation, large companies have been banned from destroying unsold apparel and footwear since 19 July 2026 (see the EUR-Lex summary). The passport itself comes later, but the direction of travel is set.
The Timeline You Actually Have To Plan Around
Plenty of articles claim textiles need a DPP in 2026. That is wrong, and building your plan around it wastes money.
The DPP sits inside the Ecodesign for Sustainable Products Regulation (Regulation (EU) 2024/1781), a framework law that entered into force in July 2024. A framework law sets objectives. The real rules for each product group arrive through a separate delegated act. Batteries go first, with a mandatory battery passport from February 2027. Textiles follow.
For apparel, the textile delegated act is expected to be adopted around late 2026 or 2027. Once adopted, requirements typically apply about 18 months later. So mandatory compliance for clothing is realistically a 2028 or 2029 event, likely hitting the Spring/Summer 2028 collections first. The EU launched its central DPP registry in July 2026, which is the plumbing that later passports will connect to.
The clearest signal so far came in May 2026. The Commission's Joint Research Centre published its study on DPP content for textile apparel, the first full specification of what a textile passport will carry. It is a proposal, not final law. But it is the document to build against, because the final act will not stray far from it.
What A Fashion DPP Will Hold
The JRC study lists 49 data points, grouped into four categories.
- Product identification:
GTIN, model and batch IDs, customs codes, and product category. - Producer identification:
manufacturer, importer, and facility IDs, with names and contacts. - Product information:
fibre composition, recycled content, substances of concern, carbon and environmental footprint, and care instructions. - Compliance documentation:
certifications and conformity declarations.
Two points matter for your systems. First, the proposed scope covers products that are at least 80% textile fibre by weight, so most garments, accessories, sportswear, and workwear are in. Fabrics and yarns as intermediate products are out, and footwear gets a separate study later. Second, the minimum granularity is the production batch, not the individual item. Item-level tracking stays voluntary. That single fact keeps the data burden manageable, because most fashion companies already manage data at model and batch level.
Why The Software Choice Is Really A Data Choice
The physical side of a DPP is close to solved. The EN 18220 standard says the product needs at least one data carrier that is free to use and readable with an ordinary smartphone. In practice, that is a QR code that opens a web page. Your label printer can handle it. Everything hard about the passport happens before the QR code exists. You need structured, typed, machine-readable data about fibre content, substances, origin, and footprint, at a level of detail most fashion businesses have never had to publish. That data usually lives in PDFs, supplier emails, and a spreadsheet someone updates by hand.
Our customers in apparel manufacturing turn to us with exactly this gap. The composition and substance data usually exists, but it sits scattered across supplier attachments in different formats, and no two products describe the same fibre the same way. Before any passport is possible, that data has to be cleaned, standardised, and given consistent fields. The passport output itself is quick to generate. Collecting and fixing the supplier data underneath it is the slow part, and it is where most of the effort goes. Software that ignores this order of operations solves the wrong problem.
What To Look For When Choosing DPP Software
The right tool depends on your data quality and where you sit in the chain. These are the criteria that separate a system you can grow into from one you will rip out in a year.
- A flexible data model.
Fashion data is messy: sizes, colours, seasons, variants, material breakdowns, and care symbols. The system has to model all of it without custom code for every new attribute. - Batch and model-level handling.
The passport minimum is batch level. Your tool needs to attach data at model and batch level cleanly, and support item level if a client demands it. - Supplier data collection.
Most passport data comes from suppliers, not from you. Look for import tooling, supplier portals, and validation on the way in, so bad data gets caught early. - Data quality rules.
Completeness checks, controlled value lists, and required-field logic stop a half-filled passport from ever going live. - Access tiers.
The ESPR gives different parties different views. Consumers see less; regulators and recyclers see more. The software must serve role-based visibility from one record. - GS1 Digital Link and carrier support.
The EU is aligning identifiers with GS1 Digital Link. Confirm the platform supports it before you commit, or you inherit an interoperability problem later. - EU hosting and an open API.
Passport data touches GDPR residency rules, so EU-compliant hosting matters. A documented API lets the data feed DPP platforms, e-commerce, and the EU registry without manual exports.
The three roles need different things from the same criteria. Suppliers hold the source data, so their priority is capturing composition and substance data accurately and passing it downstream. Wholesalers and distributors aggregate products from many brands, so they need to receive, verify, and syndicate passport data at volume. Retailers have the least data of their own and the sharpest legal exposure: they have to verify that the products they stock carry valid passports, so a non-compliant supplier can cost them shelf space before any regulator acts.
The Software Categories, And Where Each Fits
The market breaks into a few practical groups. Most companies end up combining two of them.
PIM systems are the foundation. A product information management system stores structured product data: materials, attributes, certifications, multilingual content, and supplier references. That is most of what a passport needs, which turns the DPP from a rebuild into a structured export. Trying to run passport compliance from spreadsheets tends to end with you building this layer anyway, later and under pressure. AtroPIM fits fashion use cases here because it pairs a flexible product-data repository with a publication-ready DPP output layer and a documented REST API that external passport platforms can read directly. It is open source and built by an EU vendor, which helps with the hosting-residency question.
DPP platforms such as Spherity and Minespider handle the registry side: unique identifier generation, data hosting, access-tier management, and connection to EU registry frameworks. They sit on top of your data layer. What they serve is only as good as what you feed them.
Data-governance and master-data platforms suit companies that treat the passport as part of a wider data problem across many product lines and source systems. AtroCore, Semarchy, and Stibo Systems fall here, giving you a governed single source of truth that passport output can draw from.
Sustainability and LCA tools like Ecoinvent and SimaPro calculate carbon and environmental footprint. They produce specific data points for the passport rather than managing the passport itself.
Building or extending your own makes sense when your catalog is already well structured, and you want full control of hosting and access. The same web systems that serve product pages can be extended to serve passport data to authorised parties. This works only when data quality is already high, which points straight back to having a solid PIM in place first.
A Practical Way To Start This Year
You do not need the final delegated act to begin, and waiting for it is the expensive choice. Start by mapping your data gaps: for a sample of products, write down what data you hold, what format it is in, and where it lives. The gaps are almost always bigger than expected. Then request the missing data from suppliers now, because that conversation is slow and outside your control. Standardise what you collect inside a PIM so every product describes fibre, origin, and care the same way. Pick your data carrier and confirm the platform supports GS1 Digital Link. Finally, name an owner to keep passports current, because a DPP is not a one-time filing and updates fall through the cracks without clear responsibility.
A fashion business with clean, structured product data can be passport-ready in weeks. One starting from scattered files should count on months. The difference is entirely in the data you sort out before the rules arrive.