⚖️ Why DPP is becoming essential for footwear

Footwear is a high-volume category with complex material mixes (rubbers, EVA/PU foams, textiles, leather, adhesives, coatings, metal/plastic trims) and often multi-tier supply chains.

That complexity creates real challenges:

• Material transparency (what’s in the product, and where)
• Substances of concern disclosure and safe handling (e.g., certain finishing chemicals, PFAS concerns in some treatments, adhesive chemistries, dyes)
• Durability and repairability expectations (replaceable components, care instructions, availability of parts where applicable)
• End-of-life sorting and recycling barriers (mixed materials, metals that can disrupt textile recycling, composite constructions)

Policy direction in the EU increasingly targets these topics. The Eco-design for Sustainable Products Regulation (ESPR) sets the core framework for DPP and enables delegated acts that define what data must be provided by product group.

The EU Strategy for Sustainable and Circular Textiles explicitly positions DPP as a requirement for textiles—and footwear is closely tied to textile ecosystems (uppers, linings, laces) and circularity infrastructure.

Indicative ESPR/DPP timeline milestones include:

• Dec 2025: delivery of DPP standards (CEN & CENELEC)
• Jan 2026: delegated act for Textiles DPP published
• Jul 2027: Textiles DPP enters into force (timing may evolve as delegated acts finalize)

📦 What goes into a Footwear Digital Product Passport (core data blocks)

DPP requirements ultimately depend on the delegated act for the product group.

However, the ESPR-required attribute families provide a practical structure that footwear organizations can start mapping now.

🆔 1) Identification & accountability (who made it, who placed it on the market)

Footwear DPPs commonly need to support:

• Economic operator details (manufacturer/importer) including name, contact details, unique operator identifier
• Importer information (including EORI number where applicable)
• Facility identifiers to trace production origin (important in multi-brand manufacturing)
• Commodity codes (e.g., TARIC code where required)
• A unique product identifier at the level required (model/batch/item)

📘 2) Product, operational, and compliance information

Examples of DPP-linked information for footwear:

• Consumer-facing instructions, warnings, safe-use guidance (care, cleaning, use limitations)
• Links/references to compliance documentation required under applicable rules
• Traceable references to technical files or certificates when relevant

🛠️ 3) Product lifetime, durability, repairability & circularity

Footwear DPPs can capture:

• Durability and reliability statements (where required/standardized)
• Repair and maintenance guidance (e.g., sole care, replacement recommendations, authorized repair pathways)
• Reuse/refurbishment readiness (what can be cleaned, reconditioned, replaced)
• End-of-life guidance: take-back, sorting instructions, disposal routes, recycling compatibility claims

🧪 4) Materials & substances of concern (composition + safe handling)

A footwear DPP may need to describe:

• Substances of concern present, their location, and concentration/ranges (at product, component, or spare-part level)
• Disassembly information relevant to safe handling and material recovery
• Instructions for safe use and handling where needed (especially for downstream recyclers)

🌍 5) Environmental impact & efficiency indicators (where required)

Depending on delegated act specifics and data maturity, this can include:

• Recycled content and recoverability potential
• Waste expectations and packaging metrics (weight/volume; product-to-packaging ratio)
• Microplastic release considerations (explicitly mentioned in ESPR attribute list)
• Environmental or carbon footprint fields (where required)
• Avoidance of design choices that block reuse/repair/upgrading/recycling

🏷️ The Product UID and the data carrier (QR/RFID) for footwear

✅ Product UID: the root of discoverability

The DPP architecture relies on a globally unique Product UID (or a UID that can be made globally unique upon scanning). In practice:

• The UID is usually encoded into a machine-readable carrier (commonly QR)
• If the UID is not a URI on the label (space constraints), it must be transformable into a canonical URI (RFC3986/RFC3987 concepts)

👟 Data carrier requirements that matter for footwear/textiles

The data carrier must be physically present on the product, packaging, or accompanying documentation as defined by delegated acts.

For textiles/footwear, practical data-carrier constraints include:

• Must support reuse and recycling
• Must resist water, heat, and pressure
• Must meet design and comfort standards
• Metals may interfere with textile recycling (important when considering RFID or metallic components)
• Must support effective sorting processes

🛒 Online sales: DPP access must still work

Even when customers cannot scan a physical label, DPP access should be provided via:

• a digital copy of the carrier, or
• a clickable link that resolves to the DPP information
  This aligns with the ESPR requirement to provide the Product UID for products listed in online marketplaces.

🔐 Access levels: transparency without exposing trade secrets

DPP data is not uniformly public. An ESPR-aligned access model typically includes:

1- Public model-level data: product identification, safe use, key sustainability/circularity attributes, dangerous substances overview (as required)

2- Legitimate-interest access (and Commission): deeper composition, disassembly instructions—useful for repairers/recyclers but potentially sensitive

3- Authorities/notified bodies/Commission only: restricted compliance evidence (e.g., test report results proving compliance)

4- Individual product info: item-level lifecycle status and service history where relevant

A footwear DPP should be designed for role-based filtering so each actor sees what they are entitled to—no more, no less.

🔎 How a Footwear DPP works in practice (scan → resolve → access)

A typical journey is:

1- Scan the QR/RFID on the shoe (or click the online link)

2- Read Product UID (or Product DID in DID architectures)

3- If needed, perform UID → URI transformation (e.g., GTIN → URI patterns)

4- Use a resolver (HTTP approach) or DID resolution (DID approach) to locate the correct endpoints

5- A Policy Decision Point (PDP) enforces access permissions by role

6- Retrieve passport data from decentralized DPP data repositories, with continuity ensured through backup providers and an archive function

This structure supports long product lifecycles and resilience if a brand, domain, or operator changes.

🧭 Architecture options for Footwear DPP: HTTP URIs vs DIDs

🔗 Option A: HTTP URI-based access (web-native, retail-friendly)

• Uses standard internet protocols (HTTP/HTTPS + TLS)
• Can leverage established identifier ecosystems (e.g., GS1 Digital Link transforming GTIN into a URI)
• Uses resolvers (REO resolver + potential default EU resolver fallback)
• Familiar deployment and easy adoption in retail contexts

🪪 Option B: DID-based access (identity-forward, resilient)

• Uses Decentralized Identifiers (DIDs) as URIs that resolve to a DID Document
• DID Document contains:
• Verification methods (keys)
• Service endpoints (where to fetch DPP data)
• Enables privileged access via Verifiable Credentials (VCs) and role proof
• Designed to reduce reliance on DNS/domain ownership risks and strengthen identity/auth

In many real programs, organizations evaluate both approaches based on ecosystem readiness, device compatibility, governance, and long-term resilience.

✅ Data quality, interoperability, and validation (RDF + SHACL concepts)

Many DPP reference architectures treat the DPP as a knowledge graph, often expressed using Semantic Web standards (e.g., RDF).

This matters because footwear data is heterogeneous: bills of materials, chemical declarations, supplier docs, care instructions, certifications, and packaging specs.

A SHACL control engine can distribute templates (“shapes”) for:

• required fields and relationships
• units/ranges and consistency checks
• automated validation before publishing and during updates

This supports market surveillance, reduces errors, and makes passports more machine-actionable.

⚙️ Implementation roadmap for footwear companies (practical steps)

To prepare for a footwear DPP program, organizations typically follow these steps:

1- Define scope: model vs batch vs item-level DPP strategy

2- Map required attributes to internal systems (ERP/PIM/PLM) and supplier data sources

3- Choose an identifier strategy (UID format, GTIN alignment, URI/DID readiness)

4- Select a data carrier that meets textile durability and recycling constraints

5- Design role-based access (public vs legitimate interest vs authorities) and the PDP policy model

6- Build the data pipeline: collect → curate → model → transform → publish

7- Implement validation (SHACL-like rules) and governance for ongoing updates

8- Plan for decentralized storage + backup + archive so passports remain accessible long-term

🤝 How ComplyMarket delivers Digital Product Passport (DPP) for Footwear

ComplyMarket offers Digital Product Passport for Footwear as part of its software and integrated Compliance Management Platform, helping brands, manufacturers, and importers move from scattered product documentation to a structured, scalable, audit-ready DPP capability.

With ComplyMarket, footwear organizations can:

• Define DPP scope and data model aligned to ESPR attribute families (model/batch/item strategies)
• Manage Product UID and data-carrier rollouts (QR/RFID-ready workflows)
• Configure role-based access so public users, legitimate-interest actors, and authorities see the right information
• Connect DPP preparation to operational reality by integrating with ERP/PIM/PLM and supplier documentation streams
• Apply data quality controls and validation-ready governance to reduce missing fields, inconsistent values, and compliance risk
• Support long-term continuity with structured publishing and lifecycle updates that fit circularity use cases (repair, resale, recycling)

Because ComplyMarket unifies compliance data, product information, and controlled publishing in one platform, it becomes an exceptional foundation for delivering Footwear DPP efficiently—without vendor lock-in thinking, and with the interoperability and auditability that EU-aligned DPP programs demand.