Most of the data needed for the Digital Product Passport is already in your ERP or PIM system. myDPP connects to them via ready-made connectors, API, or CSV import - and automatically builds DPP passports compliant with EU regulations.
Start with a CSV file the same day, and launch the API integration when you are ready.
The right approach depends on your company's IT maturity, number of SKUs, and frequency of data changes. You can start with the simplest option and gradually move to a more advanced one.
Fastest start - Start the same day
Prepare a file with product data in CSV or Excel format. myDPP automatically maps columns to passport attributes. Ideal for getting started and for companies with fewer SKUs.
Automation - 2-4 weeks implementation
Connect your ERP or PIM system via REST API. Data syncs automatically - a change in the source system is immediately visible in the DPP passport.
For complex environments - 4-6 weeks implementation
If you have multiple data sources (ERP + PLM + DAM), PIM consolidates them in one place. myDPP pulls a ready, unified set of product data.
Ready-made connectors for the most popular ERP systems in Europe. For others, a universal REST API and CSV import.
Connector for SAP Material Master, BOM, and environmental data. Synchronization via SAP Integration Suite or direct RFC/BAPI.
Integration with Dynamics 365 Supply Chain Management and Finance. Product, logistics, and compliance data in a single flow.
Ready-made connector for the Polish market. Import of product data, material cards, and technical parameters.
Other ERP systems? Enova365, Sage, IFS, Infor - any system with CSV export or REST/SOAP API can be connected to myDPP via the universal connector.
PIM is a natural middleware layer between your data and the DPP passport. If you already have a PIM, integration with myDPP is the fastest path to a complete passport.
Native integration. Automatic synchronization of product attributes, translations, and images via API.
REST API connector. Mapping Akeneo attributes to DPP passport fields while preserving product family structure.
Integration via Pimcore Data Hub. Support for complex data models, variants, and object relationships.
From data audit to passport publication - in 5 steps. The entire process takes from 1 day (CSV) to 4-6 weeks (full API integration with multiple sources).
We check what data you have in your ERP/PIM and how far it is from DPP requirements. We identify gaps and prioritize attributes.
We define which fields in your system correspond to passport attributes. We configure data transformations and validation.
We launch the connection: a ready-made connector for supported systems, or universal API for others. We test on a data sample.
We import the full data set. The system validates completeness and flags missing attributes required by regulations.
We generate DPP passports with QR codes and GS1 Digital Link URLs. Data updates automatically with each synchronization.
Product data flows from ERP/PIM directly into the passport. No more manual copying and no risk of inconsistencies.
Changed a parameter in your ERP? The DPP passport updates automatically. No intervention, no delays.
From 10 SKUs to 100,000. API integration handles any product volume without additional manual work.
The system checks whether data meets regulatory requirements for a given product category. You see gaps before they become problems.
Detailed comparison of integration approaches, supported systems, and a step-by-step walkthrough of the implementation process.
ArticleIntroduction to DPP: what it is, why the EU is introducing it, and which industries will be affected first.
Frequently asked questions about DPP integration
In 15-30 minutes, we will do a preliminary assessment of your data sources and choose the shortest path to launching your passport.
We will tell you whether it is better to start with CSV or connect an API right away. We will identify data gaps and propose an integration plan tailored to your IT environment.
You will receive a proposed integration scope and a plan for next steps.