Verifiable Digital Product Passports.
Structured, version-controlled product records built for compliance beyond issuance.
UCVreg helps manufacturers, importers and supply-chain teams prepare, publish and maintain DPPs with controlled access and traceable lifecycle history as ESPR requirements evolve.
What is a Digital Product Passport?
A Digital Product Passport is the digital record behind a product. It brings together the product facts, the evidence behind them and the record of what was published.
A QR code is not the passport
A QR code or other data carrier is simply the link that takes someone from the product to its record. If the product facts are wrong, or there is no way to show that the record has not been changed, the code alone means very little.
The details depend on the product
There is no single DPP checklist for every product. Under ESPR, the required information, who can see it and when it is needed depend on the rules for that product group.
UCVreg keeps published versions and checks their integrity so you can show a clear record history. These are platform controls, not requirements that apply universally across the EU.
Structured data with a clear publish moment
A Digital Product Passport is a structured data object tied to a specific product identity. It holds the product information that must be available for compliance, market access and downstream actors.
Depending on the applicable product rules, a DPP may include fields such as:
- Material composition
- Supplier identity
- Environmental metrics
- Compliance statements
- Conformity documentation
These are illustrative examples. Exact required fields are defined by product-specific ESPR delegated acts and other applicable rules—not a single universal template.
What matters operationally is the transition from editable preparation to an approved published DPP state that can be resolved later with a clear publication history.
From draft to published
Before publication, teams prepare and validate the record. After approval, the passport becomes the published product state that downstream resolution and audits refer to.
See how publish-time anchoring works on the UCVreg platform.
Draft
Editable preparation for the product record.
- [x] Editable
- [x] Internal review
- [x] Not yet published
Published
Approved product state available for resolution.
- [x] Versioned publication
- [x] Resolvable identifier
- [x] Traceable history
From physical product to the right digital view
A DPP connects a physical product to the right structured view through a controlled resolution path—without exposing internal operational systems.
How resolution works
- 01Product / model / batch / item
- 02Identifier
- 03Data carrier
- 04Resolver
- 05Appropriate view
- Deterministic resolutionThe data carrier resolves to the published passport for that product identity.
- Controlled disclosureDifferent actors can receive different views according to the applicable access rules.
- Operational isolationPublic and partner resolution does not open internal ERP, PLM or PIM systems.
New versions. Prior history stays.
Products, suppliers and materials change. A DPP must keep those changes traceable.
UCVreg prevents silent overwriting of previously published passport versions. Updates create a new version while earlier published versions remain available in history.
Instead of replacing a live record in place:
- v1.0 remains in history.
- v2.0 is issued as the new published version.
Each product identity can resolve to the correct published version for that point in time.
Why the trail matters
When a batch or model was placed on the market under a specific published declaration, that declaration should remain reconstructable later—not quietly rewritten.
See how versioning works on the platform
Issuance is only the beginning
After publication, a DPP may need to carry product-relevant lifecycle information for as long as the applicable rules require.
Depending on the product, that can include events such as:
Which lifecycle information applies depends on product-specific rules. Lifecycle updates extend the passport record; they should not erase the original published issuance state.
One passport. Role-aware views.
Not every actor needs the same depth of product information. Access categories below are illustrative; exact rights depend on the applicable product rules and your disclosure policy.
Public view
High-level product and transparency information intended for open resolution.
Authority view
Deeper compliance and evidence layers for market surveillance and regulatory review.
Repair view
Service-relevant information for authorised repair and maintenance actors.
Access is policy-driven. Public users should not receive restricted layers; authorised actors receive the views their role requires.
Backed by the UCVreg system of record
The DPP experience sits on platform capabilities for versioning, integrity verification and controlled access—without repeating the full architecture here.
Versioning
Integrity verification
Controlled access
Easy mistakes to avoid
A PDF export
A static file cannot provide controlled resolution, version history or role-based access.
A product brochure
Marketing pages are not structured compliance records tied to product identity.
A marketing badge
A transparency sticker is not a verifiable, version-controlled product passport.
The practical DPP implementation guide
A walkthrough of ESPR DPP requirements, product identifiers, data carriers, access models, lifecycle expectations and implementation planning.
Calculate your product risk and get your free report.
A few simple questions. They show which product rules may need a look before a sale, launch, or supplier call gets stuck.
Direct Rule Screening
Instant applicability check across ESPR, DPP, EUDR, PPWR & Battery Regs.
Risk & Gap Exposure
Identify supplier data missing links and customs audit bottlenecks.
Free Audit Report
Receive a structured, actionable executive roadmap with zero obligation.
Build DPPs that still work years later
If you are building ESPR readiness, start with a controlled path from draft to published passport—with resolution, access and version history designed in from the start.