Digital Product Passport
Most of a product passport is data you already hold.
A passport has to say what a product is made of, where it came from, how long it lasts, and what evidence sits behind each claim. In Prduct those are ordinary product fields – material composition read from your real bill of materials, plus origin, lifespan, warranty and designed-for-disassembly – so the passport publishes from the records you already maintain instead of being re-keyed into a second system. What you don’t hold, you request from the suppliers who do, over one link with no login.
Trusted by
GDPR-compliant · EU-hosted data
What we actually do
The passport is published from your records, not rebuilt beside them.
Each requirement on the left is set by the ESPR itself – Regulation (EU) 2024/1781. Beside it, the part of Prduct that produces it.
Material composition
What the product is made of, at component level.
The Materials block reads your real bill of materials. Correct a component once and every product built from it follows.
Evidence
The documents behind each claim: conformity declarations and certificates.
Certificates render only when a file is attached, so a claim never appears without its evidence. Expiry dates travel with it.
Product characteristics
The exact data list arrives per product group, in a delegated act.
Recycled content and energy class you add as your own fields Origin, lifespan, warranty, designed-for-disassembly and sustainable share already ship as fields. Anything new is configuration, not a release.
Model, batch or item
The passport sits at one of three levels – the act chooses which.
Per-item passport links are created one at a time A serialised item is a full record with its own identifier and its own passport. The granularity is already there.
Data quality
Accurate, complete and up to date.
Readiness is measured against your own required fields, not against a delegated act The live passport is derived from the record, so a correction reaches it at once. Every value carries who supplied it, when, and who approved it.
Proof over time
What you published has to stay provable.
While a version is published, the public page serves that snapshot Publishing a version freezes the data and the layout, with the publisher and timestamp, comparable against earlier ones.
One product, decomposed
Every part of this chair is its own record.
A passport is a claim about a whole product, but the data lives in its parts – and each part has a different supplier, a different certificate and a different level of completeness. Pick a component to see what Prduct holds for it – and this is not only an internal view: the published passport can show the bill of materials too.
Select a part of the chair
-
Oeko-Tex · validMaterialWool bouclé over CMHR foamWeight1,650 gSupplierTextile weaver · SwedenData readiness 100%
-
Oeko-Tex · expires in 41 daysMaterialWool bouclé over CMHR foamWeight2,240 gSupplierTextile weaver · SwedenData readiness 85%Outstanding: recycled-content share
-
FSC · validMaterialSolid oakWeight1,120 gSupplierOak mill · DenmarkData readiness 100%
-
FSC · validMaterialSolid oak, incl. seat and side railsWeight2,250 gSupplierOak mill · DenmarkData readiness 100%
-
Not providedMaterialStainless steel, grade 304Weight180 gSupplierFastener works · LithuaniaData readiness 40%Outstanding: material declaration, substances of concern
-
Declaration · validMaterialRecycled polyamide feltWeight40 gSupplierFelt converter · FinlandData readiness 90%Outstanding: country of origin
-
Declaration · validMaterialCorrugated board and LDPE filmWeight190 gSupplierPackaging converter · DenmarkData readiness 95%Outstanding: recycled-content share
The passport itself
What your customer actually opens.
Not a PDF, and not a barcode pointing at a marketing page. A public product page on its own link, built from blocks that read your record.
- Each block reads a field, so one correction reaches every passport. Blocks with no data don’t render – never a blank claim.
- Save a design as a template and attach it in bulk. Each product keeps its own copy, so editing one never touches the others.
- Your logo and page colour, served on your own domain rather than ours.
- Several share links per product – campaign, packaging variant, market – each reporting its own opens, with country and city.
- Live by default, freezable on purpose: it reads the current record until you publish a version, then serves that snapshot.
What you get on day one
114Product fields ready before you configure anything
17Passport blocks, each reading a field from your record
10Pre-built integrations, plus a documented REST API
Model · batch · itemPassport granularity, already in the data model
One linkWhat a supplier needs to answer – no account, no seat
One platform, beyond the DPP
The same product and material data powers your neighbouring EU obligations.
PPWR and the passport ask for a great deal of the same underlying data: what a product and its packaging are made of, how much of each material, where it came from and who supplied it. Map it once and both obligations read from the same records.
The Digital Product Passport, answered plainly.
What is a Digital Product Passport?
A structured electronic record of a product, reachable from the product itself through a data carrier such as a QR code. The EU’s Ecodesign for Sustainable Products Regulation sets out the architecture and lists the data elements; the requirements that will actually apply to your product arrive later, in a delegated act for your product group. In practice it means the data behind your product claims has to be organised, current, evidenced, and reachable by whoever opens it.
How is a DPP different from a QR code or a barcode?
The QR code is only the doorway. A barcode or plain QR code points at a fixed destination – usually a marketing page or a PDF – and carries no obligations about what sits behind it. A passport is the record itself: specified data, at a defined level (model, batch or item), which has to stay accurate and stay available. The carrier is interchangeable; the record and its duties are the substance.
When do I need one?
One date is legally fixed: from 18 February 2027, every LMT battery, every industrial battery above 2 kWh and every electric vehicle battery placed on the EU market needs a battery passport, under Article 77 of Regulation (EU) 2023/1542. For everything else the ESPR sets the framework, but the requirements arrive per product group through delegated acts and none of those dates are settled. Textiles and apparel, furniture, tyres, mattresses, iron and steel, and aluminium are named as the first priority groups.
We are waiting for the legislation to be finalised. Should we do anything now?
The parts of a passport that take longest are the parts that do not depend on the delegated act. Knowing which components go into which product, what they are made of, who supplied them and which certificates cover them is work you have to do whatever the final data list says – and it is the work that involves other companies, which is why it takes months rather than weeks. A data list can be configured once it is published. Supplier relationships cannot be configured retroactively.
Which standards does the passport follow?
What we publish today is a public per-product passport on a persistent unique address, derived from your product data, with an auditable published-version history behind it. To be plain about the rest: CEN-CENELEC has published European standards for the passport, and the Commission’s own EU registry has been live since July 2026 – we are not certified against any delegated act or data-carrier standard, and we do not submit to that registry yet. If a specific act or standard decides your purchase, ask us and we will tell you exactly where we stand rather than guess.
Does Prduct connect to our ERP or PIM?
Yes, through integrations you configure rather than a one-click app store. There are ten pre-built integrations – including Shopify, GS1, Struct, DynamicWeb and the EU’s own TRACES system – plus a documented, versioned public REST API with bulk operations. The API is unusual in that it exposes the data model itself and not just records: your systems can create the fields and the requirement templates, then load data against them programmatically. Inbound data is non-destructive by default – external values sit alongside yours until you accept them, so a sync never silently overwrites what you own.
A passport changes over time. Can we show what it said when a product shipped?
Yes. A passport is live by default – it reads your product data as it stands now, so a correction reaches every passport showing that field. You can also publish a version, which freezes a complete snapshot: the product data and the exact layout it was showing. Versions are listed with who published them and when, can be opened individually and compared against each other. Worth knowing how the two interact: once a version is published, the public page serves that snapshot rather than live data until you publish again.
Does Prduct guarantee compliance?
No, and no software can. Compliance is a legal determination about your products, made by you and your advisers. What Prduct does is hold the data, collect what is missing from the people who actually have it, score how complete it is, keep the evidence and the audit trail behind every value, and publish the passport. When the judgement has to be made – or defended – the data is there: structured, current, sourced from the party who knew it, and provable.
See where your supply chain risk actually sits.
Bring us your supplier list and your hardest regulation. In 45 minutes you'll see your own data in Prduct - not a generic demo.