PIM integration requirements: APIs, ERP, standards and channels

What do PIM integration requirements cover?

Integration requirements define how product data enters and leaves the PIM, and which systems own which fields. They form the third domain of the PIM requirements guide. In PIMvendors selections, integration is where most cost overruns start, because connectors, mappings and monitoring are often scoped after the licence is signed.

PIM Selection publishes 60 integration requirements in 11 groups.

Start from your system landscape. List every source and target system, the data each one sends or receives and the frequency. That inventory turns into requirements and into the integration part of your demo scenarios.

Which API requirements should a PIM meet?

A PIM should expose a complete, documented API that enforces the same rules as the user interface and supports bulk operations within known rate limits. Every future integration depends on these four properties.

1. Complete coverage (IN-001): read and write access to products, attributes, families, categories, assets and relationships.
2. Bulk and pagination (IN-003): full catalogue extraction within your integration window.
3. Known limits (IN-004): rate limits per licence tier, with your expected volume confirmed in writing.
4. Same rules (IN-005): API writes pass the same validation, permissions and workflow as screen edits.

IN-005 deserves a live test. Write an invalid value through the API and confirm the rejection message matches the rule in the screen. An API that bypasses validation becomes the main route for bad data within months of go-live.

Supporting requirements complete the set. Public documentation with a versioning policy (IN-002) lets your architect estimate effort before contract. Scoped credentials per integration (IN-006) limit the impact of incidents. A sandbox with representative data (IN-007) keeps integration testing away from production.

How should a PIM integrate with the ERP?

A PIM should receive the article record from the ERP and own only the fields assigned to it. Field ownership per attribute is the single most important ERP integration requirement.

The ERP usually creates the article with number, status, base unit and logistics data (IN-008). The PIM adds descriptive, technical, marketing and channel data. IN-009 makes ownership configurable per attribute, so neither system overwrites the other's fields. Agree the ownership table in the requirement phase and test conflicting updates from both sides in the demo.

Automation keeps the handover fast. A new ERP article should start the enrichment workflow automatically (IN-010). Integration errors need a monitoring screen with retry and alerts (IN-012). Silent failures leave the two systems out of sync for days.

Prebuilt connectors help when they are in real use. IN-011 asks for a reference customer on a comparable ERP version. Detailed patterns for ERP integration are covered in PIM and ERP integration.

Which product data standards must a PIM support?

A PIM must support the standards your customers and trading partners require, and no more. Electrotechnical, installation and building wholesale expects ETIM. Industrial procurement often expects ECLASS and BMEcat. Grocery, health and beauty retail expects GS1 data through data pools.

Standards publish new releases regularly. ETIM 10.0 was published in December 2024 after 5,264 change requests, according to ITEK. IN-037 asks the vendor or partner to support each new release within a stated period. Validate every standards export with the receiving trading partner during the selection. Standard-specific detail is on the ETIM and BMEcat pages.

How do we test channel feeds and marketplaces?

Test channel feeds by building one of your real channel specifications live from master data. Feeds built outside the PIM recreate the spreadsheets the PIM was bought to replace.

The core feed requirements are per-channel mapping and conversion (IN-040) and retailer templates generated from one master record (IN-043). Business users should maintain mappings with a preview (IN-041). Errors returned by channels should link back to the product and attribute (IN-042). Publication status per product shows which channel received which version (IN-045).

Marketplaces add category-specific schemas that change often (IN-047) and listing errors that should return to the PIM (IN-048). Since 13 December 2024, GPSR requires manufacturer details and safety information in every online offer to EU consumers. IN-049 maps those fields to each marketplace in scope. Marketplace-specific titles and images must not overwrite master values (IN-051).

Ownership matters as much as features. IN-050 asks who built and supports each marketplace connection. The wider syndication architecture is covered in product data syndication.

DAM, PLM, data pools and events

The remaining integration groups decide how well the PIM fits the systems around it. Each group is critical for some buyers and irrelevant for others, so filter by industry before prioritising.

DAM requirements cover linking by stable identifier (IN-016), rights and expiry synchronisation (IN-017) and document assets per language and version (IN-020). Safety data sheets and declarations of conformity belong in that last group, which is why IN-020 is tagged GPSR.

PLM requirements matter for manufacturers with engineering-driven data. Released revisions (IN-013), engineering change tasks (IN-014) and material declarations (IN-015) bring technical truth into the PIM.

Data pool requirements apply to suppliers of grocery, health and beauty retailers (IN-052 to IN-055). Event requirements apply to every modern landscape: webhooks on change (IN-056), payloads with changed attributes (IN-057), retries (IN-058) and a connector to your integration platform (IN-059). Platform-side limits such as performance at volume are covered in platform, security and vendor requirements.

The 60 published integration and syndication requirements

The full IN set is listed below with statement, rationale, test, default priority and tags. Filter, adjust and export it in the PIM requirements checklist.

{{list:requirements:IN}}