Digital Product Passport: what the rules require and who has to comply

The EU registry went live on July 20, 2026. The framework is settled, but obligations arrive one product group at a time. Here is what a passport holds, which sectors are next, and what today's dates mean for you.

Current status

Four things that changed this summer

  • The registry is live

    The European Commission launched the Digital Product Passport Registry on July 20, 2026, along with a testing environment for businesses.

  • What it does not hold

    The registry stores an identifier and a pointer to each passport. Your product data stays on your own systems or with a service provider.

  • Already binding

    The battery passport applies from February 18, 2027 under the Battery Regulation (EU) 2023/1542. It is the first mandatory DPP in the EU.

  • Standards are set

    Six core European standards were published on May 27, 2026 and cited in the Official Journal on July 15, 2026.

The Basic

A passport is a data record, not a document

A Digital Product Passport covers product identity, material composition, sustainability and circularity data, and compliance evidence. Identifiers sit at product, batch, or item level and connect to QR codes, NFC, or RFID. Different audiences see different views, so a consumer, a repairer, a recycler, and a regulator each get what applies to them. The exact fields come from each product group's delegated act.

  • 01

    Identifier

    A unique code for the product, batch, or item

  • 02

    Data carrier

    A QR code, NFC tag, or RFID chip on the product

  • 03

    Decentralized storage

    The data stays with the manufacturer or a service provider

  • 04

    Registry pointer

    The EU registry holds the identifier and a link

  • 05

    Role-based access

    Each audience sees only what applies to them

Your deadline is later than you think. Your work starts sooner.

Once a delegated act is adopted, you get a transition period of at least 18 months. That sounds generous until you look at what has to happen inside it.

  • Collecting data from suppliers is the long pole, and it does not compress
  • A registration ID only confirms that an upload succeeded. Article 13(5) is explicit that it is not proof of compliance
  • Enrolling at the organization level costs nothing today, so there is no reason to wait for a registerable product
The work ahead

Four phases, whatever your product group

  • 01

    Connect

    Bring together the product and compliance data you already hold across ERP, PLM, supplier files, and sustainability calculations

  • 02

    Check

    Determine which fields your product group requires and where data or evidence is still missing

  • 03

    Build

    Turn the verified record into a structured passport with an identifier, then attach it to a data carrier

  • 04

    Publish

    Submit the right version to the registry and to each audience, and keep it current as data changes

Most of this data already exists somewhere in your business. The job is connecting it, not collecting it again.

E-Book

Product Compliance and Digital Product Passport for Dummies

Your practical guide to the next generation of product compliance requirements. Learn how to navigate evolving regulations, improve product transparency, and prepare for the Digital Product Passport.

Frequently Asked Questions (FAQ)

osapiens hub

Explore the solution