"Digital Product Passport" can sound abstract until you see one. Strip away the regulatory language and a passport is just a structured page of data behind a QR code — but the data it has to carry is specific, and a lot of it is information most companies have never assembled in one place. Here's a field-by-field look.

The core fields

Exact requirements vary by category, but almost every passport carries a common spine:

  • Product identity — a unique identifier, typically built on a GS1 GTIN, so the passport maps to a specific product
  • Material composition — what it's made of, by share, including recycled or secondary content
  • Country of origin and key manufacturing stages
  • Durability, repairability and recyclability — how long it lasts and what happens at end of life

Environmental impact

This is the part that catches most companies out. Passports increasingly expect quantified environmental impact — carbon, water, energy and more — computed to the EU's environmental footprint method rather than estimated loosely. The EU framework defines a full set of impact indicators; in practice you start with the headline figures and the schema holds the rest.

The QR code is trivial. The verified impact data behind it is the actual work.

Almost no SME measures this directly. The realistic path is to compute it from a curated emission-factor database combined with what you do know about the product — materials, processes, origin. That's modelling, not lab testing every item.

Certifications and origin

Where you hold certifications — GOTS, OEKO-TEX, GRS and others — the passport should reflect them, with the certificate number, expiry date and who holds it (you or your supplier). Origin claims need care too: a "Made in EU" badge can only appear where the product genuinely qualifies, so any non-EU component has to flag and override it at the product level. Getting this wrong is a compliance risk in its own right.

Where the data comes from

The hardest thing about a passport isn't any single field — it's that the data lives in many places and changes over time. Composition might be in a PLM system, identifiers in a GS1 registry, supplier details on a spreadsheet, and impact figures nowhere at all. Assembling that for one product is tedious. Doing it for a whole catalogue, by hand, and keeping it current, is not realistic.

That's the problem Luxima exists to solve. It pulls from the systems and spreadsheets you already use, computes and fills the data you can't measure, validates everything against the rules for your category, and publishes a complete passport on your own domain — then keeps it up to date as your products change. The passport stops being a project and becomes something that simply runs.