Knowing what a Digital Product Passport is only gets you so far. The harder question is operational: how do you manage DPPs across your whole catalogue, keep records accurate for a decade, and choose a platform you can rely on? (New to DPPs? Read Digital Product Passport Marketing for Fashion Brands first.)
This guide covers SKU-level management, DPP hosting requirements, update workflows, technical standards, platform selection, and how to turn compliance data into a marketing advantage.
SKU-Level DPPs: When Variants Need Separate Records
A Digital Product Passport is issued at model level: one record per unique product model, identified by its GTIN (Global Trade Item Number). In practice, this means one DPP per variant wherever the regulated data differs.
Take a cotton T-shirt in three colourways: white, navy, and black. If all three use the same fabric composition, the same supply chain, and the same dyeing process, they share one DPP. Now suppose the navy version requires a different dye process that alters its environmental footprint — that colourway needs its own record. The same logic applies to sizing: if an extended size uses a different fabric supplier, it gets its own record. Wherever the regulated data differs between variants, create a separate DPP. When in doubt, err on the side of separate records.
Scale Reality: How Many DPP Records Does a Fashion Brand Need?
A fashion brand needs one DPP record per product model where the regulated data differs. At scale, that means hundreds to thousands of records for even mid-sized brands.
For a micro-brand with a focused catalogue of 50 core styles, the DPP count stays manageable. But the numbers climb quickly:
| Brand Profile | Active SKUs | Approximate DPP Records |
|---|---|---|
| Micro-brand, capsule collection | 30–80 | 30–200 |
| Small brand, seasonal collections | 200–500 | 200–1,000 |
| Mid-size brand, multiple categories | 1,000–5,000 | 1,000–5,000+ |
| Large brand, global range | 10,000+ | 10,000+ |
Even at the smaller end, spreadsheets will not hold up. You need a dedicated DPP platform or an integration with your PLM/PIM system (the product lifecycle and information management tools most brands already use to manage styles and materials).
How Long Must Digital Product Passport Data Be Stored?
Under ESPR Art. 9(2)(i), DPP data must remain accessible for the expected lifetime of the product. The exact period for textiles will be confirmed in the delegated act, but the practical implication is already clear: you need a long-term hosting arrangement, not just a short-term data contract.
Note: ESPR Art. 27(3) requires technical documentation to be kept for 10 years after the last product is placed on the market. That 10-year rule applies to technical documentation, not the DPP itself. Your hosting arrangement must address both separately.
What happens to your data if your brand restructures, gets acquired, or closes? ESPR requires that companies provide a backup copy of their DPP with a certified third-party service provider, ensuring accessibility even if the economic operator ceases to exist. Your hosting arrangement must include contractual provisions for data continuity beyond your company's lifespan.
Are Brands Legally Liable for DPP Accuracy?
Brands are legally accountable for the accuracy of their DPP data under ESPR (Regulation EU 2024/1781). Inaccurate material composition or false environmental footprint data also puts you in breach of Directive (EU) 2024/825 (Empowering Consumers for the Green Transition), which bans unsubstantiated green claims made to consumers and applies from 27 September 2026.
Your data processes need built-in verification: cross-checking supplier composition data, keeping certification references current, and calculating environmental footprint using the PEFCR (Product Environmental Footprint Category Rules) for Apparel and Footwear methodology. The goal is not perfection, just documented accuracy with a defensible data trail.
When Do DPP Records Need to Be Updated?
A Digital Product Passport is not a one-time filing. It is a living record that must be updated whenever relevant product data changes.
Update triggers include:
- Material composition changes: even a minor substitution at Tier 2 (a supplier's supplier) that alters fibre content
- A certification is added or lapses: for example, GRS (Global Recycled Standard) certification added, or OEKO-TEX certification expires
- Manufacturing location changes: production moves to a different facility or country
- Environmental footprint is recalculated: for example, after a manufacturer switches to renewable electricity, changing their Scope 2 carbon emissions figure
- Reformulation: dyeing process changes, new finishing treatment applied
At scale, managing these updates manually is not practical. You need workflows that flag data changes and push updates across all affected records.
What Technical Standards Do Digital Product Passports Use?
Digital Product Passports must connect to EU regulatory infrastructure via three key standards: GS1 Digital Link for QR codes, JSON-LD for machine-readable data, and the EU DPP Registry.
- GS1 Digital Link: The widely adopted standard for structuring the URL linked from the DPP QR code. ESPR requires data carriers that comply with ISO/IEC standards. GS1 Digital Link satisfies those requirements and is the industry consensus approach.
- JSON-LD: A structured data format that makes DPP records machine-readable, not just human-readable. It is the expected format being formalised through the EU harmonised standards process (CEN/CLC/JTC 24).
- EU DPP Registry: A central registry that ESPR Article 13(1) requires to be established by 18 July 2026. All DPP systems must connect to it.
Any platform you choose must support these natively.
What to Look for in a DPP Platform
When selecting a DPP platform, fashion brands should evaluate eight criteria: data ingestion, supplier-facing workflows, record-scale management, technical standards compliance, QR code generation, long-term hosting guarantees, extended field readiness, and consumer-facing output quality.
Platform selection is one of the most consequential infrastructure decisions you will make before 2028. (If you want a broader action plan, the EU textile regulation guide covers the full compliance roadmap.)
- 1.Data ingestion from PLM/ERP/PIM: Can it pull product data from your existing systems? Manual re-entry is unworkable at scale.
- 2.Supplier-facing data collection: Your suppliers hold most DPP data. The platform needs structured workflows they can actually use.
- 3.Record-scale management: Can it handle hundreds or thousands of records, and manage bulk updates when a supplier changes?
- 4.Technical standards compliance: Does it support GS1 Digital Link, JSON-LD, and the EU DPP registry interface? Ask for proof.
- 5.Care label QR code generation: Does it produce QR codes compatible with your label production process?
- 6.Long-term hosting with insolvency guarantees: You need contractual commitments for more than ten years of data accessibility, including escrow provisions.
- 7.Extended data field readiness: Can it accommodate social impact, animal welfare, and other fields as they become mandatory? Migrating platforms mid-compliance is expensive.
- 8.Consumer-facing output quality: Does it produce DPP views that are genuinely useful to consumers, not just regulatory tick-boxes?
How Fashion Brands Can Use DPP Data as a Marketing Advantage
The DPP starts as a compliance requirement. But the data it captures (material composition, supply chain traceability, environmental footprint, certifications) is exactly what values-driven consumers want when they shop.
Right now, a consumer cannot search across brands by "no polyester" or "made in Portugal" or "recycled content above 50%." That information exists inside brand systems but is invisible to shoppers.
When DPP data is structured and surfaced through a consumer-facing platform, it becomes a discovery tool. The QR code on the care label becomes a bridge. A consumer scans it and sees not a compliance document but a product story built on verified data. For smaller brands whose sustainability credentials are real but currently invisible, that is a genuine competitive advantage.
That's the idea behind Delvet and Storymark. Delvet manages DPPs at model level with long-term hosting guarantees. Storymark turns that same verified data into a consumer touchpoint — so every compliance obligation becomes a product story consumers can actually find.
Frequently Asked Questions
How long must Digital Product Passport data be maintained?
Under ESPR Art. 9(2)(i), DPP data must remain accessible for the expected lifetime of the product. The exact period for textiles will be confirmed in the delegated act. The separate 10-year retention rule in ESPR Art. 27(3) applies to technical documentation, not the DPP itself. Hosting must survive brand insolvency.
Can product variants share a single Digital Product Passport?
Yes. Variants that share identical regulated data (same fabric composition, same supply chain, same environmental footprint) can share one DPP record. A variant only needs its own record when the regulated data differs, for example a different dyeing process, a different fibre source, or a different manufacturing location.
When must fashion brands comply with DPP requirements?
The textile delegated act under ESPR is expected in late 2026 or early 2027. With a standard 18-month transition period, mandatory compliance for fashion brands is projected around mid-2028.
What happens to DPP data if a brand closes or goes insolvent?
Under ESPR, companies must provide a backup copy of their DPP data with a certified third-party service provider, so the data remains accessible even if the brand ceases to operate. Any DPP platform you use should offer contractual insolvency provisions and escrow arrangements.
How many DPP records does a fashion brand need?
One per product model where the regulated data differs. Variants that share identical regulated data can share one record. A brand with 500 active styles may need anywhere from 500 to several thousand records depending on variant complexity.
What technical standards must a Digital Product Passport support?
DPPs must support GS1 Digital Link (for QR code URL structure), JSON-LD (for machine-readable data, being formalised via CEN/CLC/JTC 24), and the EU DPP Registry interface (required to be operational by 18 July 2026 under ESPR Article 13(1)).
What should fashion brands look for in a DPP platform?
Data ingestion from existing PLM/ERP/PIM systems, supplier-facing data collection tools, record-scale management, GS1/JSON-LD compliance, QR code generation for care labels, long-term hosting with insolvency guarantees, and quality consumer-facing output.
Last updated: 28 March 2026. This article is based on analysis of ESPR Regulation (EU) 2024/1781, Directive (EU) 2024/825, and publicly available preparatory study documents. Specific DPP data fields for textiles will be confirmed in the delegated act expected in 2027. This does not constitute legal advice.
Related reading: