The EU Digital Product Passport (DPP) does not arrive into a data vacuum. Fashion enterprises already maintain product identifiers through GS1 schemes, product information through PIM platforms, and sustainability disclosures through a patchwork of voluntary and mandatory frameworks. The DPP adds a new mandatory data layer—but it does not simply replace what exists. It overlaps with some standards, conflicts with others, and leaves gaps that brands must fill through deliberate data architecture work.
Key takeaways
- GS1 identifiers are the most natural bridge into DPP: the GTIN is already the candidate anchor for the passport's unique product identifier, but the data models diverge significantly beyond that.
- PIM platforms store product information for commercial purposes; DPP stores it for regulatory traceability—the schemas share fields but assign different ownership, granularity, and update obligations to them.
- Sustainability reporting frameworks (GRI, ESRS, the Higg Index) operate at brand or facility level; DPP operates at SKU or batch level, creating an aggregation mismatch that cannot be resolved by mapping alone.
- The Ellen MacArthur Foundation has identified circular economy data—repair instructions, recyclability, material origin—as the category least covered by existing standards and most central to DPP requirements.
- Migration is not a one-time lift: DPP obligations are being phased in by product category, so data leads should expect an iterative programme rather than a single cutover.
What is the EU Digital Product Passport, and what data does it require?
The DPP is a machine-readable record, accessible via a physical data carrier (typically a QR code or RFID tag), that must accompany a product throughout its lifecycle. For textiles and apparel, the relevant framework sits under the Ecodesign for Sustainable Products Regulation (ESPR). The passport must carry information across several categories:
- Identity: a unique product identifier, manufacturer details, country of origin
- Material composition: fibre content, hazardous substances, recycled content percentages
- Circularity: repair and disassembly instructions, recyclability class, end-of-life guidance
- Supply chain: supplier identities at relevant tiers, certifications
- Carbon and environmental footprint: lifecycle assessment data at product level
The data must be stored in a decentralised registry interoperable with the EU's EUDAMED-style infrastructure, and it must be updatable—meaning the passport is a living record, not a static label.
Research examining adoption factors for sustainability-oriented technologies in the fashion sector, published in the Journal of Cleaner Production, confirms that economic incentives and regulatory pressure are the primary drivers pushing brands toward digital product data systems—underscoring that DPP compliance will not be treated as optional once enforcement timelines crystallise.
How does DPP compare to GS1 identifiers?
Where they align
GS1's Global Trade Item Number (GTIN) is the most widely used product identifier in fashion supply chains. The DPP specification anticipates using existing identifiers as the anchor for the passport's unique product identifier field, and the GTIN is the natural candidate. GS1's Digital Link standard—which encodes a GTIN into a URL-resolvable QR code—maps almost directly onto the DPP's requirement for a scannable data carrier that resolves to a machine-readable record.
GS1 also defines data attributes for country of origin, product description, and packaging dimensions that overlap with DPP identity fields. Brands already publishing GS1 Sync data to retail partners have a head start on populating these fields.
Where they conflict
GS1 identifiers were designed for supply chain logistics and point-of-sale: they identify what a product is and where it is. DPP requires data about how it was made, what it contains at a chemical level, and what happens to it at end of life. GS1's attribute vocabulary does not cover recyclability class, disassembly instructions, or lifecycle carbon footprint—these are structurally absent, not merely incomplete.
Granularity is also a tension point. A GTIN typically identifies a product-colour-size combination. DPP may require batch-level or even unit-level serialisation for certain product categories, particularly where supply chain traceability is mandated. GS1 supports serialisation through the SGTIN (Serialised GTIN), but most fashion brands do not currently issue or track SGTINs at scale.
Migration implication: Brands need to extend their GS1 data model, not replace it. The GTIN becomes the DPP anchor; the passport record hangs additional attribute classes off that anchor that GS1 does not currently carry.
How does DPP compare to PIM schemas?
Where they align
Product Information Management platforms—including Centric PLM, now part of Dassault Systèmes and expanding its product experience management capabilities through its Centric PXM module—store structured product data including material composition, care instructions, certifications, and supplier references. These overlap substantially with DPP identity and material fields.
Centric PLM, for instance, manages the kind of bill-of-materials data—fibre percentages, trim specifications, component sourcing—that feeds directly into DPP material composition requirements. Brands already running mature PLM implementations have a richer starting point than those relying on spreadsheets or disconnected ERP modules.
Where they conflict
PIM and PLM schemas are designed for commercial and operational use: they serve buyers, merchandisers, e-commerce teams, and production managers. Their data governance reflects that audience. DPP data governance reflects a regulatory audience with different requirements:
- Immutability vs. updateability: PIM records are routinely overwritten as products are revised. DPP records must be versioned and auditable; a change to a material composition after market entry must be traceable.
- Ownership and attestation: PIM data is typically owned by the brand's internal team. DPP data for supply chain tiers must be attested by the relevant supplier, creating a distributed data ownership model that most PIM architectures do not support natively.
- Scope of fields: PIM schemas optimise for fields that drive conversion (imagery, sizing, colour names). DPP requires fields that have no commercial value—disassembly torque specifications, chemical substance identifiers under REACH, recyclability class codes—which most PIM platforms do not carry at all.
- Lifecycle duration: A PIM record typically lives as long as the product is sold. A DPP record must persist for the product's full physical lifecycle, potentially decades after the commercial record is archived.
Migration implication: PIM is a data source for DPP, not a DPP system. Brands need an integration layer that pulls attested data from PLM, PIM, and supplier systems into a DPP-compliant registry, with versioning and access control that commercial PIM platforms were not built to provide.
How does DPP compare to sustainability reporting frameworks?
The aggregation mismatch
Existing sustainability reporting—whether under GRI Standards, the European Sustainability Reporting Standards (ESRS) under CSRD, or sector-specific tools like the Higg Index—operates at the brand, facility, or product-category level. A brand reports its total Scope 3 emissions, or a factory reports its water intensity per kilogram of fabric. These are aggregate figures.
DPP requires environmental data at the individual product level: the carbon footprint of this jacket, the recycled content percentage of this yarn, the chemical profile of this dye lot. The methodologies for product-level lifecycle assessment (LCA) are established, but most fashion brands have not applied them at SKU granularity across their full range. The gap between a brand-level carbon disclosure and a per-SKU carbon figure is not a rounding problem—it requires a different data collection infrastructure at the supplier level.
The Ellen MacArthur Foundation's work on circular economy frameworks highlights that data on repairability, material recovery, and end-of-life routing is the category most absent from current brand data systems—and it is precisely the category DPP prioritises for textiles.
Where they align
ESRS and DPP share a regulatory parent (the European Green Deal) and are designed to be mutually reinforcing. ESRS disclosures at brand level and DPP records at product level are intended to be consistent: a brand cannot report low-carbon products in its ESRS filing while DPP records show high per-SKU footprints. This alignment is a feature, but it also means that errors or gaps in DPP data will surface in ESRS audits, and vice versa.
The BSR analysis of digital passports for clothing notes the emergence of common language protocols—such as the CircularID Protocol—designed to let brands communicate consistently across the product lifecycle. These interoperability initiatives are attempting to bridge exactly the gap between existing reporting frameworks and DPP's product-level requirements.
Where they conflict
The Higg Index and similar tools use normalised scoring methodologies that allow comparison across brands. DPP does not use a normalised score—it requires raw data fields. A Higg MSI score for a material is not a valid DPP field; the underlying data that feeds that score might be, but it requires extraction and reformatting. Brands that have invested in Higg compliance cannot treat that as DPP compliance.
Comparison table: DPP vs. existing standards
| Standard | What it is | Best for | Limits in a DPP context |
|---|---|---|---|
| GS1 / GTIN | Global product identifier and logistics data standard | Anchoring DPP unique identifier; QR/RFID data carrier via Digital Link | Does not cover circularity, LCA, or chemical data; batch serialisation not widely deployed in fashion |
| PIM / PLM schemas | Commercial product data management (materials, specs, imagery, supplier refs) | Sourcing material composition, care, and certification data for DPP fields | No versioned audit trail; no distributed supplier attestation; missing regulatory-only fields; lifecycle too short |
| GRI / ESRS | Brand- and facility-level sustainability disclosure standards | Aligning DPP product data with corporate sustainability reporting | Aggregate level only; methodology does not produce per-SKU figures without additional LCA work |
| Higg Index | Sector-specific environmental scoring for materials and facilities | Internal benchmarking; supplier engagement | Normalised scores, not raw data fields; not directly mappable to DPP attribute vocabulary |
| CircularID / emerging protocols | Interoperability protocols for circular economy product data | Bridging brand systems to DPP registries across the value chain | Still maturing; adoption not yet mandatory or universal |
What migration work do brands actually face?
Phase 1: Data audit and gap analysis
Before any system work, data leads need a field-by-field mapping of what the applicable DPP delegated act requires against what currently exists in PLM, PIM, ERP, and supplier portals. The gaps will cluster in three areas: circularity attributes (repairability, recyclability), per-SKU environmental data (LCA figures), and supplier-attested chemical data (REACH substances).
Phase 2: Supplier data collection infrastructure
DPP's distributed attestation model means brands cannot generate the passport unilaterally. Tier-1 and, for some fields, Tier-2 suppliers must contribute data in a structured, machine-readable format. This requires either extending existing supplier portal capabilities or adopting an interoperability protocol that suppliers can connect to without bespoke integration per brand.
Phase 3: Registry and data carrier implementation
The passport record must be stored in a registry that is accessible via the data carrier on the physical product. This is a new infrastructure layer for most brands. The registry must support versioning, access control (some DPP data is public; some is restricted to regulators or value chain actors), and the EU's interoperability requirements.
Phase 4: Governance and update processes
Because DPP records must be updated when material facts change—a supplier substitution, a reformulation, a new certification—brands need operational processes to trigger and validate updates. This is a change management problem as much as a technical one.
Who is this for?
Enterprise data architects should focus on the registry and integration layer design: how PLM, PIM, and supplier systems feed a DPP-compliant record without duplicating master data.
Data leads in sustainability teams should focus on the LCA methodology gap: per-SKU environmental data requires a different collection approach than brand-level reporting, and building that capability takes time.
IT programme managers should note the phased regulatory timeline: DPP obligations roll out by product category, so a multi-year programme with category-specific workstreams is more realistic than a single enterprise-wide cutover.
Compliance and legal teams should map DPP obligations against CSRD/ESRS reporting timelines to ensure consistency between product-level and brand-level disclosures before either is audited.
FAQ
Can we use our existing GTIN as the DPP unique product identifier? Yes, in most cases. The GTIN is the expected anchor, and GS1 Digital Link provides the QR-resolvable carrier mechanism the DPP requires. However, if your product category requires batch- or unit-level serialisation, you will need to issue and track serialised GTINs, which most fashion brands do not currently do at scale.
Does DPP replace our PIM or PLM system? No. PIM and PLM remain the systems of record for commercial and operational product data. DPP is a regulatory output layer that draws on those systems. You need an integration architecture that pulls attested data from PLM, PIM, and suppliers into a DPP registry—not a replacement for existing platforms.
Is our Higg Index data usable for DPP compliance? Not directly. The Higg Index produces normalised scores; DPP requires raw attribute data fields. The underlying data that feeds a Higg assessment may be useful source material, but it needs to be extracted and reformatted to map onto DPP's attribute vocabulary.
How does DPP interact with CSRD sustainability reporting? The two frameworks are designed to be consistent: product-level DPP data and brand-level ESRS disclosures should not contradict each other. In practice, this means your DPP programme and your CSRD programme need shared data governance, not parallel silos.
When do textile DPP obligations actually apply? Delegated acts specifying the exact data requirements and timelines for textiles are still being finalised under the ESPR. Brands should monitor the European Commission's ESPR work programme for the textile product group and plan for an iterative compliance programme rather than a fixed single deadline.
Further reading
- Digital Passports for Clothing — BSR
- Digital product passports for cleaner production: Economic evidence — Journal of Cleaner Production