Which system should own which data
Before integrating, agree on who owns what. The ERP or PIM usually remains the source of core data: name, SKU, GTIN, brand, model and descriptions. DPPC takes over what those systems typically do not handle well: material composition with share and origin, documents and certificates with review and expiry dates, supplier data, product approval and publication of the passport with a QR code. That way every piece of information has exactly one place where it is edited.
How integration with DPPC works
DPPC provides a REST API, version v1, with documentation and a downloadable OpenAPI schema. The API covers products, materials, documents, suppliers, certificates and industry field templates, as well as workflow actions: approving, rejecting, publishing and archiving a product. There are no ready-made plugins for specific ERP systems. The integration is built by your IT team or an integrator who knows your ERP or PIM, and the DPPC API is designed to make that integration simple and predictable.
Batch sync instead of individual calls
With large catalogs it is easier to send data in batches. Sync jobs accept up to 500 product, supplier or certificate records at once, create new records or update existing ones, and are processed in a background queue. The job status, the number of processed records and a description of errors can be checked through the API. Before saving, data can also be sent for preview validation, which returns warnings without changing anything in the system.
Webhooks: sending changes back to your systems
The integration works in both directions. DPPC sends webhooks when products, materials, documents, suppliers and certificates are created, updated or deleted, and when a passport is published. Every notification is signed with HMAC-SHA256, so the receiver can verify that it comes from DPPC. Failed deliveries are retried three times, after one, five and fifteen minutes, and a test event can be sent from the organization settings.
Integration security and reliability
Each system connects with its own API key and selected permissions, for example read-only access to products or write access to certificates, so the key used by an online store cannot change data. Write operations support the Idempotency-Key header: sending the same request again, for example after a dropped connection, does not create duplicates. The limits are 180 reads and 60 writes per minute per key.
DPP ERP integration step by step
Start by mapping fields: which data from the ERP or PIM goes into DPPC and into which fields, including the industry fields from the template available through the API. Then create an API key with minimal permissions and test preview validation on a few products. Next, run the first batch sync for one category and configure webhooks if other systems need to react to changes. Documents and certificates are usually completed in DPPC, because that is where they are reviewed.