The challenge
A passport is an operating record, not a one-time page.
Different audiences need different product information, permissions, and update cycles. CommonShare separates source evidence from published views so one governed product record can support regulators, customers, repairers, recyclers, buyers, and supply chain partners.
Product workflow in practice
Move from product model to controlled publication.
Build the record once, govern every contribution, and publish the right view for each audience.
- Product and complianceDefine the passport object
- Suppliers and internal teamsConnect lifecycle evidence
- CommonShare networkResolves records and coordinates the configured workflow
- Compliance, service, and marketingReview audience views
- Product operationsPublish and maintain
01 InitiateDefine the passport object02 ResolveConnect lifecycle evidence03 CoordinateReview audience views04 DecideKeep publication authority accountable05 ActPublish and maintain the record
Define the passport object
Identify the model, batch, or individual product; its identifier; applicable data fields; lifecycle status; and audience rules.
- Input
- Mapping, Passports
- Decision or control
- Runs within the configured workflow boundary.
- Handoff
- Connect lifecycle evidence · Suppliers and internal teams
- Define the passport objectProduct and compliance
The Digital Product Passport remains connected to its source records, lifecycle evidence, approvals, permissions, and intended downstream use.
Connected evidence model
One product identity, many governed views.
Every object remains connected to the people, evidence, versions, and decisions that give it meaning.
- 01Product model, batch, or serialized identity
- 02Components, materials, and composition
- 03Organizations, facilities, and countries
- 04Tests, declarations, certificates, and claims
- 05Carbon, footprint, durability, and repair data
- 06Access roles, QR destinations, versions, and lifecycle status
Connected capabilities
Configure one platform around the work.
Bring the right capabilities into one accountable flow.
Multi-tier network mapping
Connect product models, batches, components, materials, facilities, and lifecycle records around one governed identity.
Supplier collaboration
Request structured lifecycle data and supporting evidence through shared supplier and internal-team workflows.
Evidence governance
Extract, version, approve, and preserve lifecycle evidence with a reviewable audit trail.
Cases and decision workflows
Route exceptions, approvals, publication reviews, and updates to accountable teams.
Digital Product Passports
Publish persistent QR and role-based product views from the governed lifecycle record.
Impact calculations
Keep carbon, footprint, durability, repair, and other calculation versions connected to their methods and evidence.
Controlled product outputs
Publish the right role-based product view for customers, buyers, repairers, recyclers, auditors, and authorities.
Commons Architecture
The shared foundation beneath the workflow.
Architecture keeps identity, data exchange, claims, permissions, automation, and human accountability coherent across organizations.
CommonID Registrar
Give the product and connected records persistent identities across the network.
Data Interoperability
Align source systems and audience views around shared product meaning and exchange policy.
Verified Claims Architecture
Keep visible claims connected to scope, evidence, and responsible verification.
Where it applies
See the workflow in industry context.
Apparel & Textiles
Connect styles to materials, facilities, impact, care, and circularity views.
Batteries & Energy Storage
Maintain model- and battery-specific data, access roles, and lifecycle status.
Requirements and methods
Connect evidence to the right pathway.
ESPR
Delegated acts define the products, data, access, and timing for ESPR passports.
EU Batteries
The Batteries Regulation creates a sector-specific passport for covered battery categories.
CommonShare can publish product passports today. A legal passport obligation, required data set, access model, and compliance date arise from the applicable product-specific act or separate sector legislation.
Frequently asked
Digital Product Passports, made clear.
Practical answers about scope, workflow, evidence, and accountable decisions.
Yes. Role-based views can separate public information from records intended for buyers, suppliers, repairers, recyclers, auditors, or authorities.
Design holistically