---
id: KB-NO-001
url: https://app.codecontract.io/help/regulation/what-is-the-digital-product-passport
idioma: en
categoria: normativa
subcategoria: producto
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-NO-002, KB-TZ-002]
citadoPor: [KB-NO-002, KB-NO-004, KB-CS-021, KB-NO-006, KB-NO-007, KB-NO-011]
---

# What the digital product passport is

_What information it asks for, where it comes from, and why it resembles a case file._

**Responde a:** what is the digital product passport · dpp meaning · product passport ecodesign · what information does the dpp carry

The digital product passport is a set of information about a specific product — what it is made of, where it comes from, how it is repaired, how it is recycled — usually accessible by scanning a code on the product or its packaging.

## Why it resembles what you already do

Because it is the same thing under another name: information coming from third parties — your suppliers — that has to be gathered, that expires, and that someone outside will consult. The difference is who consults it: here it may be a customer, a recycler or an authority.

| What you already do | What the passport asks for |
| --- | --- |
| Request certificates from a supplier | Request composition and origin of each component |
| Mark what expires | Keep the information current while the product exists |
| Show a case file to an auditor | Let anyone consult it by scanning |

## Where the information comes from

**En corto**

- From your suppliers, for the most part.
- From your own manufacturing processes.
- And it has to be updatable: it is not a fixed snapshot.

> [!IMPORTANT]
> The rollout is being staged by product category and is not the same for everyone. When it affects you and which exact fields you will be asked for is something to confirm with your adviser or trade association: this explains how to have the information ready, not what the rule requires in your case.

> [!WARNING]
> The hard part is not publishing the passport: it is getting the data from your supplier's supplier. Starting to ask for composition and origin before it is mandatory is what separates arriving early from arriving in a rush.

> [!NOTE]
> If you sell to large customers, they will probably ask before any authority does. That is usually the first real warning.

**Does this replace labelling?**

No. It is additional information, accessible digitally.

**Do I have to publish it myself?**

It depends on your role in the chain; check.

**Can I start without knowing the exact date?**

Yes, and it is sensible: gathering composition and origin from your suppliers helps under any timetable.

## Ejemplos

**A furniture manufacturer is asked by a large customer for per-product composition data.**

- Builds a process requesting composition and origin from each supplier
- Marks the data that needs renewing

→ When the formal requirement arrives, they already hold what others are only starting to request.

**The information requested is spread across five suppliers.**

- Requests each one's part and gathers it into one file

→ What was scattered becomes consultable at once.

**Each supplier sends their data in a different format.**

- Requests specific documents to a single destination

→ What is received is comparable across suppliers.

**A figure changes and nobody knows which version was declared.**

- Keeps each version with its date

→ You can say what was declared at each moment.

**A supplier's data is missing and they do not reply.**

- Records what was requested, when, and what came back

→ The gap is documented rather than blank.

**Preparation for next year starts and nobody knows where to begin.**

- Starts by inventorying what information already exists

→ The real work turns out smaller than it looked.