“How much does a DPP system actually cost?” is the most common question among buyers. The second most common: “What if we do not do it?” Both questions belong together. Here is a cost view of both sides: the platform subscription and the penalties.
What a DPP costs - the three axes
Concrete amounts depend on the provider, the depth of integration and the product portfolio - they can only be quantified seriously on a case-by-case basis. What can be generalised are the three axes on which DPP platforms price:
- one-off set-up - configuration, integration, data migration. Scales with the depth of integration: a self-service start at the low end, a deep ERP integration in a group at the high end.
- ongoing platform fee - depending on the provider, per product, per scan or as a flat rate. Transpareo works with a flat rate; this makes the costs calculable independently of scan volume.
- data quality and content - translation, LCA calculations, certificate management. Often the underestimated item, because it recurs every year. At Transpareo the AI translation into 39 languages (all 24 official EU languages included) is already part of the plan.
At Transpareo there are no set-up costs: you set up the platform yourself, without consulting hours. The transparent plans on the registration page show the current prices - the only figures in this article, because they are the only ones we can vouch for.
What a breach costs - the mechanics
The ESPR (Reg. 2024/1781) leaves the level of penalties to the member states and requires in Article 74: “effective, proportionate, dissuasive”. The national implementations are in some cases still at the draft stage; concrete fine levels are therefore not yet fixed. The mechanics are emerging, however:
- fines per breach, in individual drafts also revenue-related where there is intent
- placing-on-the-market ban: affected products may not be sold on until the breach is remedied
- recall of non-compliant products
- publication obligation for the breach in individual countries - the reputational damage comes for free
France flanks this with the AGEC law, which knows revenue-related penalties where there is commercial benefit from a breach. The EU Batteries Regulation is, from experience, sharper: the German implementation in the BattDG provides for fines and recall orders by the BAuA.
The real damage: the placing-on-the-market ban
The fine is the painful but manageable problem. The placing-on-the-market ban is the existential one:
- a delivery arrives at the Hamburg customs yard, is inspected, has no valid DPP
- the goods stay put in the free warehouse
- for perishable goods: worthless after a few days
- for capital goods: massive storage costs plus loss of reputation with the customer
- the correction (a subsequently filed DPP plus re-inspection) typically costs 10 to 60 working days
For a batch of EV batteries that may not be moved for weeks, interest and storage costs, reputational damage and contractual penalties at the OEM quickly exceed the actual fine by a multiple.
This is not a hypothetical scenario. Analogous cases from REACH enforcement show: companies have lost considerably more through customs stops than through fines.
Who actually inspects?
A common misconception: “We are too small, nobody inspects us.” The EU has systematically strengthened market surveillance in recent years:
- customs authorities inspect imports on a sampling basis - a QR-code scan at the port
- market-surveillance authorities of the countries carry out risk-based inspections
- the ECHA Enforcement Forum coordinates EU-wide inspection campaigns
- consumer-protection associations have become alert to DPP gaps
On top of this comes privately driven inspection: Amazon, Zalando and Otto have for years checked the sustainability and compliance data of their suppliers. Anyone who does not deliver the data is hidden from assortments - without an authority becoming active.
Planned vs. reactive - the calculation without numbers
Even without price tags the calculation can be made, because the items differ structurally:
Scenario A: setting up the DPP in a planned way
- set-up once, at your own pace, without a rush surcharge
- ongoing platform and data-maintenance costs, calculable and budgetable
- the team gets to know the system in normal operation, not in a crisis
Scenario B: a delayed, reactive introduction
- a fine event plus the procedural costs around it
- a customs stop with goods standing still, storage costs and annoyed buyers
- the same DPP introduction as in Scenario A - only under time pressure and with a rush surcharge
- reputation and trade-partner trust: not monetisable, but real
Scenario B contains Scenario A as a subset - plus the penalty, plus the customs stop, plus the surcharge. It is structurally more expensive, regardless of which amounts you plug in. This pattern is known from other EU regulations (REACH, CLP, the Medical Devices Regulation): the planned introduction is below the cumulative costs of the reactive one.
What you should really do differently
The most common mistake is to see the DPP topic as an IT project. It is a cross-departmental topic: purchasing delivers supplier data, production delivers batch data, marketing uses the end-customer touchpoints, compliance owns the audit trail.
Anyone who resolves today to complete the topic before the end of 2026 is within the planned time window. Anyone who starts in 2027 opts for the reactive scenario. The maths then shows which scenario was cheaper.