Journal
Regulation12 May 2026 4 min read

ESPR and textiles: what changes by 2028

The Digital Product Passport deadline for clothing: what you need ready and when — without the scare tactics.

The EU ESPR regulation (Ecodesign for Sustainable Products Regulation) introduces the Digital Product Passport (DPP): a set of structured data — composition, origin, care, recyclability, certifications — reachable from a QR on the garment. For textiles it isn't a distant hypothesis: it's a deadline with hard dates, and the time to get ready is measured in months of work, not a final click.

What ESPR is (and why textiles)

ESPR is the framework regulation by which the EU asks products to be designed to last, be repaired and recycled — and to declare it with verifiable data. The DPP is the vehicle for that declaration. Textiles are among the first priority categories: one of the highest-impact sectors with the most opaque supply chain, hence among the first the obligation will apply to.

The timeline that matters

The right reading isn't "there's plenty of time", but "the foundations are laid now": the registry and EmpCo arrive two years before the full obligation.

What a passport must contain

A passport isn't a document to attach: it's a data-centric artifact. At a minimum it requires:

  1. An identifier for each garment — GS1 Digital Link or an internal UID.
  2. Machine-readable structured data (JSON-LD), not free text.
  3. A public page the QR resolves to, hosted and persistent.
  4. Source traceability for every value: on an artifact with legal weight, invented data is a risk, not a detail.

The real problem for small and mid-size brands

Most IT/EU brands don't have a willingness problem — they have a data-shape problem. The information exists, but scattered: a collection spreadsheet, spec sheets in PDF, certificates in a drawer. What's missing is the structured data and the technical standard know-how. Enterprise providers exist, but they're slow, sales-led and expensive: built for companies that already have a data team, not a brand with a few hundred SKUs.

DPP-ready, not "compliant": the difference

Promising "ESPR compliance" today is misleading: the mandatory fields aren't fixed yet. The honest word is "DPP-ready" — already having structured data, identifiers and QR codes aligned to GS1 and the ESPR draft, in a form that updates when the act is final. That's a promise you can keep; "compliant" isn't.

How to arrive ready without rework

Getting ready costs a fraction of the last-minute scramble. Three moves, in order:

  • Structure now the data you already have — start from the file you've got, see from CSV to passport.
  • Generate identifiers, QR codes and JSON-LD aligned to GS1 and the ESPR draft.
  • Version the schema: when the delegated act is final, you regenerate instead of redoing.

Zero rework isn't a slogan — it's an architecture choice. Whoever structures the data now will only have to press a button in 2028.

Frequently asked questions

Generate your collection's passports

From product sheet to compliant, hosted, print-ready QR codes.

Get started