8 Digital Product Passport Pilot Programmes Fashion Brands Can Learn From
· Last updated:
The Digital Product Passport is no longer a regulatory abstraction. Across the EU and beyond, brands, consortia, and research programmes have been running structured pilots—testing data architectures, carrier formats, stakeholder handoffs, and governance models under real supply-chain conditions. The lessons from those programmes are available now, well before mandatory DPP requirements take effect for textiles. If your sustainability, product, or IT team is scoping an implementation, the eight cases below compress years of field learning into actionable decisions.
Key takeaways
- Pilots consistently reveal that data collection at the raw-material tier is the hardest problem, not the QR code or the consumer interface.
- Interoperability between brand systems and supplier systems is the single most common cause of pilot delays.
- Governance—who owns the passport record and who can write to it—must be decided before any technical architecture is chosen.
- The CircularID Protocol and similar common-language frameworks are emerging specifically because brand-by-brand proprietary schemas fragment the resale and repair ecosystem.
- Brands that treat the DPP as a compliance checkbox rather than a product-data infrastructure investment tend to rebuild from scratch when scope expands.
Why study pilots before your own implementation?
Mandatory DPP requirements for textiles are expected under the EU Ecodesign for Sustainable Products Regulation (ESPR), with delegated acts for apparel and footwear in preparation. The Ellen MacArthur Foundation has documented the circular-economy case for product-level data transparency extensively, and the regulatory direction is settled. What is not settled—and what pilots reveal—is the implementation detail: which data fields cause supplier friction, which carrier technologies fail at scale, and which governance models survive a brand acquisition or a factory switch.
The eight programmes below are drawn from documented industry activity and published research. They are not exhaustive, and several remain ongoing. Each entry covers what the programme set out to test, what it found, and what is still unresolved.
1. The Aura Blockchain Consortium's luxury-goods traceability pilots
The Aura Blockchain Consortium—founded by several major luxury houses—piloted blockchain-anchored product passports for leather goods and ready-to-wear, linking NFC chips embedded in physical products to on-chain records covering material origin, manufacturing site, and ownership transfer. The consortium's architecture separates the public-facing consumer layer (brand story, care instructions, authentication) from the private supply-chain layer (supplier identities, audit results), with access governed by cryptographic keys assigned to each stakeholder tier.
What it signals: luxury groups are moving toward a model where the DPP is also an anti-counterfeiting and secondary-market authentication tool, not only a sustainability disclosure. The dual-layer architecture—public consumer record plus permissioned supply-chain record—is likely to become a template that mid-market brands adapt at lower infrastructure cost.
What is still unclear: the cost of NFC chip embedding at volume, and whether the consortium's permissioning model is compatible with the open-access requirements that EU regulators are signalling for the consumer-facing layer.
2. The Certilogo connected-product programme
Certilogo has operated connected-product programmes for apparel brands for over a decade, and its work has become one of the more cited references as the DPP debate has matured. As Business of Fashion reported, new regulatory requirements are moving DPP technology from a niche consideration to a core strategic focus—a shift that Certilogo's client base has been navigating in practice.
The programme links a per-garment QR code or NFC identifier to a cloud record that brands can populate with authentication signals, care and composition data, and end-of-life instructions. The consumer-facing interface is brand-controlled, but the underlying identifier is persistent across ownership changes.
What it signals: the per-garment unique identifier—not a per-SKU identifier—is the foundational requirement that separates a genuine DPP from a product information page. Brands that have already deployed per-garment serialisation for anti-counterfeiting are significantly closer to DPP readiness than those that have not.
What is still unclear: how brands will handle the data liability when a garment's passport record contains supplier information that the supplier considers commercially sensitive, and the garment subsequently enters the resale market.
3. The BSR CircularID Protocol initiative
BSR (Business for Social Responsibility) has documented the CircularID Protocol as a common-language framework that allows brands to communicate across the product lifecycle using a shared data schema. As BSR's emerging-issues brief describes, the protocol is designed to give brands a standardised vocabulary for product-passport data so that downstream actors—recyclers, resellers, repair services—can read passport records without bespoke integrations for each brand.
The initiative addresses a structural problem that every brand-by-brand pilot eventually hits: if each brand defines its own data fields and carrier format, the ecosystem of actors who need to read those records (take-back programmes, sorting facilities, recommerce platforms) faces an integration burden that makes circular business models economically unviable.
What it signals: the industry is beginning to treat DPP data schemas as pre-competitive infrastructure, similar to how EDI standards were treated in the 1990s. Brands that build proprietary schemas now may find themselves re-platforming when interoperability requirements are formalised in delegated acts.
What is still unclear: which body will govern CircularID or any successor standard long-term, and whether the EU's own ESPR technical specifications will align with or supersede industry-led schemas.
4. Patagonia's repair and materials transparency work
Patagonia has built one of the more documented material-transparency and repair-programme infrastructures in outdoor apparel, tracking fibre origin, recycled content percentages, and bluesign certification status at the fabric level. Its Worn Wear repair programme generates longitudinal data on garment longevity and failure modes that most brands do not collect at all.
From a DPP architecture perspective, Patagonia's approach illustrates what a brand-controlled, materials-first data model looks like in practice: data is collected at the supplier tier, validated against third-party certifications, and surfaced to consumers through product pages and hangtag QR codes. The repair programme adds a post-sale data layer that most DPP pilots have not yet addressed.
What it signals: brands with existing material-certification workflows have a meaningful head start on DPP data collection, because the hardest fields to populate—fibre origin, recycled content, chemical compliance—are already being gathered for other purposes. The DPP becomes an aggregation and disclosure layer rather than a new data-collection exercise.
What is still unclear: how Patagonia's model, which relies heavily on direct supplier relationships and a relatively contained product range, scales to brands with thousands of SKUs and multi-tier supply chains where tier-2 and tier-3 suppliers are not directly contracted.
5. Hugo Boss and digital product creation integration
Hugo Boss has been active in digital product creation, connecting 3D design workflows to downstream product data systems. The strategic direction—linking the design-phase digital twin to the physical product's data record—is directly relevant to DPP architecture, because the design file is the earliest point at which material specifications, construction details, and care requirements are known.
Integrating DPP data collection into the product creation workflow, rather than retrofitting it at the point of shipment, is one of the clearest lessons from pilots that have attempted both approaches. When material data is entered once at the design stage and flows through PLM into the passport record, error rates and supplier re-contact costs drop substantially.
What it signals: the DPP is most efficiently built as an output of the existing product creation process, not as a parallel compliance workflow. Brands with mature PLM and digital product creation infrastructure are better positioned to automate passport population than those relying on manual data collection at the factory gate.
What is still unclear: how brands handle the DPP record when design specifications change during development—a common occurrence—and whether version control for passport data will be addressed in the ESPR delegated acts.
6. The RETRACED supply-chain transparency pilots
RETraced has run supply-chain transparency pilots with European apparel brands, mapping multi-tier supplier networks and attaching facility-level data (certifications, audit status, location) to product records. The architecture uses a supplier-facing data-entry interface that allows factories to self-report and upload certification documents, reducing the brand's data-collection burden while maintaining a verifiable audit trail.
The supplier self-reporting model surfaces a governance tension that most DPP frameworks have not fully resolved: the entity generating the data (the supplier) is also the entity whose compliance status the data is meant to verify. Pilots using this model have found that data completeness improves significantly when supplier participation is tied to order placement rather than requested voluntarily after the fact.
What it signals: DPP data quality is a procurement and supplier-relationship problem as much as a technical one. Brands that embed data-submission requirements into supplier contracts and purchase-order workflows achieve higher completion rates than those that treat data collection as a post-production step.
What is still unclear: how liability for inaccurate supplier-submitted data is allocated between the brand (which publishes the passport) and the supplier (which provided the underlying data), particularly when the inaccuracy is discovered after a product has entered the resale market.
7. The EURATEX and European textile industry DPP readiness assessments
EURATEX, the European Apparel and Textile Confederation, has conducted readiness assessments across its member base to understand where SMEs in the textile supply chain stand relative to DPP requirements. The findings, consistent with similar assessments by national industry bodies, show that data availability is highly uneven: large brands have partial data for tier-1 suppliers; almost none have systematic data for tier-2 and beyond.
The assessments also document a capacity problem: many tier-1 and tier-2 suppliers in the EU and near-shore sourcing regions lack the IT infrastructure to generate, store, or transmit structured product data in any standardised format. This is not a willingness problem—suppliers understand the direction of regulation—but a resource and tooling problem.
What it signals: the DPP compliance burden will fall disproportionately on brands that source from SME suppliers, because those suppliers cannot absorb the data-infrastructure cost independently. Brands that invest in supplier-facing tooling—simple data-entry interfaces, pre-populated templates, API connections to existing ERP systems—will achieve higher data quality than those that issue data-submission requirements without supporting infrastructure.
What is still unclear: whether the EU will provide transition support or funding mechanisms for SME suppliers in the textile sector, and how enforcement will be calibrated for brands whose supply-chain data gaps reflect supplier capacity rather than brand non-compliance.
8. The GS1 Digital Link standard pilots in apparel
GS1's Digital Link standard—which encodes a product's GTIN and additional attributes into a single URL that resolves to different data endpoints depending on the requesting party—has been piloted by several apparel brands as a carrier-agnostic DPP infrastructure. The standard allows a single QR code to serve a consumer (returning care and composition information), a customs authority (returning origin and tariff data), and a recycler (returning material composition and disassembly instructions), with access controlled by the resolver.
The GS1 Digital Link approach is significant because it is carrier-agnostic and resolver-based: the physical identifier (QR code, NFC, RFID) does not change when the data behind it is updated. This matters for DPP compliance because regulatory data requirements will evolve over the product's lifetime, and a passport architecture that requires re-labelling to update data fields is operationally untenable at scale.
What it signals: the resolver model—where the identifier is stable and the data layer is updateable—is likely to become the default DPP infrastructure pattern for mid-to-large brands, because it decouples the physical product from the regulatory data layer. Brands evaluating DPP infrastructure should assess whether their chosen carrier technology supports resolver-based data updates without re-labelling.
What is still unclear: how GS1 Digital Link resolvers will be governed and who bears the cost of resolver infrastructure over a product's full lifecycle, including after a brand is acquired or ceases to operate.
What the pilots, taken together, tell you
Across these eight programmes, a consistent set of implementation decisions emerges that your team should resolve before selecting technology:
- Identifier granularity: per-garment serialisation is the direction of travel; per-SKU records will require migration.
- Data architecture: a resolver-based model that decouples the physical identifier from the data layer is more durable than a static QR code pointing to a fixed URL.
- Data collection entry point: integrating passport data collection into the design and procurement workflow, rather than the shipping workflow, produces higher data quality at lower cost.
- Supplier enablement: data-submission requirements embedded in contracts outperform voluntary post-production requests by a wide margin.
- Governance: decide who owns the passport record, who can write to it, and how disputes are resolved before any technical architecture is chosen.
- Interoperability: building to an emerging common schema (such as CircularID or GS1 Digital Link) reduces the risk of re-platforming when interoperability requirements are formalised.
No single pilot has solved all of these problems. The programmes that are furthest along are those that started with governance and data architecture, then selected technology—not the reverse.
FAQ
What data fields does a fashion Digital Product Passport need to include? Regulatory requirements are still being finalised in ESPR delegated acts, but pilots consistently include: fibre composition, country of origin for key manufacturing stages, chemical compliance certifications, care instructions, recycled content percentage, and end-of-life instructions. Supplier facility identifiers are also common in supply-chain-facing layers.
What is the difference between a per-SKU and a per-garment DPP? A per-SKU passport holds data for a product model; every unit of that model shares the same record. A per-garment passport assigns a unique identifier to each physical unit, enabling individual authentication, ownership transfer tracking, and repair history. EU regulatory signals favour per-garment serialisation for traceability purposes.
How do brands handle DPP data when a supplier changes mid-season? This is one of the unresolved governance questions across most pilots. The practical approach is to version the passport record at the batch or production-order level, so that units produced by different suppliers carry distinct data records even if they share an external SKU. PLM integration is the most reliable way to trigger a new passport version when a supplier changes.
Can a QR code on a garment serve as a compliant DPP carrier? A QR code can be a compliant carrier if it encodes a persistent, resolvable identifier—not a static URL that may break when a website is restructured. GS1 Digital Link pilots demonstrate that a QR code encoding a GTIN-based URL, resolved through a governed resolver, meets the persistence and updateability requirements that regulators are signalling.
What is the CircularID Protocol and do brands need to adopt it? CircularID is an industry-led common data schema designed to give brands, recyclers, resellers, and repair services a shared vocabulary for product-passport data. Adoption is currently voluntary. Its relevance is that brands building proprietary schemas now may face interoperability requirements later that necessitate migration; building to an open schema reduces that risk.
Further reading
- Reimagining Customer Connections Through Digital Product Passports — Business of Fashion
- Digital Passports for Clothing — BSR