Loading...
Loading...
A versioned regulatory state representing a product at issuance.
Not a marketing file. Not a PDF. A structured, liability-carrying data object.
A Digital Product Passport (DPP) is not merely a compliance requirement. It is a persistent regulatory data object that must remain resolvable for the lifespan of the product.
Once issued, a DPP becomes a regulatory reference. It defines what was declared at a specific moment in time.
Under ESPR, the passport is not symbolic. It becomes a liability anchor detailing:
It may be requested years after issuance. It must resolve to the exact structured state that was originally published.
// Retroactive mutation is a liability risk.
The moment a DPP is published, it transitions from internal documentation to a regulatory artifact. This creates a clear boundary where operations end and legal liability begins.
Internal preparation phase.
The committed regulatory declaration.
Products evolve. Suppliers change. Materials change. Regulatory thresholds change.
A DPP cannot be overwritten.
Instead of replacing data:
Each batch resolves to the correct regulatory version.
Historical compliance cannot be retroactively mutated. If a batch was produced under a specific supplier declaration, that declaration must stand permanently.
Learn how versioning worksDPPs resolve via QR or API. Resolution does not expose internal ERP systems.
The lifespan of the passport mirrors the lifespan of the physical product.
Lifecycle events extend the passport. They do not overwrite the original state. Each event is strictly appended to the Event Journal.
Not all data is public. Disclosure is controlled by RBAC and policy enforcement.
High-level compliance data and consumer transparency metrics.
Full structured compliance layer, including upstream supply chain data and CE documentation.
Service-relevant components, schematics, and secure disassembly instructions.
Regulators do not see less. Public users do not see more.
The DPP is not standalone. It is generated and protected by the core UCVreg platform architecture.
It is a regulated, versioned, verifiable artifact.