Compliance Required by July 2027

Digital Product Passports Are Coming for Textiles Next

Batteries were first. The EU's delegated act for textiles and footwear was published in January 2026 — here's what it requires and what's still to be finalized.

✓ ESPR Priority Sector
✓ All Apparel Sold in the EU
✓ QR Code Data Carrier

Where Things Stand Today

The EU published its delegated act for textiles and footwear in January 2026, setting a compliance date of July 2027 — a similar structure to the Battery Regulation's February 18, 2027 deadline, just for a different product category. Full technical implementation guidance is still being finalized, so some specifics below are the expected direction rather than a locked checklist. See the category-by-category breakdown in our Digital Product Passport industries timeline and the fuller regulatory picture in our Digital Product Passport guide.

Where Things Actually Stand

The Digital Product Passport isn't a single law — it's a framework created by the Ecodesign for Sustainable Products Regulation (ESPR), rolled out one product category at a time through separate delegated acts, as laid out on the European Commission's official Digital Product Passport page. Batteries went first, with binding requirements now in force from February 18, 2027. Textiles and footwear are next, with their own delegated act published in January 2026 and compliance required by July 2027.

The requirement applies to clothing, footwear, and likely fashion accessories and home textiles sold in the EU market — regardless of where the brand is headquartered or how large it is. That scope is consistent with how ESPR has applied to every category so far.

What the Passport Will Cover

The published delegated act confirms the general data categories for this sector; the exact field-by-field technical specification is still being finalized. Expect a garment's digital product passport to include:

  • Fiber composition — material breakdown by percentage, including recycled content
  • Durability data — how the product is expected to hold up under normal use
  • Recyclability information and end-of-life handling instructions
  • Supply chain traceability — country of manufacture and origin points
  • Care instructions in a format that can be updated without reprinting the garment tag
  • Repair and resale information, supporting the EU's broader circular-economy goals

Fiber composition, durability, recyclability, and supply chain traceability are the categories confirmed in the delegated act itself; the remaining items reflect how the equivalent battery and metals passports were structured and are a reasonable but unconfirmed expectation for the exact field list.

Why the Garment Label Itself Has to Change

A woven or printed care label has a fixed amount of space and can't be edited once it's sewn in. A digital product passport needs a data carrier — almost certainly a QR code, based on how every other DPP category has been implemented so far — printed or woven into the garment, pointing to a page that can hold far more information than fabric ever could, and can be updated after the garment has already shipped.

Woven Care Label QR-Linked Digital Passport
Fixed at time of sewingContent editable after the garment ships
Limited to a few lines of icons and textFull fiber, supply chain, and repair data
No link to resale or repair servicesCan route to resale, repair, or recycling programs
Identical across every unit of a SKUSerialized per batch or per unit if needed

What to Prepare Now, Before July 2027

The compliance date is confirmed, but full technical implementation guidance is still rolling out — which means there's real groundwork to start now rather than waiting for every field to be finalized:

  • Centralize the fiber and supply chain data you already have — most brands hold this scattered across suppliers, not in one system.
  • Pilot a QR-linked care label on one product line now, so the workflow exists well before the July 2027 deadline.
  • Use a custom domain for any garment-level code you start rolling out now, so it doesn't need replacing once final technical specs land.
  • Bulk-generate per style or batch using a CSV-driven label workflow, since a full apparel line can mean thousands of SKU/size/color combinations.
  • Watch the same GS1 Digital Link standard that's already shaping battery and general product passports — textiles are expected to follow the same technical direction.

Frequently Asked Questions

Is the textile Digital Product Passport law finalized?

The delegated act itself was published in January 2026, with compliance required by July 2027 — the deadline is confirmed. The detailed technical implementation guidance (exact data fields and formats) is still being finalized ahead of that date.

Will every garment need its own QR code?

The exact serialization level (per unit vs. per batch or SKU) is part of the technical guidance still being finalized. The battery regulation requires unit-level codes; textiles may follow a similar model given the category's circular-economy focus, but this specific detail isn't confirmed yet.

Does this apply to brands outside the EU?

Yes, consistent with how ESPR has applied to other categories — it covers any apparel, footwear, or textile product sold in the EU market, regardless of where the brand is based.

Should I wait until every technical detail is final to start?

Not necessarily. With the July 2027 date confirmed, centralizing your fiber and supply chain data and piloting a QR-linked label on one product line now builds the workflow well ahead of the deadline, without needing to guess at the last remaining technical details.

Does QRTRAC provide the passport data hosting?

No. QRTRAC provides the dynamic QR code and link layer that can point to wherever your garment's passport data lives, and lets you update that destination as requirements are finalized. Structuring the passport data itself is a separate workstream for your compliance and product teams.

Pilot a QR-Linked Garment Label Now

Bulk-generate dynamic, per-SKU QR codes on your own domain — ready well ahead of the July 2027 compliance date.