DAM and PIM integration connects the system that governs media files with the system that governs product data, so every product record references the correct, approved and licensed assets. The most common pattern keeps files and rights in the DAM and stores asset references, roles and sort order in the PIM, with links created automatically through GTIN or SKU based naming or metadata.
DAM and PIM integration connects the system that governs media files with the system that governs product data, so each product record references the correct, approved and licensed assets. In the most common design, the DAM owns files, renditions and rights, while the PIM owns product attributes and the relationship between a product and its assets. Links are created automatically through a shared key such as GTIN or SKU.
Which system should own which data?
Integration problems usually start with unclear ownership. A clear split assigns every data element to exactly one system of record.
| Data element | System of record | Notes |
|---|---|---|
| Original file and versions | DAM | Single approved version per asset |
| Renditions and crops | DAM or CDN | Generated per channel profile |
| Descriptive and technical metadata | DAM | Shot type, colour space, dimensions |
| Rights, licences, expiry | DAM | Propagated to PIM as a status |
| Asset-to-product link | PIM | Many-to-many: one image can serve several variants |
| Asset role and sort order | PIM | Main image, gallery, detail, packaging |
| Alt text per locale | PIM or DAM, agreed once | Often product-specific, so PIM-owned |
| Channel-specific selection | PIM or syndication layer | Different sets per marketplace |
Alt text deserves an explicit decision. The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 and covers e-commerce services, which raises the importance of text alternatives for product images, as discussed in European Accessibility Act and product content.
What are the main DAM and PIM integration patterns?
Four patterns cover most implementations:
- Embedded asset module. The PIM stores files itself. Simple, suitable for product images at modest volume, limited for campaign content and rights.
- DAM master with references. Files stay in the DAM; the PIM stores asset IDs or CDN URLs. Channels receive URLs, so files are never duplicated.
- Scheduled synchronisation. A connector copies approved assets or metadata between systems at set intervals. Easier to build, but changes such as expiries arrive with a delay.
- Event-driven synchronisation. Webhooks or messages from the DAM (asset approved, updated, expired) trigger updates in the PIM through an integration platform. Most timely, with higher build and monitoring effort.
Choosing between them depends on three factors. Volume matters first: tens of thousands of product images fit many embedded modules, while large video and campaign libraries favour a DAM master. Rights complexity comes second: licensed lifestyle content needs DAM-level rights data and fast propagation of expiries. Timeliness is third: daily synchronisation may be acceptable for new catalogue images, but recalls, safety information and withdrawn assets need event-driven updates.
Vendor-provided connectors exist for many combinations. A connector should be tested for its handling of deletions, version changes and expiry, which are frequent sources of production incidents.
How to link assets to products automatically
Manual linking does not scale beyond a few thousand assets. Automated linking relies on a shared identifier captured at ingest:
- File naming: the GS1 Product Image Specification defines names that start with the 14-digit GTIN followed by image type, facing and orientation codes, for example
09521234567813_C1C1.tif. - Metadata fields: SKU, GTIN or model number stored in a mandatory DAM field, plus an asset role such as packshot or lifestyle.
- Rule engine: the connector maps role and facing codes to PIM asset roles and sort order.
Assets that fail to match a product should land in an exception queue with the reason (unknown GTIN, missing role, duplicate facing), so the studio or supplier can correct the source instead of the PIM team fixing links by hand. Rules for these fields belong in the DAM metadata taxonomy.
How do rights and expiry flow between DAM and PIM?
Rights data must reach every channel that displays an asset. A working flow:
- The DAM records licence terms and expiry for each asset.
- On expiry, the DAM changes the asset status and emits an event.
- The PIM unlinks the asset or swaps in an approved fallback image.
- The next product data syndication run withdraws the asset from webshops, marketplaces and retailer feeds.
- A report lists products that lost their main image, so the studio can schedule a reshoot.
Detailed rights fields are described in digital asset rights management.
Practical next steps
- Agree the ownership table above with product, marketing, studio and IT teams.
- Choose the integration pattern based on volumes, rights complexity and need for timeliness.
- Define the linking key and enforce it at ingest for studios, agencies and suppliers.
- Test connectors with deletions, new versions and expiries before go-live.
- Monitor broken links and missing main images as a data quality metric. An independent DAM vendor directory is available at DAM Atlas.
Frequently asked questions
Should images be stored in the PIM or the DAM?
Where a dedicated DAM exists, original files and renditions should live in the DAM, with the PIM holding references and product-specific context such as asset role and sort order. Organisations with modest volumes of product images often use the asset module inside the PIM instead.
How are assets linked to products automatically?
Automatic linking uses a shared identifier. Files named with the GTIN according to the GS1 Product Image Specification, or tagged with SKU and asset role metadata at ingest, can be matched to product records by a connector or rule engine without manual work.
What happens when an image licence expires?
The DAM marks the asset as expired and sends an event or flag to the PIM. The PIM removes or replaces the reference, and the next syndication run withdraws the asset from webshops, marketplaces and retailer feeds.