For manufacturers
The same question, six formats, every quarter
Passport obligations land on brands, but the data lands on you. Assert each figure once, signed under your own key, and let every customer verify it instead of asking you to re-enter it.
- Assert
- Once, signed
- Events
- EPCIS 2.0
- Integration
- API or export
Definition
What does a supplier contribute to a Digital Product Passport?
Suppliers contribute the evidence behind a passport: material composition, recycled content, certifications, carbon footprint figures and production events. In CirculeID each contribution is issued as a Verifiable Credential signed by the supplier, so the customer can prove who asserted it without the supplier re-entering it per customer.
Signing matters to both sides. Your customer needs attribution to satisfy the ESPR; you need a record of exactly what you asserted and when, rather than a figure someone at the brand transcribed two years ago.
What changes
From questionnaire response to issued credential
Assert under your own key
Claims are issued under your organisation’s decentralized identifier, so attribution never depends on the customer’s records.
One dataset, many formats
Issue against the standards model once; each customer projects it into the form their regulation or portal wants.
Component-level claims
Attach evidence to the component or batch it applies to, not to a whole catalogue with a footnote.
MES and ERP integration
Data flows from the systems you already run. No migration, and no second place to key the same figure.
Validity periods
Issue a figure with an expiry so an out-of-date footprint stops being treated as current.
Confidentiality preserved
Assert a property of what you supply without revealing which upstream party it came from.
Onboarding
What it takes to start supplying credentials
- 01
Establish your identity
Your organisation receives a decentralized identifier and a signing key. Every claim you issue afterwards is attributable to it.
- 02
Agree the claim set
Decide what you will assert — composition, recycled content, certifications, footprint — and at what granularity.
- 03
Connect the source system
Values arrive from the MES, ERP or laboratory system through the API or a scheduled export, rather than by hand.
- 04
Issue and let customers verify
Customers pull your signed claims into their passports and verify them independently. The questionnaire stops arriving.
Answers
Frequently asked questions
Why should a supplier care about product passports?
Because the requests are coming either way. Every customer subject to the ESPR (EU) 2024/1781 will ask for composition, footprint and recycled content, in their own format, on their own schedule. Issuing the data once as a signed credential your customers can each verify replaces that queue of questionnaires with a single artefact.
Do we have to expose our own suppliers to our customers?
No. You can assert a property of what you supply — recycled content, a certification, a footprint figure — without revealing which upstream party it came from. That is the practical advantage of signed claims over shared databases: the claim is verifiable without the supply chain behind it being visible.
What does signing a claim commit us to?
The same thing a signed declaration on letterhead commits you to, with better provenance. The credential records that your organisation asserted a specific value on a specific date. It does not expose your systems, and it can be issued with a validity period so a figure is not treated as true indefinitely.
How does this fit with our MES or ERP?
It sits above them. Data flows in through the REST API or a scheduled export, and production events can be written as EPCIS 2.0 events from the systems already emitting them. There is no migration and no second place to key data, which is usually the condition of a supplier agreeing at all.
What if different customers want different formats?
They will, and that is the problem this is designed to end. The claim is issued once against a standards-based model; each customer’s platform projects it into whatever their regulation or portal asks for. You maintain one dataset rather than one per customer relationship.
Next step
Answer the next questionnaire once
Bring the last data request a customer sent you. We will show you the credential that would have satisfied it, and every one after it.