The Digital Product Passport Does Not Have to Be a Burden

What this is about

On 19 July 2026 the central EU register for the Digital Product Passport goes live. From 18 February 2027, no traction battery above 2 kWh may be sold in Europe without a DPP. Textile follows, furniture follows, steel follows, electronics follows, tyres follow, construction products follow on a rolling timeline through 2032.

Most mid-sized manufacturers we speak to know this. They also know they are affected. What they do not know is: how does the data get to where it needs to go without the company standing still for three quarters.

That is exactly what this piece is about.

The pain points nobody likes to talk about

First: the data is in the house, but not together.

The material proof sits with procurement. Energy consumption sits in production. Repair history sits with service. The recycling concept — if it even exists yet — sits with an external consultant. The CO₂ balance gets calculated once a year for the annual report, not per batch, not per serial number.

The DPP requires: per product, per batch, per serial number. End to end.

Second: the ESPR mandatory fields are a moving target.

The delegated acts for battery, textile and steel differ. The mandatory fields for a winding machine in textile differ from those for a lithium pack at an automotive supplier. Anyone buying a DPP solution today that only does battery rebuilds half of it once the textile obligations kick in in 2027.

Third: most DPP vendors sell an island.

They collect the DPP data and write it into the register. What they do not do: they do not talk to the bookkeeping that posts incoming goods. They do not talk to the logistics that writes the eFTI freight documents. They do not talk to the sales people who took the order.

The result is absurd: the DPP solution asks the employee again for data the company has long had — just in other systems. The mid-sized manufacturer pays for a tool whose main job is to find data that already belongs to it.

Fourth: the audit question.

When a market surveillance authority shows up in 2028 and asks for the product passport for batch B-2027-118, having the data is not enough. It must be provable that this data was present at the time the product entered the market — not tidied up retroactively. Plain database entries without tamper resistance fail in any serious audit.

Fifth: the update obligation.

The DPP is not “set up once, done”. Repairs, component swaps, ownership changes, recycling certificates — the passport lives with the product, often fifteen, twenty years. Anyone maintaining that by hand builds up an original sin that catches them by year three.

What HEINI does differently

HEINI is not a DPP tool that you stand next to your ERP, next to your bookkeeping, next to your logistics. HEINI is the layer that connects all three — and the DPP is one of many disciplines running on this layer.

Concretely that means five things.

One: the data comes from the sources where it arises anyway.

When procurement uploads a material proof to the supplier portal, it lands in the DPP. When production closes a batch, the energy consumption lands in the DPP. When service documents a repair, it lands in the DPP. Nobody fills anything out twice. Susi, the digital receptionist, asks back directly in the Slack channel when in doubt — in normal language, not in forms.

Two: HEINI maintains the ESPR mandatory fields, not the customer.

When the EU adjusts the battery mandatory fields in Q3 2026, nothing changes for the customer. When the textile delegated act arrives in 2027, nothing changes for the customer. HEINI keeps the fields current; the customer keeps delivering the same data from the same sources. That is the difference between software that grows with the law and software that needs an expensive adjustment every eighteen months.

Three: the audit proof is built in, not bought separately.

Every DPP entry receives a tamper-resistant time stamp at the moment it is created — a cryptographic anchor that cannot be deleted or altered after the fact. When someone asks in 2028 whether batch B-2027-118 was really produced on 14 November 2027 with this recyclate share, the answer is technical, not a matter of trust. That is exactly what market surveillance and auditors will expect from DPP data in the coming years.

Four: the passport lives with the product.

Repairs, component swaps, ownership changes — all run through the same layer. HEINI appends the new records to the existing passport without overwriting the old data. If a customer wants to know fifteen years after sale who swapped the battery pack in 2031 — the answer is in the passport.

Five: circular economy is built in, not extra.

The DPP is the EU’s answer to the recycling problem. But the truly interesting use cases only emerge once the data can flow: repair acceptances checked in seconds instead of hours. Recyclate shares that procurement can see live for the next order. Warranty extensions that apply automatically because the passport proves the device was correctly maintained. HEINI makes these enrichments automatic — the mid-sized manufacturer does not have to commission any programming.

What this means in money

Anyone buying the DPP as a stand-alone product pays three times: once for the DPP vendor, once for the interface to the ERP, once for the audit-ready archive. When the eFTI freight-document obligation kicks in in 2027, a fourth bill arrives. When the next industry joins in 2028, a fifth.

Whoever has HEINI pays once — for the layer, not for the discipline. The DPP is in. The freight document is in. The bookkeeping connection is in. The audit trail is in.

This is not a marketing promise, it is architecture. A layer that carries all disciplines costs less than five islands that don’t know each other. More on the layer logic in the trust-stack piece.

What to do now

Whoever is hit by the battery obligation in 2027 has until February 2027. That sounds long. It is not long. Cleanly merging data flows from three or four systems — including supplier portal, including audit anchor, including ESPR mandatory-field mapping — takes six to nine months in practice. Anyone starting in spring 2027 will miss the deadline.

See pricing for the four plans (Basis, Finanzen, Betrieb, Enterprise). Anyone who starts now has a settled layer in the house by the DPP go-live — not a project that is just starting.

The DPP will arrive whether one is ready or not. With the right layer behind you it is not a burden. It is an opportunity to finally organise your own data the way it should have been organised all along.

About HEINI HEINI is the digital layer for the German mid-market. Configuration, bill of materials, product passport, manufacturing, delivery — end to end, in an architecture that grows with European law. More on security and enterprise. Operator: HEINI, Münster.

Sources