A lightweight DPP layer, built before the deadline is even set

No textiles or footwear delegated act exists yet under ESPR — but the unsold-goods destruction ban already binds large apparel and footwear companies today. Structure your Shopify or Magento product data now, on GS1 Digital Link identifiers, so the eventual passport requirement is an extension, not a scramble.

See what's actually binding Scope your connector

"ESPR applies" and "you need a passport" are different claims

ESPR the framework regulation is in force. A Digital Product Passport requirement for any specific product category is not — it only activates once that category gets its own delegated act, and none of the categories most Shopify and Magento merchants sell have one yet.

Instrument	Status on review date	What's actually required
ESPR framework	In force since 18 July 2024	Establishes the DPP mechanism and grants the Commission power to adopt category-specific delegated acts
Unsold-goods destruction ban (apparel/footwear)	Binding for large enterprises since 19 July 2026; disclosure duty since 2025	No destroying unsold stock without a documented exception; public disclosure of discarded quantities and reasons
Iron & steel delegated act	Not adopted — expected Q4 2026, compliance around 2028	First product-specific ecodesign/DPP requirements under the 2025–2030 working plan
Textiles / footwear delegated act	Not adopted — expected around 2027, compliance around 2028	The actual passport requirement most apparel and footwear merchants are asking about

Track the Commission's own implementation page rather than a fixed date from any single article — delegated-act timelines have already shifted once across this working plan. Implementing the ESPR.

What the framework already tells you to build for

ESPR doesn't leave the passport's shape entirely open — it sets the general architecture that every category-specific delegated act will build on top of.

Unique product identifier

Every passport-bearing product needs an identifier that resolves to its specific passport record, not a shared category-level page.

A physical data carrier

Typically a QR code (or equivalent) on the product or its packaging, linking to the digital passport.

Layered information access

Some passport data is public-facing; other data is restricted to authorities, recyclers or supply-chain actors — not one flat public page.

Economic-operator responsibility

Manufacturers, importers and distributors each carry defined responsibilities for passport availability along the value chain.

Category-specific data fields

The actual content — durability, repairability, recycled content, carbon footprint, and more — is set per product category by its own delegated act.

Interoperability intent

The framework anticipates a shared technical approach (like GS1 Digital Link) rather than every brand inventing its own format.

Build the identifier, data-carrier and access-layer architecture now — that part won't change per category. Leave the category-specific field list flexible until the relevant delegated act actually publishes it. Regulation (EU) 2024/1781.

The rule that's already live has nothing to do with QR codes

Merchants searching for "ESPR compliance" often find themselves reading about passports when the obligation that already applies to them is about what they do with unsold stock.

Destruction ban

Large enterprises may not destroy unsold apparel, clothing accessories or footwear as of 19 July 2026, absent a documented exception.

Disclosure duty

Large enterprises discarding unsold covered products — directly or through a third party — must publicly disclose quantity, weight, reasons and treatment.

Medium-enterprise runway

Medium-sized enterprises have until 19 July 2030 before the ban applies to them — a real grace period, not an exemption.

Documented exceptions

Exceptions (health, safety, donation-related, and similar) exist but must be properly disclosed and supported with records retained for a reported five years.

If you sell apparel or footwear at large-enterprise scale in the EU, audit your returns/overstock disposal process against this rule before spending further effort on passport architecture. Regulation (EU) 2024/1781.

A lightweight connector, not an enterprise PLM rollout

Most Shopify and Magento merchants don't need — and can't justify the cost of — the kind of full product lifecycle management system a large manufacturer might build. A lean, standards-aligned data layer covers the same ground at SME scale.

Build on existing catalog data

Map SKUs and variants to GS1-compatible identifiers rather than inventing a proprietary scheme
Extend product metafields (Shopify) or attribute sets (Magento) with passport-relevant fields as they become known
Generate GS1 Digital Link-formatted QR codes per product/variant, resolving to a hosted passport page

Design for category extension

Keep the data model open to additional category-specific fields rather than a fixed schema
Separate public-facing passport content from any future authority/professional-only layer
Version passport content per product so historical claims stay auditable as data changes

The CIRPASS-2 project's published architecture and pilot results for textiles and electronics are a useful reference point for this design work, even though its outputs aren't themselves binding law. CIRPASS-2 and GS1 Digital Product Passport standards.

Selling anything with a battery? That's a separate, nearer deadline

The EU Battery Regulation is further along than ESPR's general passport track and already has a real date attached — don't let general DPP research distract from it if it applies to you.

Battery passport: February 2027

Regulation (EU) 2023/1542 requires a battery-specific digital passport for industrial and electric-vehicle batteries starting February 2027 — a firmer, nearer deadline than anything on the general ESPR track covered on this page. If your products contain an in-scope battery, treat that as its own compliance project. Regulation (EU) 2023/1542.

See our dedicated page for that requirement: EU Battery Passport API Connector.

Controls that hold up regardless of when the delegated act lands

Build governance now around the parts of this that are already real — data accuracy and unsold-goods disclosure — so the eventual passport requirement extends a working system instead of exposing an ungoverned one.

Claim accuracy control

Any sustainability or material claim already published needs a documented basis — this matters independent of DPP and overlaps with EU green-claims rules.

Unsold-goods logging

If you're a large apparel/footwear enterprise, log every discard event with quantity, weight, reason and treatment as it happens, not retrospectively.

Exception documentation

Retain evidence for any destruction-ban exception claimed, for the reported five-year retention period.

Identifier stability control

Once a product identifier is issued and a QR code printed, changing the underlying scheme breaks every physical unit already shipped — version carefully.

Data-field readiness review

Revisit your data model against each newly published delegated act as it lands, rather than waiting for a compliance deadline to force the review.

Access-layer separation

Keep public passport content and any future restricted-access content in genuinely separate systems, not just a UI toggle.

Start with identifiers and disclosure, not the full passport

Sequence the work around what's real today, with the passport itself built as an extensible foundation rather than a guess at a still-unpublished spec.

Confirm your unsold-goods exposure
Determine whether the destruction ban and disclosure duty already apply to your enterprise size and product categories.
Assign GS1-compatible identifiers
Map your existing SKU/variant catalog to GS1-compatible identifiers as the foundation for future passport URLs.
Build the QR/resolver layer
Implement GS1 Digital Link-formatted QR codes that resolve to a hosted passport page per product.
Structure an extensible data model
Design product metafields/attributes so category-specific fields can be added later without restructuring the catalog.
Wire up unsold-goods disclosure tracking
If applicable, implement discard-event logging and public disclosure reporting now, ahead of any audit.
Track delegated-act publication
Set a recurring check against the Commission's implementation page so you extend the system the moment your category's act lands.

Acceptance criteria for the connector

Standards-aligned

Identifiers and QR codes follow GS1 Digital Link rather than a proprietary scheme that won't interoperate.

Extensible

New category-specific fields can be added to the data model without restructuring existing product records.

Access-layered

Public and (eventually) restricted-access passport content live in separable layers from day one.

Disclosure-ready

Unsold-goods discard events are logged and reportable, if the destruction ban and disclosure duty apply to you.

Not over-built

No production effort is sunk into category-specific fields that no adopted delegated act has actually defined.

Trackable

The team has a standing process for checking delegated-act publication, not a one-time reading of current guidance.

DPP integration FAQ

Is the Digital Product Passport actually mandatory for our products yet?

For textiles, footwear and most consumer electronics — no, not yet. As of this page's 2 September 2026 review, no product-specific ESPR delegated act had been adopted for any of those categories. Iron and steel is the first product group in line, with a delegated act expected in Q4 2026 and, per the standard 18-month minimum transition, real compliance not before roughly 2028. Textiles are expected to follow with a delegated act around 2027 and mandatory compliance around 2028.

So is there anything under ESPR we already have to comply with, right now?

Yes, and it's easy to miss because it isn't the passport itself. Large enterprises have been barred from destroying unsold apparel, clothing accessories and footwear since 19 July 2026, and have had to publicly disclose data on discarded unsold products — quantities, weight, reasons, treatment — since 2025. Medium-sized enterprises get until 19 July 2030. If you sell apparel or footwear at scale in the EU, this disclosure and destruction-ban duty is the actual live obligation, not the passport.

Should a small Shopify or Magento merchant build a DPP system now?

Build the foundation, not a finished compliance system. Nobody has a legal deadline for a textiles or footwear passport yet, so a large, rigid ERP-grade PLM rollout is premature. What's worth doing now is structuring your product data — unique identifiers, durability and material data, a QR-code-ready architecture — so that when your product category's delegated act lands, you're extending an existing system instead of building one from zero under deadline pressure.

What should the QR code and passport data actually be built on?

GS1 Digital Link is the standard converging around this use case — it embeds product identifiers (like a GTIN) in a resolvable web address, built on ISO/IEC 15459 for identification and ISO/IEC 18004 for the QR code itself. The EU-funded CIRPASS-2 project is piloting real DPP implementations, including for textiles and electronics, and is a useful reference for what a compliant data structure will likely need to support.

Is the Digital Product Passport the same thing as the Battery Passport?

No — related concept, separate and more advanced regulation. The EU Battery Regulation (2023/1542) requires a battery-specific digital passport for industrial and electric-vehicle batteries starting February 2027, well ahead of any ESPR product-specific delegated act. If you sell products with a battery in scope, that's a distinct, nearer-term compliance track from the general ESPR passport this page covers.

What exactly will a DPP have to contain once it applies to us?

The ESPR framework sets the shape — a unique product identifier, a data carrier (typically a QR code), and structured information accessible to different audiences (some public, some restricted to authorities or supply-chain actors) — but the specific data fields (durability, repairability, recycled content, carbon footprint, and more) are set per product category by that category's own delegated act, which for textiles and footwear doesn't exist yet. Build for the general shape; don't guess the category-specific field list before it's published.

Are there exemptions from the unsold-goods destruction ban?

Yes — the ban includes documented exceptions (for example, health, safety, or donation-related reasons), but claiming one isn't automatic. A company relying on an exception has to properly disclose it and retain supporting documentation, reportedly for five years. Treat 'exempt' as something you have to demonstrate, not assume.

Primary sources and status

Reviewed 2 September 2026. ESPR (Regulation (EU) 2024/1781) is in force, including the unsold-goods destruction ban and disclosure duty for large enterprises. No product-specific ESPR delegated act had been adopted for any category on the review date; iron and steel and textiles were the nearest in the pipeline. The EU Battery Regulation is a separate, more advanced instrument with its own February 2027 date. GS1 and CIRPASS-2 materials are technical/industry references, not binding law. Yarify's architecture recommendations are engineering guidance, not legal advice — confirm your obligations with qualified counsel.