Integrating PIM with ERP: data flows and integration patterns

Which data flows from ERP to PIM and back?

Most data flows from ERP to PIM, and only a few flow back. The direction follows the attribute-ownership map described in the PIM architecture pillar. ERP masters identification, commercial and logistic data. The PIM masters marketing content and classification.

Prices and stock for web shops usually bypass the PIM. They go directly from ERP to the commerce platform, because they change faster than content.

Which integration patterns exist for PIM and ERP?

Four patterns exist: batch, event-driven, API and iPaaS. Each fits a different kind of flow. Choose a pattern per data flow.

In PIMvendors selections, the typical mid-market landscape combines nightly batch for logistic data with events for new articles and status. Enterprise landscapes add an iPaaS when several ERP instances or business units feed one PIM.

When is batch integration good enough?

Batch integration is good enough when the data changes slowly and channels tolerate a delay of hours. Weights, dimensions, packaging units and customs codes fit that profile. Batch is also the easiest pattern to build, test and monitor.

Batch has three weak points:

• New articles wait for the next run before enrichment can start.
• Full reloads hide which records changed, which complicates auditing.
• Failed runs often go unnoticed until a channel shows outdated data.

Use delta exports where ERP supports them, and add monitoring with alerts on failed or empty runs. A batch that runs every night with clear error reporting is better than a fragile real-time flow.

When should you choose event-driven or API integration?

Choose event-driven integration when the business needs changes in minutes and the volume of changes is moderate. New articles, lifecycle status and blocked products are typical candidates. Enrichment can start as soon as ERP creates the article.

Choose API integration for lookups and small updates on request. A PIM screen showing current ERP stock, or a supplier portal checking an article number, are examples. API calls create tight coupling, so check rate limits and behaviour when one system is down.

Both patterns need a decision on error handling. Define what happens when the PIM rejects a message, who is alerted and how the message is replayed. Put that decision into the integration requirements before the demos.

How does ERP replacement affect PIM integration?

ERP replacement affects PIM integration because every ERP flow must be rebuilt for the new system. SAP Business Suite 7 mainstream maintenance ends on 31 December 2027. Extended maintenance for EHP6 to EHP8 runs until 31 December 2030. Organisations on SAP ECC therefore face an ERP migration within the term of a typical PIM contract.

Design the PIM integration to survive that migration:

1. Map ERP data to a neutral PIM data model, so the PIM side stays stable.
2. Put mappings in an integration layer or iPaaS, outside custom PIM code.
3. Document every flow in a data flow inventory with source, target, data, pattern and frequency.

The SAP ecosystem shortlist covers PIM options for SAP-centred landscapes.

Who should own the PIM and ERP integration?

One named integration owner should hold every PIM and ERP flow, with the ERP and PIM owners as approvers. Integrations without an owner fail quietly. Nobody notices until a channel shows outdated data or a new article never arrives.

The integration owner is responsible for four things:

• The data flow inventory, kept current when flows change.
• Monitoring and alerts for failed, delayed or empty runs.
• Error handling rules, including who fixes rejected records.
• Change control when ERP or PIM releases affect mappings.

Decide early whether the implementation partner, your IT team or an iPaaS team owns the integration after go-live. That choice moves cost between the implementation, run cost and internal time lines of the TCO. The PIM total cost of ownership guide shows where each option lands.

What should the PIM selection test for ERP integration?

The PIM selection should test ERP integration with your own data and your own flows. A connector on a slide says nothing about your field mapping, custom fields or volumes.

Include three integration scenarios in the demos:

1. Import an ERP extract of one product family, including custom fields, and show the mapping.
2. Create a new article in a test ERP and show when and how it appears in the PIM.
3. Approve content in the PIM and show the write-back flow, if one exists.

Score the results against your integration requirements. PIMvendors cross-checks requirements against a 4-domain checklist of more than 400 requirements, with Integration and syndication as one domain. The product data stack guide places ERP integration in the wider landscape. The SaaS vs on-premise guide covers how hosting affects integration options.