DPP and ERP Integration - a practical guide for companies

The Digital Product Passport (DPP) requires detailed product data - from composition and environmental parameters to supply chain information. Most of this data already exists in your ERP system. The real question is: how do you extract it and feed it into a DPP platform in a repeatable, scalable, and secure way?

This article covers concrete integration approaches, supported ERP systems, and a step-by-step integration process.

If you are not yet familiar with what DPP is and why the EU is introducing it, start with our introductory article: Digital Product Passport in 15 minutes.

Key takeaways

Most data required for DPP already lives in your ERP - you do not need to collect it from scratch.
Three main integration approaches: CSV export, direct API, PIM as middleware.
The right approach depends on your IT maturity, number of SKUs, and how often data changes.
Platforms like myDPP offer ready-made connectors for popular ERP systems.
Integration is a matter of weeks, not months - if your data is in good shape.

Why ERP integration matters for DPP

Your ERP system is the central source of truth for product data in most manufacturing and distribution companies. It holds:

master product data (name, SKU, classification),
composition and material information,
logistics data (weight, dimensions, packaging),
supplier and supply chain information,
certificates and compliance records.

Manually transferring this data to a DPP platform leads to errors, inconsistencies, and delays. Automated integration eliminates these risks and keeps product passports up to date at all times.

EU regulations (ESPR, Battery Regulation) require DPP data to be current and verifiable. Integrating with your ERP is the most straightforward way to meet that requirement.

What data flows from ERP to DPP

Not all DPP data comes from the ERP - some requires additional sources (e.g., lab test results, third-party certificates). However, the ERP provides the foundation:

Data category	Examples	ERP source
Product identification	GTIN, SKU, trade name	Product master data
Composition and materials	BOM, raw materials, substances	Production module
Logistics data	Weight, dimensions, packaging unit	Logistics module
Supply chain	Suppliers, country of origin	Procurement module
Compliance	Certificates, declarations	Quality module
Environmental data	Carbon footprint (if calculated)	ESG/reporting module

Three integration approaches

1. CSV export / flat file

Best for: companies with a smaller number of SKUs that update data infrequently (e.g., once a month).

The process is simple - you export data from your ERP into a CSV file in a defined format, then import it into the DPP platform. Many ERP systems support scheduled automatic exports.

Pros: low barrier to entry, no development work required. Limitations: no real-time updates, risk of errors when handling files manually.

2. Direct API integration

Best for: companies with large product catalogs, frequent data changes, or a need for real-time updates.

The DPP platform exposes a REST API that your ERP (or middleware) pushes data to automatically. Changes in the product master record can be instantly reflected in the product passport.

Pros: full automation, data always current, supports two-way communication. Limitations: requires development effort on the ERP side or middleware implementation.

3. PIM as middleware

Best for: companies that already use a PIM (Product Information Management) system for managing product data.

If you have a PIM (e.g., Akeneo, Pimcore, inRiver), it already aggregates data from your ERP and other sources. Connecting the PIM to a DPP platform is often the fastest path, because the data is already cleaned, structured, and enriched.

Pros: highest data quality, easy field mapping, natural extension of an existing process. Limitations: requires an existing PIM - not the right starting point if you do not have one.

Step-by-step integration process

Data audit - identify which DPP-required fields already exist in your ERP and which need to be filled. Prepare a field mapping document.
Choose your approach - based on SKU count, change frequency, and IT capabilities, decide between CSV, API, or PIM.
Configure the connector - set up the connection between your ERP and the DPP platform. With myDPP, you can use pre-built connectors or the REST API.
Field mapping - map ERP fields to the fields required by the DPP schema. This is the most critical step - it determines the quality of your passports.
Test sync - push data for a handful of products and verify correctness. Check completeness, formats, and character encoding.
Full sync - after test approval, run the sync for your entire catalog. Set up a schedule for automatic updates.
Monitoring - track sync errors, missing fields, and integration logs. The myDPP platform provides a dashboard to monitor integration health and data quality.

Supported ERP systems

SAP (S/4HANA, ECC)

SAP is the most widely used ERP in large manufacturing companies. DPP integration typically runs through SAP Integration Suite or directly via RFC/BAPI and REST APIs. Product data from the MM (Material Management) and PP (Production Planning) modules forms the passport foundation.

Microsoft Dynamics 365

Dynamics 365 offers native APIs (Dataverse / OData) and Power Automate for data flow automation. Integration with a DPP platform is relatively straightforward - especially in environments already using the Microsoft ecosystem.

Comarch ERP

A popular choice among mid-sized companies in Central Europe. Comarch ERP (XL, Optima, Altum) exposes APIs and supports data exports. DPP integration is often done via flat file or a dedicated connector.

Enova365

An ERP system commonly used by Polish SMEs. Enova365 supports data export and API-based integration. For smaller product catalogs, CSV-based integration is sufficient.

FAQ

How long does an ERP-to-DPP integration take?

For companies with well-maintained ERP data, expect 2 to 6 weeks depending on the integration approach and catalog complexity. The biggest time investment is usually data auditing and cleanup, not the technical integration itself.

Do we need to modify our ERP?

Typically not. The integration reads data from your ERP rather than modifying the system. In some cases it makes sense to add extra fields (e.g., carbon footprint), but that is an extension, not a change.

What if our ERP data is incomplete?

That is common. The myDPP platform allows you to fill in missing data manually or from other sources. ERP integration covers the foundation - the rest can be added in stages.

Can we integrate more than one ERP system?

Yes. Companies with multiple business units or post-merger landscapes often run different ERP systems. A DPP platform can accept data from multiple sources and merge them into a single product passport.

Next steps

If your company is planning a DPP rollout and wants to connect ERP data, the myDPP platform offers:

pre-built connectors for SAP, Dynamics 365, Comarch, and Enova365,
a REST API for any system,
CSV import for a quick start,
a dashboard for monitoring integration health and data quality.

Book a demo and see how fast you can get your integration running: mydpp.app.