Technology
·
November 19, 2026

How Is Digital Product Passport Data Authenticated?

Martina Sattanino
Content Writer
MONOBI garment with an embedded RFID label for connected product data

A Digital Product Passport is created by the economic operator responsible under the applicable legislation and may later be updated by other authorised actors throughout the product’s lifecycle.

The manufacturer or other responsible economic operator may create the original passport. A professional repairer, refurbisher or recycler may later be permitted to add information relevant to a repair, remanufacturing or end-of-life activity.

This requires a DPP system to establish who is performing each action, whether that actor is authorised to perform it and whether the resulting record has subsequently been altered. The ESPR requires the actors allowed to create or update a passport, the data they may introduce and their access rights to be specified at product-group level. It also requires data authentication, reliability and integrity to be ensured.

The European standard EN 18246:2026 – Digital Product Passport – Data authentication, reliability and integrity provides the technical foundation for authenticating data contributors and protecting the integrity of their contributions throughout the passport’s lifecycle.

‍

What does DPP data authentication mean?

In a Digital Product Passport, authentication establishes the identity of the actor performing an action on controlled passport data. That action may involve:

  • creating the original passport or its initial dataset;
  • adding new information permitted for the actor’s role;
  • modifying or correcting existing information;
  • recording a repair, refurbishment or other lifecycle event;
  • deleting or superseding a record where this is permitted.

Authentication and authorisation are closely connected, but they are not the same. Authentication establishes who the actor is. Authorisation determines what that authenticated actor is permitted to do.

A manufacturer may be authorised to create the original DPP and manage core product information. A repair provider may be allowed to add a repair event without changing the manufacturer’s original composition data. A recycler may contribute end-of-life information without receiving access to commercially sensitive records.

Integrity addresses a further question: whether information attributed to an authenticated actor has remained unchanged, or whether any subsequent modification can be detected and traced. None of these controls automatically establishes that the information entered is factually correct. Validation and substantiation are separate processes.

‍

How EN 18246 supports DPP data authentication and integrity

EN 18246 establishes technical mechanisms for identifying actors that contribute controlled DPP data and for connecting their actions with the resulting records.

This is particularly relevant in a multi-actor environment. The organisation that creates the passport may not be the only party permitted to contribute information during the product’s lifetime. The standard supports:

  • authentication of actors creating, modifying or deleting controlled DPP data;
  • attribution of each action to the responsible authenticated actor;
  • detection of subsequent or unauthorised alterations;
  • integrity-protected and traceable records of changes;
  • exchange of authenticated information across interoperable systems.

The standard requires actors providing controlled DPP data to be authenticated through mechanisms that demonstrate control of a digital certificate issued following an identity-proofing process. Once an actor has been authenticated, the DPP system can apply the relevant authorisation rules to determine which data that actor may introduce or update. Under the ESPR, those rights will be specified in the applicable product-specific delegated act.

One mechanism described by the standard is the secure electronically signed data construct, or ESDC. It allows structured information to carry electronic proof of the actor associated with it and enables subsequent alterations to be detected without requiring every participant to use the same underlying software.

EN 18246 does not prescribe the complete architecture of a Digital Product Passport. DPP use cases, secure elements embedded in data carriers and cryptographic protection of unique product identifiers remain outside its scope.

As of November 2026, EN 18246 has been published as a European standard, but its reference has not yet been cited in the Official Journal of the European Union. It can already inform implementation decisions, although it does not yet provide the presumption of conformity associated with the six DPP standards already cited under the ESPR.

See how the eight European Digital Product Passport standards fit together.

‍

Who can create or update a Digital Product Passport?

Under the ESPR, the applicable product-specific delegated act will define the actors that may create a Digital Product Passport or update its data, the information they may introduce and the detailed arrangements for doing so.

The original passport will generally be created by the economic operator responsible for placing the product on the EU market, such as the manufacturer or, in relevant cases, the importer. Suppliers may be required to provide information to that operator, but this does not mean that every supplier writes directly to the passport. Later in the product lifecycle, additional actors may be permitted to contribute specific information, including:

  • professional repairers recording interventions or replaced components;
  • refurbishers or remanufacturers documenting changes made to a product;
  • resale operators adding a permitted ownership or condition event;
  • recyclers or waste operators adding end-of-life information;
  • other actors expressly identified in the applicable legislation.
  • Each actor must be authenticated before its contribution can be attributed to it.
  • Its authorisation must then limit it to the actions and data assigned to its role.

Contributing to a passport should not give an actor unrestricted control over the complete product record. A repairer, for example, may add a repair event without being allowed to change the information originally provided by the responsible economic operator.

The exact actors, permissions and update procedures will depend on the applicable product-specific delegated act. Until those requirements are adopted, companies should design role-based processes that can accommodate different access and update rights.

Authentication enables the system to identify the actor behind each action. It does not independently decide whether that actor should have permission to perform it; this requires clearly defined authorisation rules.

‍

What happens when DPP data changes?

A Digital Product Passport is not a static record. Information may need to be corrected, expanded or updated as the product moves through its lifecycle.

EN 18246 connects the creation, modification and deletion of controlled DPP data with the authenticated actor responsible for the action. Integrity-protected logs can then preserve a traceable record of what occurred.

A DPP system should therefore be able to establish:

  • who performed the action;
  • when the action occurred;
  • which information was created, modified or deleted;
  • whether the resulting record was subsequently altered;
  • whether the actor was authorised to make it;
  • whether previous versions and changes can be traced.

This is particularly important when multiple organisations contribute information. A repairer may add a lifecycle event without being authorised to change the manufacturer’s original material data. A recycler may contribute end-of-life information without receiving access to unrelated or restricted parts of the passport. Authentication must therefore work together with clearly defined access and update rights.

Maintaining only the latest visible value is not sufficient when the history of the information affects compliance, accountability or downstream use.

‍

Does authentication prove that DPP information is correct?

No. Authentication does not independently verify that the underlying product information is factually correct.

Authentication can establish the identity associated with a data contribution. A digital signature or seal can demonstrate which actor is associated with the information and whether it has been altered since it was signed. An audit trail can show when and by whom it was updated.

These controls do not independently demonstrate that:

  • a supplier declaration is accurate;
  • a calculation used the correct methodology;
  • a certificate remains valid;
  • a test applies to the specific product;
  • an environmental claim satisfies the applicable legal requirements.

EN 18246 can help establish who created or modified controlled DPP data and whether it has subsequently been altered, but it does not determine whether the underlying information or product claim is factually correct.

Authentication concerns the identity behind the action. Validation and substantiation concern the quality and factual support of the information itself. Companies need separate governance processes for assessing declarations, certificates, test results and other supporting evidence.

‍

What companies should require from a DPP system

Companies should define authentication and authorisation rules before allowing multiple organisations to contribute to a Digital Product Passport.

For each type of actor, companies should establish:

  • how its identity will be authenticated;
  • which passport data it may access;
  • which information it may create or update;
  • whether it may correct, delete or supersede previous entries;
  • how its actions will be logged and protected against undetected alteration;
  • what happens when its authorisation expires or is revoked.

Questions for DPP providers should include:

  • Which identity-proofing and actor-authentication mechanisms are supported?
  • Can permissions be assigned according to role, action and data type?
  • Are creation, modification and deletion events attributed to authenticated actors?
  • Can lifecycle contributors add permitted information without changing the original product record?

These controls should apply both when the passport is first created and when authorised actors contribute information later in the product lifecycle. Authentication mechanisms should also remain interoperable: a company must be able to preserve actor attribution, permissions and modification history when integrating another system or changing its DPP provider.

‍

Maintaining control throughout the DPP lifecycle

A Digital Product Passport may remain active long after the product has been placed on the market. Over time, different actors may need to record repairs, replacements, refurbishment or end-of-life activities.

The system must therefore do more than identify who created the original passport. It must authenticate future contributors, apply the appropriate permissions and preserve an integrity-protected record of relevant changes.

EN 18246 provides a common technical foundation for this process. It does not validate whether each contribution is factually correct, but it helps ensure that actions can be attributed to authenticated actors and that unauthorised changes can be detected.

Renoon supports companies in defining DPP roles, permissions and lifecycle processes, connecting product information across organisations while maintaining control over who can create and update each part of the passport.

Speak with our team about implementing a controlled Digital Product Passport infrastructure.

Where would you
like to start?