Real Product Passport Examples: Fashion and Consumer Goods

!Decorative digital product passport title card illustration

Usable Digital Product Passport (DPP) examples already exist across batteries, textiles, apparel, and consumer goods. The most instructive ones come from EU-adjacent pilots and voluntary brand programs that are now informing mandatory compliance under the Ecodesign for Sustainable Products Regulation (ESPR). Here is a fast scan of what is live or in active pilot today:

• Battery passports: Audi and automotive-sector pilots using instance-level JSON credentials with recycled content, cell chemistry, and dismantling instructions
• Textile batch passports: Garment-level QR codes linking to fiber composition, origin, and care data (PANGAIA, H&M Group experiments)
• RFID-enabled transparency: Decathlon's in-store and logistics RFID tagging feeding product-level data to consumer-facing pages
• Supply-chain traceability: Everledger's provenance ledger and Nespresso's coffee-origin transparency program
• On-demand identity: Unspun's per-garment digital ID tied to made-to-measure denim production
• Tag and label platforms: Avery Dennison's Janela platform connecting physical hang tags to hosted product data pages

The single most transferable lesson from these pilots: start with open standards (GS1 Digital Link for identifiers, W3C JSON-LD for data payloads), plan your model/batch/item granularity before you touch a supplier spreadsheet and pilot supplier data collection on a small SKU set first.

Real-world DPP examples from batteries to apparel show that open standards, correct granularity, and early supplier onboarding are the three factors that determine whether a passport program succeeds or stalls.

• Why DPPs are now a regulatory reality for EU brands
• Real product passport examples: case studies from batteries to apparel
• What data fields and technical approaches DPPs actually use
• How to prepare your brand for DPP requirements: a practical checklist
• How to avoid vendor lock-in and choose standards that last
• What DPP readiness actually looks like for fashion brands
• DPP Grid helps fashion and consumer-goods brands publish evidence-backed passports
• Sources
• FAQ

The DPP is not a future concept. It is a digital container being introduced progressively across specific product groups under ESPR, with batteries already in scope and a staged timetable for the rest.

The ESPR legal text requires persistent unique product identifiers, open and interoperable data formats, and regulated access rights tied to delegated acts. Brands must make a DPP available wherever a delegated act requires it, including to marketplaces and customs authorities. The EU DPP Registry assigns persistent registration identifiers, runs semantic conformity checks on submission, and issues proof of registration. Registration granularity follows the delegated act for each product group: model, batch, or item level.

Phased product-group timeline:

• Batteries (2026 onward): First mandatory group under the Battery Regulation; instance-level passports required for EV and industrial batteries
• Textiles and apparel: Preparatory studies completed; delegated act in progress; fiber composition, recycled content, and durability metrics are confirmed data points
• Iron and steel, aluminum: Delegated acts in preparation; material composition and recycled content are the core fields
• Furniture and mattresses: In scope under ESPR; durability, repairability, and hazardous-substance data expected
• ICT and electronics: Delegated acts in preparation; repair scores, spare-part availability, and software update periods are likely requirements
• Construction products: Covered under separate regulation but DPP-aligned; CIRPASS-2 pilot ran interoperability tests across construction value chains

The DPP Registry implementation regulation specifies that economic operators must register at the granularity the delegated act prescribes. Omitting linked batch or model identifiers when registering at item level causes fragmented data and failed market-surveillance checks. That is a compliance gap, not a technicality.

Statistic callout: The EU DPP Registry performs semantic conformity checks at upload time and issues a unique persistent registration identifier. Brands that submit incomplete or non-conforming payloads will not receive proof of registration, which is required for placing products on the EU market under applicable delegated acts.

For a practical overview of ESPR requirements and what they mean for your product range, the ESPR Digital Product Passport readiness guide covers the key obligations in plain language.

The following case cards draw on publicly documented pilots and voluntary programs. Each shows what data was captured, how the product was linked to its passport, where data lives, and what the primary lesson was.

Sector: Automotive batteries Data fields: Cell chemistry, recycled content percentage, manufacturing site, carbon footprint per kWh, dismantling instructions, state of health Data carrier: QR code + NFC tag on battery housing; GS1 Digital Link URI resolving to instance-level record Storage/verification: Brand-managed database with verifiable credential layer; signed JSON-LD payload Maturity: Pilot; mandatory compliance under Battery Regulation from 2026 Primary use case: Regulatory compliance, end-of-life recycling, second-life assessment

Lesson: Instance-level granularity is non-negotiable for EV batteries. Audi's pilot showed that linking each physical battery to a unique identifier from manufacturing, rather than retrofitting identifiers later, dramatically reduces data-reconciliation effort at end of life.

Sector: Apparel and textiles Data fields: Fiber composition and percentages, dyeing process, country of origin, care instructions, take-back program link Data carrier: QR code on garment label; resolves to hosted product page Storage/verification: Brand-managed database; no public verifiable credential layer reported Maturity: Voluntary program; DPP-aligned but pre-regulatory Primary use case: Consumer transparency, brand storytelling, circular take-back

Lesson: PANGAIA's ReWear initiative demonstrated that consumers do scan garment QR codes when the landing page offers genuine value (repair guides, take-back options) rather than just a product description. The UX design of the passport page matters as much as the data inside it.

Sector: Fast fashion and apparel Data fields: Material composition, supplier country, chemical compliance status, recycled content, care and end-of-life guidance Data carrier: QR code on label; RFID in some store pilots Storage/verification: Internal product information management system; exploring third-party registry integration Maturity: Pilot and voluntary; preparing for ESPR textile delegated act Primary use case: Regulatory readiness, supplier data consolidation, consumer transparency

Lesson: At H&M Group's scale, the bottleneck is not technology but supplier data quality. Getting thousands of suppliers to provide verified fiber composition and chemical compliance data consistently is the hardest part of any large-brand DPP program.

Sector: Sporting goods and apparel Data fields: Product identity, materials, country of manufacture, care instructions, repair service availability Data carrier: RFID tag (UHF) on product; QR code for consumer access; GS1 GTIN as base identifier Storage/verification: Decathlon's centralized product database; RFID enables item-level tracking through logistics Maturity: Deployed at scale in logistics; consumer-facing DPP features in pilot Primary use case: Inventory accuracy, repair service routing, consumer transparency

!RFID tag on garment inventory label

Lesson: Decathlon's RFID rollout shows that the same physical data carrier can serve both internal logistics (item tracking, inventory) and external DPP obligations (consumer access, repair routing) if the identifier architecture is designed for dual use from the start.

Sector: Diamonds, batteries, luxury goods Data fields: Provenance chain, certification status, ownership history, material origin, recycled content (batteries) Data carrier: Unique digital identifier linked to physical product; QR or NFC depending on product type Storage/verification: Distributed ledger with verifiable credentials; third-party attestation Maturity: Deployed for diamonds; battery and materials pilots active Primary use case: Provenance verification, anti-counterfeiting, circular economy traceability

Lesson: Everledger's ledger approach works well for high-value, low-volume products where per-item verification cost is justified. For fashion at scale, the same verifiable-credential pattern can be applied at batch level rather than item level, reducing cost while maintaining attestation integrity.

Sector: Consumer goods (food/beverage) Data fields: Coffee origin (farm or cooperative), AAA Sustainable Quality Program certification, farmer support data, carbon footprint indicators Data carrier: QR code on packaging; resolves to web-based transparency page Storage/verification: Brand-managed database; third-party audit certification Maturity: Deployed; voluntary program aligned with EU supply-chain due-diligence expectations Primary use case: Consumer transparency, supply-chain due diligence, brand trust

Lesson: Nespresso's program shows that supply-chain transparency pages built before DPP mandates become a compliance head start. The data architecture they built for voluntary disclosure maps closely to what ESPR delegated acts will require for provenance and certification fields.

Sector: Denim and apparel Data fields: Body scan data (anonymized), fabric composition, production batch, manufacturing location, unique garment ID Data carrier: QR code on label; unique identifier per garment Storage/verification: Brand-managed database; per-item record from point of production Maturity: Deployed for made-to-measure production; DPP-aligned Primary use case: Product authenticity, ownership transfer, resale verification

Lesson: Unspun's model proves that item-level passports are operationally feasible when the production process is digital from the start. Brands that manufacture on demand have a structural advantage: the digital record exists before the physical product does.

Sector: Cross-sector (apparel, consumer goods, food) Data fields: Configurable per brand; typically product identity, materials, care, sustainability claims, certifications Data carrier: Printed QR codes, NFC tags, RFID labels; GS1 Digital Link compatible Storage/verification: Hosted cloud platform; brand-controlled data; API integration with brand systems Maturity: Commercially deployed; used by multiple apparel and consumer-goods brands Primary use case: DPP publishing, consumer engagement, brand transparency

Lesson: Avery Dennison's platform illustrates that the physical label and the digital passport can be designed together. Brands that treat the data carrier as an afterthought end up retrofitting QR codes onto labels not designed for them, which creates scanning reliability problems in retail environments.

Summary of case study dimensions:

Most DPPs combine five categories of information: product identity (model, batch, or item identifiers), material composition, provenance, operational guidance (care, repair, disassembly), and end-of-life data (recycling routes, hazardous substances). The published JSON samples for battery and textile passports confirm this structure: typical fields include id, type, manufacturer, composition, recycledContent, dismantlingInstructions, validFrom, and version.

Common data fields across DPP implementations:

• Identity: Unique product identifier (GTIN, UUID, or custom), model number, batch number, serial number where applicable
• Materials: Fiber or material composition with percentages, recycled content share, substances of concern (SVHC list)
• Provenance: Country of origin, manufacturing site name and address, supplier identifiers
• Compliance documents: Test reports, certifications (OEKO-TEX, GOTS, ISO), conformity declarations
• Care and repair: Washing and care instructions, repair service locations, spare-part availability and part numbers
• Durability: Durability class or score, microfibre release class (textiles), expected service life
• End of life: Recycling instructions, disassembly sequence, material recovery guidance, take-back program link
• Passport metadata: Version number, valid-from date, issuing economic operator, registry registration identifier

Technical approaches in use:

GS1 Digital Link provides the URI structure that resolves a product identifier (typically a GTIN) to a web resource. It is the most widely adopted approach for consumer-facing QR codes because it works with existing barcode infrastructure and is explicitly recommended by the European Commission's DPP FAQ guidance for interoperability.

W3C JSON-LD is the machine-readable payload format most aligned with ESPR's open-standards requirement. It allows semantic validation, meaning a registry or verifier can check that a field labeled recycledContent actually contains a percentage value, not a free-text string.

RFID and NFC serve logistics and item-level tracking. RFID (UHF) is suited to warehouse and supply-chain scanning without line of sight; NFC is better for consumer tap-to-read interactions on individual items.

Verifiable credentials (following the UNECE UNTP specification) add a cryptographic attestation layer. A signed credential proves that a specific economic operator issued a specific claim at a specific time, which is useful for third-party audit evidence and customs verification.

A 2026 Springer peer-reviewed paper proposing a minimal DPP data model found that a well-structured core schema can meet many ESPR requirements but needs targeted extensions for substances of concern and some conformity fields. That is a useful calibration: do not over-engineer the initial schema, but do plan extension points.

Data fields mapped to standards and typical obligation status:

Start with data discovery and supplier onboarding. Everything else depends on knowing what product data you actually have versus what you need. Here is a realistic sequence:

!Checklist infographic of DPP readiness steps

1. Data discovery (weeks 1–4) — Owner: product / compliance team Audit your existing product records. Identify which SKUs are in scope for the first delegated act that applies to your product group. Map what data you have (material composition, supplier names, certifications) against what the delegated act will require.

2. Supplier onboarding (weeks 3–8) — Owner: supply chain / procurement Send structured data-request templates to suppliers. Ask for fiber composition with percentages, manufacturing site details, substance compliance declarations, and any existing certifications. Build a supplier evidence library, not just a spreadsheet. For supplier product-data collection, structured workflows that track response status and flag missing fields reduce follow-up time significantly.

3. Data model and identifier design (weeks 4–6) — Owner: IT / product Decide on model/batch/item granularity for each product group. Choose GS1 Digital Link as your URI structure and W3C JSON-LD as your payload format. Define your identifier namespace now; retrofitting identifiers after production is expensive.

4. Evidence collection and document management (weeks 6–10) — Owner: compliance Collect test reports, certifications, and conformity declarations. Store them with version history and timestamps. The DPP Registry will require proof of registration; market surveillance authorities may request supporting evidence at any time.

5. Passport page design and QR publishing (weeks 8–12) — Owner: e-commerce / product Design the consumer-facing passport page. It needs to be scannable without an app, load fast on mobile, and present the data in plain language. Generate QR codes that resolve via GS1 Digital Link to your passport page. For Shopify brands, the Shopify DPP integration guide covers the publication workflow in detail.

6. Registry submission and verification (weeks 10–14) — Owner: compliance / IT Submit passport records to the EU DPP Registry at the correct granularity. Confirm that semantic conformity checks pass and that you receive persistent registration identifiers. Store proof of registration.

7. Operations and versioning (ongoing) — Owner: product / compliance Establish a process for updating passports when product formulations, suppliers, or certifications change. Version every update with a timestamp. Assign a named economic operator responsible for each passport record.

Pro Tip: When onboarding suppliers, ask for machine-readable data (CSV or structured form) rather than PDFs. A PDF certificate proves a fact but cannot be ingested into a data model without manual re-entry. Structured supplier forms cut data-entry time by a large margin and reduce transcription errors.

A realistic pilot scope for a fashion brand is 20–50 SKUs over a 12–16 week period, with two to three internal team members (product, compliance, and one technical resource) and a platform to manage data collection and publishing.

Prioritize open, widely adopted standards from the start. Proprietary binary formats for core product data create migration costs that compound over time as delegated acts evolve and the registry's semantic validation rules tighten.

Standards priority list:

• Identifiers: GS1 Digital Link as the URI structure; GTIN as the base product identifier for most consumer goods. These are already embedded in retail infrastructure and explicitly supported by the EU DPP FAQ guidance.
• Semantic format: W3C JSON-LD for machine-readable payloads. It supports semantic validation, is human-readable, and maps cleanly to the UNECE UNTP sample credential pattern.
• Attestation: Verifiable credentials (W3C VC Data Model) for third-party claims and audit evidence. The UNECE UNTP specification provides a worked example of a signed DPP credential.
• Registry integration: API-first integration with the EU DPP Registry. Avoid batch-upload-only workflows; they cannot support real-time updates when product data changes.
• Technical standards body: CEN-CENELEC JTC 24 is finalizing eight core interoperability standards for DPPs. Implementations that align with GS1 Digital Link and JSON-LD now are well-positioned for those standards.

Risk-mitigation practices:

• Use persistent URIs that will not break if you change hosting providers or platforms
• Version every passport record with a validFrom timestamp and maintain the full version history
• Require contractual evidence obligations from suppliers (not just best-effort requests)
• Validate JSON-LD payloads against the relevant schema before submission to the registry
• Maintain backup copies of all passport records and supporting evidence with timestamped proofs for market-surveillance requests

Pro Tip: When registering at item level, always include linked batch and model identifiers in the same submission. The registry expects these links; omitting them creates fragmented records that fail market-surveillance checks and cannot be resolved correctly by customs authorities.

The practical recommendation from the EU pilot programs (CIRPASS-2 and others) is to pilot now with open standards, then extend the schema when delegated acts finalize rather than waiting for perfect specifications before starting.

The brands that move fastest on DPP readiness share one trait: they treat it as a data infrastructure project, not a compliance checkbox. The ones that struggle are waiting for final delegated acts before touching their supplier data, which means they will be scrambling when mandatory dates arrive.

For fashion and consumer-goods teams in Central Europe, the most practical starting point is a model-level passport for your highest-risk SKUs: the products with the most complex supply chains, the most supplier touchpoints, or the ones most likely to fall under the first textile delegated act. A model-level passport covers every unit of a given product design, so you get broad coverage without the overhead of item-level serialization.

The pattern that works in practice: import your product catalog, send structured data requests to suppliers, collect and review evidence, publish a passport page with a QR code, and then iterate. The iteration part is what most brands underestimate. Product formulations change, suppliers change, certifications expire. A DPP is a living record, not a one-time document. Building the update workflow into your operations from day one is what separates brands that stay compliant from those that publish a passport once and let it go stale.

For apparel brands specifically, the clothing digital product passport guide covers the specific data fields, QR publishing options, and supplier evidence workflows relevant to garments and textiles.

Getting from a supplier spreadsheet to a published, registry-ready passport page is where most brands stall. DPP Grid is built specifically for that gap: import products from Shopify, CSV, or API; send structured data requests to suppliers; collect and manage evidence documents; use AI-assisted extraction with human review and approval; and publish permanent passport pages with QR codes.

!DDP Grid

Key capabilities tied directly to the readiness checklist above:

• Shopify, CSV, and API import to bring your existing product catalog in without manual re-entry
• Supplier evidence workflows that track response status, flag missing fields, and store documents with version history
• Model, batch, and item-level support so you can match the granularity your delegated act requires
• QR code publishing with GS1 Digital Link-compatible resolution to permanent passport pages
• AI-assisted data extraction with mandatory human approval before anything is published
• Registry readiness workflows to organize the data and evidence the EU DPP Registry will require

DPP Grid does not provide legal certification and does not claim that using the platform automatically makes a product compliant. It provides the data infrastructure, evidence management, and publication tools to organize and demonstrate your product information.

Start with a 14-day free trial at Dppgrid or explore the full platform solutions to see how it maps to your specific product groups and compliance timeline.

The sources below are the authoritative references for verifying DPP rules and examining sample schemas. Use the EU Commission pages for legal compliance questions and the technical specs for schema design.

• Digital Product Passport | Internal Market, Industry, Entrepreneurship and SMEs
• Consolidated TEXT: 32024R1781 — EN — 28.06.2024
• Digital Product Passport | UN Transparency Protocol - UNECE

A Digital Product Passport is a structured digital record linked to a physical product via a data carrier (QR code, RFID, or NFC). It contains identity, composition, provenance, care, repair, and end-of-life data, and is required for specific product groups under the EU's Ecodesign for Sustainable Products Regulation.

Batteries are the first mandatory group, with EV and industrial battery passports required from 2026. Textiles, iron and steel, furniture, mattresses, and ICT products follow under staged ESPR delegated acts currently in preparation.

Textile passports typically include fiber composition with percentages, recycled content, country of origin, manufacturing site, care instructions, microfibre release class, durability score, substances of concern, and end-of-life guidance. The JRC textile preparatory study confirms these as the core recommended fields.

The recommended approach is a QR code using GS1 Digital Link, which resolves a standard product identifier (GTIN) to a web-hosted passport page. RFID or NFC can be added for logistics and item-level tracking. The EU Commission's DPP FAQ guidance explicitly recommends GS1 Digital Link for interoperability.

DPP Grid provides registry readiness workflows, data organization, evidence management, and QR publishing tools to help brands prepare the information the EU DPP Registry requires. It does not provide legal certification and does not guarantee compliance, but it structures the data and evidence that registry submission depends on.

• Clothing Digital Product Passport: A 2026 Guide