Digital Product Passports
Build ESPR-aligned passports, publish them to a public page with QR / Digital Link, and register them with an EU registry.
A Digital Product Passport (DPP) is the EU ESPR-aligned record of a product's sustainability and compliance data, resolvable by anyone with the product's identifier. PIE builds passports from your existing product data and publishes them to a public, snapshotted page.
The passport data model
A passport projects an allowlisted subset of a published product's attributes and linked entities into the ESPR data model. Only allowlisted, published data can reach the passport — nothing private is exposed. The passport is snapshotted at publish, so the public page reflects exactly what you published, not later drafts.
Publishing a passport
Publish a passport from a published product. PIE generates:
- A public passport page served under a dedicated public database role that can read only published passports (row-level security plus an allowlist projection).
- A GS1 Digital Link and QR code so the passport resolves from the product's GTIN.
The public resolver (/public/resolve) turns a Digital Link into the passport page.
Registry credentials
Passports can be registered with an EU DPP registry. Registry integration runs per organisation with encrypted credentials: you store your registry credentials once (encrypted at rest), and a background worker resolves them when registering. The registry client supports disabled, mock, and live modes, and records the outcome (registered, skipped, or the credential source used) so you can audit what was submitted.
A note on food passports
Publishing a food DPP requires the mandatory material / origin entity types to be present. If those entity types are not seeded in your environment, a food passport may be un-publishable out of the box — link the required entities first. See the Products guide for reference entities.
Related
- GS1 & GDSN — the identifiers and readiness a passport builds on.
- DPP / ESPR concept — the regulatory background.