Digital infrastructure needs, challenges and solutions for turning supplier information into reliable, attributable DPP data – before the passport goes live.
The EU framework expects product information that is interoperable, machine-readable, structured and searchable. The EU DPP Registry has been operational since July 2026 – yet much of the information behind a passport originates outside the operator that is responsible for it.
of operations and supply chain leaders rank data availability and quality among the top three challenges to scaling AIPwC via WEF · 2025
of COOs identify data quality issues as their most significant data priorityIBM Institute for Business Value · 2025
annual cost of poor data quality, estimated by over a quarter of organizationsIBM Institute for Business Value · 2025
of supply chain leaders cite lack of trust or confidence in data as a top hurdleGartner · 2023
report moderate to significant operational impact from duplicates, inaccuracies and no real-time verificationMelissa · State of Enterprise Data Quality 2025
data points defined for EV, LMT and industrial batteries in the Digital Batteries Passport guidanceEuropean Commission · Aug 2026
DPP interoperability does not eliminate the cost of data exchange – it determines where that cost is incurred.
External information rarely arrives "DPP-shaped". Before it can be exchanged efficiently, it has to become usable within the receiving organization's own data model.
A certificate expresses it as a percentage by mass. A supplier DPP exposes it as 0.374 kg/kg. The receiving DPP needs a defined percentage field, linked to a specific material, component or product level. Same fact – not interchangeable without interpretation and mapping.
What information is actually being provided?
What exactly does the value mean in the source's context?
Which field or data object should contain it?
How does the source representation correspond to the target?
Is the resulting value technically and contextually valid?
Which product, variant, batch or entity does it describe?
Which entities are described, which attributes belong to them, and how the resulting information is accessed and governed. The standardized layer defines required data points; the organization configures everything around it.
Attached to the wrong product, interpreted incorrectly, unsupported by evidence, or contradicted by another source. Validation is a progression from syntax to cross-source reconciliation.
Is the value in the correct format; is a number actually a number? Highly deterministic, easily automatable, reinforced by the DPP framework's structure and controlled vocabularies.
Is it placed in the correct part of the model? A batch production date must not become a property of the product model. Database constraints, referential integrity, hierarchy and cardinality rules.
Does "37.4% recycled PET" describe the PET itself, the finished component, or something else? Vocabularies, semantic mappings and calculation rules help – human supervision often still needed.
Is the document present, valid, unexpired, matched to a known record, digitally verifiable? Finding evidence is not the same as deciding it is sufficient.
DPP, certificate and ERP say 37.4%; procurement says 40%. A system can detect the difference and apply predefined authority rules – it cannot safely infer why the numbers differ.
The more automated the exchange becomes, the more important it is to know what the system can validate – and when it needs to stop and ask.
An electronics manufacturer with an incorporated battery module relies on information that originates several tiers upstream. Designating one system as "the source of truth" only multiplies duplication.
ERP holds the commercial identifier of the purchased module, PLM establishes which module belongs to which variant, MES links it to a production batch. The "quest for the ultimate upstream source" is often pointless – use the source with sufficient authority, context and accessibility.
Measured in a laboratory, declared by a supplier, calculated from a bill of materials.
The supplier's MES, the manufacturer's ERP – each holding its own representation.
Supplier DPP, portal, API, documentation – every node before the target system.
A manual workflow is a feedback loop: apply the model, encounter exceptions, refine rules, repeat – while stable steps are stacked in the automation backlog.
Normalization makes representations technically compatible. Semantic interoperability establishes whether they are conceptually compatible. Mapping turns the relationship into an operational rule.
Production date → Production date
37.4% PCR PET → content, material type, methodology
component mass + recycled mass → recycled %
0.374 kg/kg → 37.4% once meaning and scope are known
Destination depends on component type, battery category or regulation
A battery manufacturer receives recycled cobalt content for a cathode material from three sources. A simple routine sees the values differ – it cannot decide which one belongs in the DPP without rules defined upfront.
Context-first reconciliation checks whether the values describe the same component, batch, period and method before comparing authority.
Facts change during the lifecycle (temporal decay), and representations drift as values move between systems (representational distortion). Each step can be legitimate – and still lose precision, context or meaning.
Material batch C-2026-041, reporting context 2026.
✓ still validTotal cobalt in the bill of materials changes.
→ triggers dependentsNo source expired – the conditions of the calculation did.
needs recalculationThe goal is not to prevent change. It is to make it visible, attributable and traceable.
A supplier reports that 42% of cobalt in a cathode active material batch comes from recovered sources. The manufacturer's DPP is scoped by model, batch or individual battery. Three legitimate moves – not interchangeable.
Keep. If no battery-level value is required, the 42% figure remains at material-batch level – original scope preserved.
One is the rated capacity specified for Model X, the other a measured result for battery B12345.
Model, variant, batch or serial; site; period; measured, calculated, declared or specified.
Retain the original and request more data rather than publishing a more precise-looking number.
If every company builds its own integration and mapping, the same work is duplicated across the network. Shared interfaces, schemas or intermediaries turn repeatable work into reusable infrastructure.
Getting to set your own schema is an "early bird" privilege. Integration capability can morph into infrastructure rather than a one-off compliance expense.
Manufacturer X may use V's confidential data to compile its DPP – but not publish it or pass it unchanged to Y. Technology can't always enforce contractual limits, but it can represent them and make permitted flows auditable.
| Recycled-content value | Manufacturer X |
| Supporting production records | X + authorized authorities |
| Onward sharing with defined partners | Permitted |
| Public disclosure of the records | Not permitted |
Source data → validation / calculation → derived result → authorized disclosure. Each stage can carry its own access conditions, enforced by role-, organization- and relationship-based rules, controlled APIs and audit records.
As products, suppliers and exchange relationships grow, the question shifts from "How do we create our DPP?" to "What infrastructure keeps the information behind it reliable as everything changes?"
Standards can define how information should be represented and exchanged. They cannot eliminate the need to establish what it means, where it came from, whether it is still valid, and who is responsible for it.
10 chapters on data models, validation, source conflicts, data decay, granularity, B2B access and the infrastructure that keeps a DPP reliable.
Check your inbox for the download link. Want to discuss your DPP data infrastructure? Talk to Lionwood →