twelve weeks. That’s the window between today (April 28, 2026) and July 19, 2026, when the EU Central Digital Product Passport Registry is expected to go live. It is the date most product directors I talk to have not put on the roadmap, because the conversation about DPP has been dominated by the textile delegated act, the battery passport, and ESPR working plans. The registry doesn’t make headlines. It just quietly rewires how customs and market surveillance authorities verify what you sell into the EU.

Look, the battery passport already became mandatory in January 2026. The textile delegated act was finalized January 2025. CEN/CENELEC just published the 8 harmonized DPP standards in March 2026. The pieces are clicking into place faster than most PIM teams budgeted for. And the registry is the keystone: when it flips, your products either show up in it or they don’t. Customs systems will be querying it by the end of 2026.

Most PIM stacks today cannot register products into the registry. Most teams have no clear owner for “DPP registration” as a workflow. And most CFOs have been told DPP is a 2027/2028 problem. They are about to find out it has a July 2026 dependency.

What the EU Central DPP Registry Actually Is

Cut through the regulatory language and the registry is three things at once.

First, it is an authoritative product index. Every DPP-covered product placed on the EU market needs a unique identifier registered centrally before it can be sold. That identifier links to the product passport hosted by the manufacturer, brand, or appointed economic operator. Think of it as the EU equivalent of a domain registry: the registry doesn’t host the content, but without an entry, your “site” doesn’t exist as far as the system is concerned.

Second, it is a customs enforcement tool. Customs authorities at EU borders will query the registry to verify that a product entering the market has a valid passport. This is the part most PIM and supply chain teams underestimate. Currently, customs checks are slow, paper-based, and reactive. The registry shifts customs to API-first, real-time verification. Products that fail the lookup get flagged, held, or returned. This is not theoretical. The European Commission has explicitly confirmed no grace period for textile and electronics DPP deadlines, and the registry is the operational mechanism that makes that enforcement real.

Third, it is a data interoperability layer. The registry uses the CEN/CENELEC harmonized DPP standards for data carriers, APIs, and security. That means every PIM, ERP, or downstream system that wants to register a product has to speak the standard. If your current PIM was built before the standards published in March 2026, you are looking at integration work, not a config change.

The registry doesn’t replace your PIM. It sits downstream of it. But it imposes hard schema and identifier requirements upstream of customs, and that pulls the requirement back into your product data architecture.

Why July 2026 Matters Even If Your DPP Deadline Is 2028

The textile DPP delegated act applies roughly 18 months after publication. The textile compliance deadline is late 2028 / early 2029. Furniture, construction, and tyres land in 2028. So why am I writing about July 2026?

Three reasons that come up in every CFO conversation we have at LemonMind right now.

Battery passports are live. As of January 2026, every EV battery and industrial battery over 2 kWh placed on the EU market needs a passport. For automotive OEMs, energy storage manufacturers, and anyone who ships e-mobility products, the registry going live in July is not a future problem. It is the production system that will route their already-mandatory data into customs verification. Battery teams need their registry integration working in Q3, not Q4.

Multi-category catalogs cross deadlines. A typical mid-market e-commerce or industrial catalog touches 3-5 ESPR product categories. If you sell home furnishings (textiles 2028 + furniture 2028), bicycles (tyres 2028 + LMT batteries 2027), or construction products (construction 2028 + iron/steel 2026), your effective compliance deadline is the earliest one. Plan for the registry as if you are in scope today, because at least one of your product lines probably is.

Voluntary listing pre-deadline is leverage. The registry will accept voluntary submissions before mandatory deadlines for each category. Brands that register early get two things: a head start on customs API integration testing, and a B2B differentiator. We are already seeing tier-1 retailers in DACH ask suppliers, “are you in the registry?” as a procurement question. That is faster than the regulator and matters for revenue.

So the registry isn’t a 2028 problem. It is a Q3 2026 readiness problem, with revenue implications in 2027.

The Five Data Requirements Most PIMs Are Not Ready For

Across 70+ PIM implementations at LemonMind, we have run a registry-readiness audit on 23 client catalogs in the past 60 days. The honest scorecard breaks like this.

RequirementWhat it meansAverage readiness across 23 audits
Persistent unique product identifierGS1 Digital Link, GTIN, or equivalent that survives variant changes47 percent ready
Structured material compositionPer-component, per-substance, per-percentage breakdown18 percent ready
Verified supplier provenanceTier-1 supplier identity for every component, cryptographically signed where applicable9 percent ready
Repair and end-of-life metadataSpare parts availability, repair scores, recyclability fields12 percent ready
Multi-language compliance textDPP fields translated and locked to regulator-approved terminology in 24 EU languages31 percent ready

Average across all five requirements: 23 percent ready. That is the gap between today’s PIM state and the registry’s expected schema. Closing it costs roughly EUR 14,000 to EUR 22,000 per 1,000 SKUs in our benchmark, depending on category complexity and supplier responsiveness. If you have 50,000 SKUs and you are at the 23 percent baseline, that is a EUR 700K to EUR 1.1M project, mostly in supplier data acquisition and validation.

The painful part: most of that cost lives upstream of your PIM. It lives in the supplier portal, the email thread, the WeTransfer ZIP, the legacy ERP that doesn’t track materials at all. PIM vendors keep adding DPP modules and AI translation features, and they are useful at the last mile. They don’t help you call your supplier to find out the origin and percentage of recycled content in a zipper, which is a textile DPP data field.

What Registry-Readiness Actually Looks Like

Most CTOs ask the same question when we run this audit: “do we just buy a DPP module from our PIM vendor?” The honest answer in April 2026 is more nuanced.

The PIM vendor DPP modules (Akeneo, Pimcore, Salsify, Inriver) work well for the outbound side of DPP: storing the data, formatting it for the QR code or NFC tag, exposing the consumer-facing passport view, sometimes even managing translations. They are getting better fast.

What they don’t solve is the inbound side: getting verified, structured, multi-tier supplier data into the PIM in the first place. And that is where 60-70 percent of the registry-readiness cost actually lives, based on our audits.

Registry-readiness in 2026 means three workstreams running in parallel.

Workstream A: Identifier strategy. Pick GS1 Digital Link, GTIN, or a category-specific identifier. Make sure it persists across SKU changes, product variant updates, and supplier substitutions. Build it into your PIM master data model. Estimated effort: 4-6 weeks for a clean implementation, 3-6 months if your current SKU structure is messy.

Workstream B: Supplier data layer. Build or buy an intake layer that ingests supplier data in any format (PDF datasheets, ERP exports, supplier portal CSVs, email attachments), maps to the DPP-required schema, validates completeness, and pushes to PIM. This is where we built OpenProd.io as PIM-agnostic intake. The math: cutting per-1,000-SKU onboarding cost from EUR 14K to under EUR 1K with AI-driven mapping and supplier portal automation. For a 50K SKU catalog facing a 2027/2028 deadline, that’s the difference between a 2-FTE project and a 12-FTE project.

Workstream C: Registry API integration. Once the CEN/CENELEC standards and the registry API spec are stable (expected Q2 2026 for the API), build the integration to register products, update them on change, and handle the verification callbacks from customs. This is real engineering work, not a checkbox. Plan for 8-12 weeks once the spec is published.

Workstream A is the easiest. Workstream C is well-scoped engineering. Workstream B is the bottleneck, and it is also the workstream that pays back beyond DPP, because it solves the same supplier intake problem that already costs you EUR 14K per 1,000 products in operational overhead.

Where the PIM Market Splits in 2026 on DPP

Two camps are emerging, and they look like the agentic PIM split I wrote about last week.

Camp A: PIM vendors layering DPP modules on top of existing platforms. Akeneo announced DPP capabilities in Spring 2026. Pimcore has DPP-aligned data structures plus the Agent SDK for automation. Salsify added a DPP framework in 2025. These work if your data is already in the PIM and largely complete.

Camp B: Specialized DPP platforms. PassportCraft, EON, Caruma, Fluxy.One. These are DPP-first platforms that integrate with your PIM but own the registration workflow, the QR code, and the consumer-facing passport. They tend to be stronger on the regulatory side and weaker on the upstream supplier data side.

Honestly, neither camp solves the supplier intake problem at scale. That is structurally upstream of both, and it is why we positioned OpenProd.io as the PIM-agnostic ingest layer. We feed Akeneo, Pimcore, Ergonode, or a custom schema. We feed the DPP platforms too, when clients run them in parallel. The supplier chaos is the same regardless of what you registered with on the regulatory end.

This is also why 2026 budget conversations are getting interesting. CFOs who used to fund “the PIM project” are now funding three things: the PIM, the DPP platform or module, and the intake layer. The intake layer is the new line item, and it is the one that determines whether the other two actually deliver value.

What to Do This Quarter If You Are a CTO Reading This

Three concrete moves, in order.

One. Run the registry-readiness audit. Pick 50 representative SKUs across your top categories. Score them against the five data requirements above. The number you get tells you whether you have a 6-month problem or a 24-month problem. Use the OpenProd.io PIM ROI calculator to translate that into a euro figure your CFO can budget against.

Two. Designate a registry owner. This is not a job for compliance, IT, or product alone. It is cross-functional. The fastest-moving clients we work with have appointed a “DPP product manager” reporting to the COO or CTO, with authority over PIM, supplier portal, and customs integration. Without a single owner, registration drifts.

Three. Don’t wait for vendor RFPs to start the supplier data work. Even if you haven’t picked a DPP platform, you can start collecting structured supplier data today. Material composition, supplier provenance, repair metadata - all of these are DPP-agnostic in the early phase. The data you collect now in a clean schema feeds whatever platform you eventually pick. The data you skip costs 7x to recover after the deadline hits.

Last point. The registry going live in July 2026 is a real date with real consequences. Battery teams already know this. Textile and electronics teams have a delegated act that doesn’t move. Furniture and construction teams have a 2028 deadline that nobody at the Commission is going to extend. The compliance window opened months ago. The question this quarter isn’t whether DPP affects you. It is whether your PIM and intake architecture can register products into the EU system before customs starts asking.

That’s our job. We think it should be a budgeted job for any catalog with EU exposure this year.

Sources and Further Reading