Publish a Digital Product Passport

What a passport is

A Digital Product Passport is a structured record of a product: what it is made of, where it came from, how to repair it, and how to dispose of it. EU rules under ESPR are making it a requirement, product category by product category, with batteries early and textiles behind them. The QR code on the product resolves to the passport.

How it works here

1. Open DPP in your dashboard and create a passport. It starts as a draft, which is served with no-index and no-cache headers and is never treated as authoritative. Nothing is public until you publish it.
2. Fill in the product identity, including its GTIN if it has one.
3. Add materials, care and repair information, and disposal routing.
4. Publish. You get a GS1 Digital Link QR code that resolves to the passport.

Bulk work goes through CSV import and export, and every change is versioned, so you can show what the passport said on any past date. For a regulated record that audit trail is the point, not a convenience.

Verification, and what it gates

A passport declares who issued it, so we verify the issuer by email domain or a DNS record. Verification gates the claim, not your access: you can buy, create and publish immediately, but an unverified passport says so on its page and in its structured data. Nobody waits on a human, and we never publish a claim we cannot back.