Guides

A DPP is not a QR code

Many conversations about digital product passports start in the wrong place: “Which QR should we print?” The label is visible. The preparation is much larger than creating a code.

Updated 21 August 2026~7 minute read

Many conversations about digital product passports start in the wrong place: “Which QR should we print?” That is understandable – the label is visible. But the preparation is much larger than creating a code.

Three layers that often get mixed up

  1. Data carrier – QR, NFC, a link or another identifier on the product or pack
  2. The product passport – the structured dataset and how it is presented
  3. The data foundation – master data, documentation, supplier data and the processes that keep it true over time
Without layer 3, layers 1–2 quickly become a neat façade with outdated or incomplete information.

Where the real work sits

At Original Creation we see the same pattern with manufacturers:

  • Scattered data in business systems, spreadsheets, PDFs and email
  • Unclear ownership between purchasing, engineering, quality, production and sustainability
  • Maintenance over time – products, materials and suppliers change; the passport has to follow

What happens if you start with the QR

  • You publish links before the data model is ready
  • Every product variant becomes a manual exception
  • Supplier changes do not show up in the passport
  • Compliance becomes a project that has to be redone at every range update

A better order

  1. Requirements and scope for your product group
  2. Mapping and gaps (the checklist)
  3. Data model + ownership
  4. First passports for a pilot line
  5. Then the carrier/QR in production and on the pack

In short

The QR code is visible. The DPP value sits in the right data, the right process and ongoing maintenance. Start there – otherwise you are only buying a label.

See how OC automates the data foundation