Product Passports¶
The Product Passports workspace is a domain adapter over the general OpenETR protocol model.
It is for product data artifacts, compliance evidence, manufacturing metadata, lifecycle attestations, and related product records. It is not about personal identity passports.
EU Regulatory Context¶
The European Union is introducing Digital Product Passports progressively through the Ecodesign for Sustainable Products Regulation and sector-specific legislation. The EU DPP Registry became operational on 20 July 2026, and the first mandatory deadline applies to specified batteries from 18 February 2027.
The EU model combines a central Registry for identifiers, registration, semantics, and enforcement with decentralized passport data maintained by the responsible economic operator or a DPP service provider.
OpenETR does not replace the Registry, product-specific delegated acts, harmonized standards, economic-operator responsibilities, or market-surveillance decisions. It can preserve exact passport versions and signed lifecycle evidence as an independently verifiable DCR.
What A Product Passport Is In OpenETR¶
In this domain:
- the Product Passport file or data artifact is the Digital Artifact;
- the Product Passport digest is the stable object identity;
- each signed OpenETR Anchor, control, or linked-evidence event is a record in the Product Passport DCR;
- later lifecycle documents can be attached as linked evidence records;
- the linked set of Anchor Records and later evidence records is the Product Passport control graph;
- the broader linked set of Anchor, control, and evidence records is the Product Passport evidence graph.
The Product Passport itself may be a PDF, image, JSON document, data bundle, credential, registry export, or another canonical artifact. OpenETR does not need to parse it before it can identify the artifact by digest and record control-relevant evidence.
Requirements Mapping¶
A working Digital Product Passport requirements overview is available at Product Passport Requirements Mapping.
The mapping is intentionally incomplete so each requirement can be reviewed before project evidence, gaps, and recognition-boundary notes are filled in.
Current App Surface¶
The live Product Passports workspace is:
https://openetr.org/digital-product-passports
The current page supports two starting workflows.
| Workflow | Purpose |
|---|---|
| Query Product Passport Control | Upload a Product Passport file and query the OpenETR control graph associated with its digest. |
| Create Product Passport Evidence Record | Publish the initial OpenETR evidence record for a Product Passport document using the selected profile signer. |
Product Passport Metadata¶
The first Product Passport control-record flow can carry basic signed metadata:
| Field | OpenETR Tag |
|---|---|
| Product name | product_name |
| Product id | product_id and record_reference |
| Manufacturer or issuer | manufacturer |
| Batch or lot | batch_or_lot |
| Description | record_description |
| Domain | domain=digital_product_passport |
| Document type | document_type=product_passport |
These tags are early domain-adapter metadata. They make the evidence record easier to inspect without turning OpenETR into a complete Product Passport schema or compliance engine.
Likely Future Evidence Records¶
Product Passport workflows will likely need domain-specific profiles and verifier policies for:
- manufacturer or importer attestations;
- material provenance;
- repair, refurbishment, and resale history;
- sustainability and compliance claims;
- recall, restriction, or safety notices;
- recycling, recovery, or end-of-life events;
- registry, auditor, or marketplace recognition.
OpenETR can provide the signed graph and digest linkage. Domain policy decides which claims are trusted, which actors are recognized, and what legal, regulatory, or operational effect follows.
Relationship To Warehouse Receipts¶
Product Passports and Warehouse Receipts should use the same underlying OpenETR vocabulary:
| Shared OpenETR Concept | Warehouse Receipts | Product Passports |
|---|---|---|
| Digital Artifact | Receipt document | Product Passport artifact |
| Anchor record | Initial receipt control evidence | Initial Product Passport control evidence |
| Linked evidence record | Supporting receipt evidence or attestations | Repair reports, recall notices, lifecycle certificates, audit evidence |
| Evidence graph | Receipt control and evidence history | Product Passport control and lifecycle evidence history |
| Recognition layer | MLWR law, registry rules, warehouse policy | Product regulation, compliance policy, registry rules, marketplace policy |
This is the domain-adapter pattern: each workspace speaks its own language, but the DCR evidence and state-derivation model stay general.