Integration
PLM and PIM Systems for the DPP
How product data held in PLM and PIM systems feeds a Digital Product Passport — which data lives where, and how to design the integration.
Product data does not live in one system. ERP holds commercial and logistics data, PLM holds design and technical data, and PIM holds marketing content. A Digital Product Passport draws on all three — and the most critical fields usually sit in PLM.
Which data lives where?
| Data | Usually in | Passport heading |
|---|---|---|
| Product code, GTIN, price, stock | ERP | Identity |
| Bill of materials, material shares | PLM | Composition |
| Supplier and facility | PLM / ERP | Origin |
| Technical specifications, tests | PLM | Compliance |
| Certificates | PLM / Quality | Compliance |
| Images, descriptions, translations | PIM | Presentation |
| Care and repair instructions | PLM / technical publications | Circularity |
See ERP integration for DPP and DPP data fields.
Why PLM is central in textiles
In apparel, collection development runs through PLM: style, material card, supplier assignment, sampling and approval. Fibre shares, fabric supplier and trim information originate in PLM, not ERP. That makes PLM the centre of gravity for textile DPP integrations. See the textile DPP guide.
The source-of-truth problem
When the same field exists in several systems it will eventually disagree with itself. Set rules:
- Identity: ERP.
- Composition and technical: PLM.
- Marketing copy and translations: PIM.
- Additional regulatory fields (carbon, recycled content): the passport platform.
Without those rules written down, publishing a wrong value is only a matter of time. See DPP data quality management.
PIM's proper role
PIM enriches the consumer experience of a passport: imagery, short descriptions, translations. It should not be the source for regulatory fields, because marketing copy changes often and follows different approval flows. See what consumers should see.
An integration pattern
- Pull technical and composition fields from PLM (triggered by product approval).
- Pull identity and commercial fields from ERP.
- Pull presentation fields and translations from PIM.
- Complete missing regulatory fields in the passport platform.
- Run pre-publication quality checks and create a version.
Frequently asked questions
I have no PLM. What now?
A single structured source for your bill of materials is enough. In small teams that can be a spreadsheet; what matters is that there is only one.
Can I pull regulatory fields from PIM?
Technically yes, but it is unwise: approval and version discipline differ. Keep regulatory fields in controlled sources.
Do I have to connect all three systems?
No. Start manually from one source in the pilot and extend integration only after the field mapping settles.
