🧪 Why a DPP is different (and harder) for chemical products

Chemical products introduce challenges that a DPP system must handle by design:

• Hazard and safe-use criticality (high consequence of errors): downstream users and authorities need accurate, current information.
• Composition confidentiality: detailed formulation data can be commercially sensitive, yet some actors legitimately require deeper visibility.
• Batch/lot variability: composition or properties may differ by batch, plant, or supplier—so deciding model vs batch vs item-level passport scope matters.
• Packaging and logistics realities: chemicals are shipped in many formats (small packs, drums, IBCs, bulk), which affects data carrier durability and placement.
• Multi-actor lifecycle: manufacturers, importers, distributors, industrial users, waste handlers, and authorities all interact with the product data at different moments—and need different access rights.

These characteristics map directly to core DPP principles under ESPR: strong identification, controlled access, interoperability, and long-term availability.

🧩 What a Chemical Products DPP typically contains (ESPR-aligned data blocks)

DPP data requirements are shaped by the Eco-design for Sustainable Products Regulation (ESPR) and its delegated acts.

While chemical-product-specific delegated acts will define the exact mandatory fields, ESPR already outlines the key categories of information a DPP can include.

Below is a practical structure for chemical product passports, aligned with ESPR’s required attribute families.

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

• Name, contact details, and unique operator identifier of the economic operator established in the Union
• Importer information (including EORI where applicable)
• Unique facility identifiers (supporting traceability across multi-site production)
• Additional operator identifiers beyond the manufacturer (where applicable)

For chemicals, these fields support rapid escalation (incidents), targeted surveillance, and consistent origin tracing when products are repacked or rebranded.

📘 2) Product, safety & compliance information

• User manuals / instructions / warnings / safety information required by applicable Union law
• References to compliance documentation (e.g., declarations, technical documentation pointers, certificates)
• Commodity codes (e.g., TARIC) where required
• Global identifiers such as GTIN (ISO/IEC 15459-6 or equivalent) where used
• The unique product identifier at the level mandated by the relevant delegated act

For chemical products, this block is where companies usually connect existing safety and compliance documentation to a standardized, machine-readable access layer—without duplicating data across systems.

♻️ 3) Product lifetime & sustainability information

• Durability and reliability (packaging/container integrity and shelf-life, where applicable)
• Ease of reuse/refill/returnable packaging/containers 
• Instructions to minimize environmental impact and to enable correct end-of-life handling
• Recycling quality and ease (including packaging-related considerations)

Even when the chemical itself is consumable, packaging, return/take-back systems, and waste classification guidance can be highly relevant to circularity outcomes.

🧷 4) Materials & substances of concern (SoC) information

• Names of substances of concern present
• Location of substances of concern (as applicable)
• Concentration, maximum concentration, or concentration range
• Instructions for safe use
• Disassembly information (often relevant for packaging/components and safe handling)

This block is where access levels become essential: chemicals may require publishing certain information broadly while restricting formulation-level details to legitimate actors.

🌍 5) Environmental impact & efficiency (where applicable)

ESPR outlines a broad set of potential environmental and efficiency attributes, such as energy/resource use, recycled content, recovery potential, waste generation, environmental footprint, carbon footprint, emissions to air/water/soil, and conditions for use.

For chemical products, organizations often start with what they can substantiate reliably and expand over time—especially if future delegated acts require more standardized footprint or lifecycle metrics.

👥 Roles and responsibilities: the Responsible Economic Operator (REO)

Under ESPR, the Responsible Economic Operator (REO) can be a manufacturer, authorized representative, importer, distributor, dealer, or fulfillment service provider.

🔑 In the DPP system, the REO is central to:

• Ensuring a Product UID exists and is attached to the product (via a data carrier)
• Uploading mandatory DPP information and keeping it accessible
• Managing lifecycle updates (e.g., corrections, re-labelling events, repackaging, downstream status changes where applicable)

⚠️ A recurring complexity is lifecycle boundary-setting: if a product is refurbished, repackaged, or remanufactured in a way that makes it “new” under the applicable rules, responsibility and even identifier strategy may shift (including whether a new DPP and/or new Product UID is required).

🔐 Access levels: protecting sensitive chemical data while enabling legitimate use

A DPP is not automatically “fully public.” ESPR outlines distinct access levels, including:

• 👤 Public product model information: low-security, high-value facts (identification, dangerous substances as required, safe usage guidance, sustainability attributes).
• 🧑‍🔧 Legitimate-interest access (and the Commission): higher-detail information that could reveal know-how (e.g., detailed composition, disassembly guidance).
• 🏛️ Authorities / notified bodies / market surveillance (and the Commission): restricted compliance evidence such as test report results proving compliance.
• 🔒 Individual product information for legitimate interest: classified, purpose-limited access (useful for item/batch-specific traceability).

For chemical products, this access model is often the difference between a DPP that is adopted at scale and one that is blocked by confidentiality concerns.

🏷️ Data carriers for chemicals: QR, RFID, and real-world durability

ESPR requires a machine-readable data carrier that is physically present on the product, packaging, or accompanying documentation (as specified by delegated acts). The carrier can be a QR code, RFID, or another suitable form.

Chemical product realities to design for:

• Resistance to exposure: moisture, abrasion, solvents, UV, temperature changes
• Placement: container vs outer packaging vs documentation (important for bulk shipments)
• Readability lifecycle: the product may move through multiple hands and storage conditions
• Online sales readiness: ESPR requires DPP accessibility for products sold online—commonly via a link or digital copy of the carrier.

🔎 How the DPP works in practice (scan → resolve → authorize → retrieve)

A practical DPP user journey—applicable to chemical products—looks like this:

1- A user scans the data carrier on the product/packaging

2- The scan yields a Product UID (or a DID/URI)

3- If needed, a UID → URI transformation converts compact identifiers into resolvable URIs (web identifiers).

4- A resolver routes the request to the correct data location (often in decentralized repositories)

5- A Policy Decision Point (PDP) enforces role-based access and usage policies

6- The system retrieves DPP data from Decentralized DPP Data Repositories, supported by backup and (where necessary) archival services for long-term continuity

This matters for chemicals because data must remain accessible even if an operator changes systems—or, in extreme cases, goes out of business.

✅ Data quality and validation: knowledge graph + RDF + SHACL

CIRPASS proposes the DPP as (conceptually) a knowledge graph: information represented as semantic triples and rooted in a unique product identifier.

This improves interoperability and futureproofing because new data can be attached without redesigning the entire schema.

To ensure integrity and compliance, the system uses SHACL (Shapes Constraint Language) to validate RDF graphs:

• Regulators can translate delegated act requirements into SHACL shapes
• REOs can pre-validate DPP data before submission
• Market authorities can validate DPP data consistently during surveillance

For chemical products—where incorrect units, missing substance disclosures, or inconsistent identifiers can create serious downstream risk—automated validation is a major operational advantage.

🧭 Architecture options for a Chemical Products DPP: HTTP URIs vs DIDs

Two access architectures are commonly discussed:

🔗 HTTP URI-based access (web-native, widely compatible)

• Built on HTTP/HTTPS and resolvers
• Supports converting identifiers into URIs (including approaches inspired by GS1 Digital Link)
• Typically easier to deploy across retail and web ecosystems

🪪 DID-based access (stronger identity + resilience)

• Uses Decentralized Identifiers (DIDs) that resolve to DID Documents
• Adds an identity and authorization layer through Actor DIDs and Verifiable Credentials (VCs)
• Can reduce dependency on DNS/domain control and improve long-term persistence

For chemical products, DID-based models are particularly compelling when privileged access must be enforced tightly and audited—without making sensitive information broadly discoverable.

🤝 ComplyMarket Digital Product Passport Service for Chemical Products

ComplyMarket provides Digital Product Passport (DPP) for Chemical Products through its integrated Compliance Management Platform, helping teams organize required data, control access, and publish an audit-ready passport without relying on scattered files or siloed tools.

How ComplyMarket supports chemical DPP delivery

• DPP scope & data mapping: model/batch/item strategy aligned to ESPR-style data blocks.
• Identifiers & carriers: Product UID setup, UID→URI planning, and QR/RFID rollout fit for chemical packaging.
• Role-based access: public vs legitimate-interest vs authority access aligned with PDP principles.
• Data quality & interoperability: machine-readable, validation-ready structure (knowledge-graph/SHACL mindset).
• Systems integration: connects with ERP/PIM/PLM and document repositories to reduce manual work.
• Continuity: supports decentralized storage patterns with backup/archive readiness for long-term access.

When you need a chemical DPP that remains trusted, maintainable, and scalable, ComplyMarket delivers the platform and governance to run it as an ongoing compliance capability—not a one-time publishing exercise.