Digital product passports only create value when the underlying data can be queried, validated, and exchanged. ESPR insists on open, machine-readable formats because brand-owned PDFs and bespoke portals prevent regulators and partners from working quickly. Article 10(1)(d) of the ESPR asks for data that is open, interoperable and machine-readable. In Traced, a passport is any JSON you upload. Each version is stored with a SHA-256 checksum, and earlier versions are kept. Traced does not yet check a passport's fields against the regulation, because the rules for iron, steel and aluminium are still being finalised.
Start with the bill of materials
A passport in TraceID is the JSON you supply, so you can separate structural data—materials, components, suppliers—from behavioural data such as lifecycle events and service history.
Layer events and lifecycle data
TraceID records each manufacturing batch with its operator, start and end times, and a PASS or FAIL result, and logs every scan of a trace ID with its time and location.
One record, two views
Traced keeps one record for each product, so there is nothing to clone for each stakeholder. The public scan page shows that record to anyone who scans the code. Signed-in staff also see the batch record, and their access is set by role, with four tiers from Super Admin to Client User.
The result: a digital product passport held as open, versioned JSON, with a checksum and earlier versions kept. The same scan URL also returns JSON, so other systems can read it. Reach out if you want to talk through what your passport should hold.
Need a clearer record model?
Discuss a practical Traced or Verified setup for your product and inspection workflow.
Talk to usRelated Articles
What a passport looks like for an industrial part
What DPP 4.0 and the Asset Administration Shell suggest for a machined part, what the Regulation...
Read What a passport looks like for an industrial part