How to Prepare Your Product Data for the EU DPP Registry (July 2026)

On 19 July 2026, the European Commission will launch the EU Digital Product Passport registry. It's not a pilot program, not a voluntary initiative, and not a future aspiration — it's operational infrastructure mandated by Article 12 of the Ecodesign for Sustainable Products Regulation (ESPR).

When product-specific requirements start taking effect — batteries from February 2027, iron and steel from 2027–2028, textiles shortly after — the registry is what connects each physical product to its digital passport. If your product data isn't structured, identified, and ready to submit, the passport can't exist.

This article explains what the registry actually does, what it expects from manufacturers, and what you should be doing now to prepare your product data.

What the DPP Registry Actually Does (It's Not What Most People Think)

The most common misconception about the DPP registry is that it stores your product data. It doesn't. The registry is an index, not a database.

The DPP system follows a decentralized architecture. Companies (or their certified DPP Service Providers) host the actual passport data in their own systems. The EU registry stores only the minimum needed to connect a product to its passport:

This means the registry serves three functions: it enables regulatory authorities to look up any product and find its passport, it enables customs to verify that products entering the EU have valid passports, and it creates a single reference point for the entire system. Products without a valid registry entry can be held at the border.

The practical implication for manufacturers: you don't submit your full product data to the EU. You submit identifiers, host the passport data yourself (or through a certified provider), and make sure your identifiers resolve to the right data when someone looks them up.

Unique Identifiers and Data Carriers: The Physical-Digital Bridge

Every DPP starts with a unique product identifier complying with standards listed in Annex III of the ESPR. In practice, this means GS1 GTIN (Global Trade Item Number) based on ISO/IEC 15459 — the same identifier system already used globally for product identification and barcode scanning.

The ESPR allows three granularity levels, determined per product category by delegated acts:

The identifier must be encoded in a data carrier physically present on the product, its packaging, or in accompanying documentation. QR codes are the expected primary mechanism, but NFC chips and RFID tags also qualify. The key standard here is GS1 Digital Link — a URI syntax that embeds the product identifier in a web URL. When scanned, a resolver service directs the requester to the appropriate passport data, potentially showing different information to consumers, regulators, and recyclers from the same QR code.

A standard under development by CEN/CENELEC JTC 24 will formalize which identifiers can be used within the EU DPP system. Eight harmonised standards for DPP data and interoperability are expected to be completed by 2026.

What Data Format the System Expects

The ESPR itself is technology-neutral at the regulation level — it doesn't mandate a single format in the legislation text. But Article 10 requires that DPP data must be “based on open standards, developed with an interoperable format, machine-readable, structured, searchable, and transferable through an open interoperable data exchange network without vendor lock-in.”

In practice, the emerging technical framework points clearly to:

If your product data is currently locked in PDFs and Word documents, the first step toward DPP compliance is getting it into structured format. SpecMake's JSON-LD export maps extracted product data to schema.org Product vocabulary — the same semantic framework the DPP system is being built on.

Which Products Are First

The registry goes live in July 2026, but no ESPR-based DPP requirements are mandatory on that exact date. The registry enables product-specific mandates that follow:

The 18-month rule applies: there is always a minimum 18-month transition period between a delegated act's adoption and its obligations taking effect. So even when the Commission publishes requirements for a product group, companies get preparation time. But that preparation time is much less useful if you haven't started getting your data structured.

For batteries specifically, the passport requirement is less than a year away. For construction products, the revised CPR is already in force with priority categories facing full compliance by 2028.

Five Things Every Manufacturer Should Do Now

The registry launches in four months. Product-specific deadlines follow within the next year. Here's the practical preparation sequence:

The Upstream Gap: From Documentation to Structured Data

The DPP ecosystem is filling up with platforms that store, share, and manage passport data. What none of them solve is the upstream problem: getting the data out of your existing documentation in the first place.

Most manufacturers today have product specifications in PDFs, test results in Word documents, declarations in scanned forms, and material data in spreadsheets from different departments. A DPP platform can store the finished passport beautifully — but someone has to extract, structure, and clean the data before it gets there.

This is what SpecMake is built for. The pipeline reads your existing technical documentation — PDFs, DOCX files, in any language — and produces structured, machine-readable output with every property, value, unit, and standard reference identified. The extraction engine handles complex table layouts, multi-column data, and position-aware text. The quality audit catches missing values and contradictions before they reach your passport. And the JSON-LD export maps everything to schema.org vocabulary — the same semantic framework the DPP system is being built on.

Key Dates

SpecMake transforms technical documentation into structured, DPP-ready data. Upload a spec sheet and see how the extraction, audit, and JSON-LD export work with your own documentation.