DPP Designer

6 min read

Who’s at the helm of the Digital Product Passport? A guide to choosing a DPP owner within your company

The Digital Product Passport cuts across product, quality, IT, sustainability, and supply chain functions. Who should lead it within a company?

by Corrado Facchini, CTO & Innovation Manager

In this article

Perché il DPP ha bisogno di un "proprietario"

The Digital Product Passport (DPP) was created with Regulation (EU) 2024/1781 on the eco-design of sustainable products (ESPR), which came into force on 18 July 2024. It is a digital file associated with a product, a batch or a model, which can be consulted via a data carrier, usually a QR code, which collects information on composition, materials, recycled content, substances, reparability and end of life.

On paper it looks like a labeling project. Nella pratica è un progetto trasversale che tocca quasi ogni funzione aziendale:

  • chi progetta il prodotto conosce materiali e componenti;
  • chi gestisce la qualità custodisce certificazioni e dichiarazioni di conformità;
  • chi si occupa di sostenibilità misura impatti e redige la rendicontazione ESG;
  • l'IT governa ERP, PLM, siti web e integrazioni;
  • gli acquisti dialogano con i fornitori, da cui arriva gran parte dei dati.

Proprio perché coinvolge tutti, il rischio è che non sia di nessuno. For this reason, the DPP Designer guide poses an organizational question rather than a technical one as the key question of the "Company" area: who is responsible for the DPP project?

La responsabilità legale è chiara, quella interna no

The ESPR leaves no doubt about who is responsible externally: the primary responsibility for the creation of the passport and the correctness of the data falls on the economic operator who places the product on the EU market or puts it into service. È questo soggetto che deve registrare il passaporto nel registro europeo previsto dall'articolo 13 del regolamento.

Il registro è operativo da luglio 2026 e le regole di funzionamento sono state definite con il Regolamento di esecuzione (UE) 2026/1778. Un elemento spesso sottovalutato: prima di registrare un passaporto, l'operatore deve completare una verifica della propria identità. Da quel momento diventa l'interlocutore delle autorità, anche quando il dato contestato proviene da un fornitore.

La norma, però, parla all'azienda nel suo insieme. Non dice quale ufficio debba coordinare il lavoro. Questa scelta resta interna e incide direttamente su tempi, qualità dei dati e costi.

The five possible answers

The guide identifies five scenarios. Nessuno è giusto in assoluto: conta il punto di partenza dell'azienda.

1. Sustainability / ESG

Chi è: il team che già redige il report di sostenibilità.

Strengths

  • Conosce metriche ambientali, impronta di carbonio, LCA e rendicontazione.
  • Ha familiarità con la raccolta di dati da fornitori e filiera.
  • Ha già una visione d'insieme degli obblighi normativi green (CSRD, dichiarazioni ambientali).

Limitations

  • Spesso è una funzione piccola, con poca leva su IT e produzione.
  • There is a risk of treating the DPP as an annual reporting exercise, while the passport is living data, linked to the individual product and to be updated over time.

Quando funziona: in aziende dove la sostenibilità ha un mandato forte del vertice e budget dedicato.

2. Quality and compliance

Chi è: l'ufficio che prepara il fascicolo tecnico e le dichiarazioni di conformità.

Strengths

  • È abituato a ragionare per requisiti normativi, evidenze documentali e audit.
  • Gestisce già certificazioni, marcature e rapporti con enti terzi.
  • Ha la cultura della tracciabilità e della responsabilità legale, coerente con la logica ESPR.

Limitations

  • Può avere un approccio molto difensivo ("il minimo per essere conformi"), perdendo il valore commerciale e di filiera del passaporto.
  • Non sempre ha competenze sui dati ambientali o sulle architetture digitali.

When it works: In heavily regulated industries, such as batteries or construction products, where the passport builds on existing obligations.

3. IT / information systems

Chi è: il team che gestisce ERP, PLM e sito web.

Strengths

  • Il DPP è, alla fine, un sistema di dati: identificativi univoci, interoperabilità, formati, accessi, conservazione nel tempo.
  • L'IT conosce le fonti dei dati e sa come integrarle.
  • È la funzione giusta per scegliere eventuali fornitori di servizi DPP e piattaforme.

Limitations

  • Rischia di costruire un'infrastruttura impeccabile ma vuota, senza sapere quali dati servono davvero e perché.
  • Il contenuto del passaporto (cosa dichiarare, con quale affidabilità) non è una competenza IT.

Quando funziona: in aziende con dati di prodotto già strutturati e un'IT abituata a lavorare per progetti di business.

4. Product / R&D

Who they are: The technical department or the Research & Development (R&D) team.

Strengths

  • Possesses deep knowledge of bills of materials (BOMs), materials, components, and design choices.
  • Serves as the natural hub where ecodesign—the core of the ESPR (Ecodesign for Sustainable Products Regulation)—can be transformed into a competitive advantage.
  • Can leverage the Digital Product Passport (DPP) to drive repairability, durability, and recyclability.

Limitations

  • Often fully occupied with new product development, leaving the DPP at risk of becoming a secondary, lower-priority task.
  • Tends to be strong on technical data, but less focused on supply chain, compliance, and sustainability-related information.

When it works best: In companies that handle their own manufacturing, and where the technical department already plays a central role in material selection.

5. Not yet defined

This is the most honest answer for many businesses, especially SMEs. The guidance is clear: identifying a person in charge is one of the first recommended steps. Without a designated point of contact, different departments end up waiting on one another, suppliers receive inconsistent requests, and deadlines arrive before the company is prepared.

Beyond choosing a department: how to build governance

Regardless of which area is selected, the "DPP owner" cannot work in isolation. Here are some best practices:

  1. Appoint an individual, not just a department. You need a specific person—by name—with dedicated time and a formal mandate from management.
  2. Establish a cross-functional working group. Include representatives from product development, quality, sustainability, IT, and procurement, with regular meetings.
  3. Map the data and its "owners." For every piece of information included in the passport, you must know who generates it, where it is stored, who validates it, and how frequently it needs to be updated. 4. Involve suppliers early on. Information regarding the origin of materials, the percentage of recycled content, and measured performance metrics is often provided by third parties—yet the company itself remains directly accountable for this data. Contractual agreements and data exchange formats must be established in advance.
  4. Define the scope of the passport. Whether it applies to a product model, a specific batch, or an individual item—a decision that will depend on the delegated acts for each product category—will fundamentally alter the complexity and costs of the project.
  5. Plan according to industry deadlines. The Digital Product Passport is not yet mandatory for all products. Industrial batteries (exceeding 2 kWh), electric vehicle batteries, and batteries for light means of transport will lead the way starting in February 2027; other sectors—such as textiles, furniture, and steel—will follow, in line with the European Commission’s work plan.

A hybrid model is often the best approach

In practice, leading companies tend to adopt a mixed model: a "content-focused" function (covering sustainability, quality, or R&D, depending on the sector) working alongside an IT technical lead responsible for the infrastructure, with a management sponsor to resolve any conflicts regarding priorities.

The specific departmental label matters less than three key requirements: a clear mandate, access to data, and the ability to foster collaboration between functions that typically operate in silos.

Conclusion

The Digital Product Passport is not a task that can be left until the last minute. It is a project that encompasses data management, supply chain oversight, and regulatory compliance. While the question "Who is responsible for this?" may seem simple, the answer determines the quality of everything that follows. If your company’s current answer is "not yet defined," then your first step is to make that decision.

Sources

  1. DPP Designer – Who is responsible for the DPP project within a company?
  2. EUR-Lex – Regulation (EU) 2024/1781

← All articles

Choose which cookie categories to allow. You can change your mind at any time from the «Cookie preferences» link at the bottom of the page.

Cookie preferences
Always on

Needed for the site to work: signing in, resuming your project, language, theme and storing your choices. They cannot be turned off.

Help us understand, in aggregate, how the site is used so we can improve it.

Allow us to show you content and communications matching your interests, including on other sites.

No services active at the moment.

Cookie policy