Custom solution · product data

Connect product data reliably between systems

We integrate data sources, ERP, PIM, files and target systems into a clearly defined data flow. Field mapping, validation, error handling and handover are implemented traceably.

Discuss product data integration
Schematic illustrationConnect systems
Customer / source system
ERP / PIMCSV / XML / JSON
excodata · agreed scope
  1. Mapping
  2. Transformation
  3. Validation
Recipient / target systemOutput · Acceptance

We integrate data sources, ERP, PIM, files and target systems into a clearly defined data flow. Field mapping, validation, error handling and handover are implemented traceably.

Typical projects

Source data

  • synchronise ERP and PIM
  • automatically import supplier or customer files

Processing

  • transform CSV, XML, JSON, BMEcat and API data
  • merge media and product references

Review and approval

  • check data quality before export or import

Output

  • generate catalogue- and recipient-specific output

The technical target state

A reliable integration has defined sources and destinations, unique keys, versioned mapping rules, logged errors, repeatable processing and testable acceptance criteria.

Fictional integration example

ERP file → Transformation → PIM · No standard interface promised

A missing unit stops the handoff of the affected item

01 · SourceCustomer · Data and access rights

ERP file · Input state

A-101 · Mounting bracketWeight: 0.25 · Unit: kg
A-102 · SupportWeight: 0.40 · Unit: missing

02 · Processingexcodata · Agreed scope

Example rule · Version 1

  1. Map the item number to the target identifier.
  2. For “kg”: value × 1000, target unit “g”.
  3. Without a unit: hold the item and log the error.

03 · TargetRecipient · Testing and acceptance

PIM · Result of this run

A-101 · 250 gFor the agreed handoff
A-102 · Held backNo handoff without a unit
Clarification for A-102
Error log → Customer → Reprocessing

Document “Unit missing” with the item identifier. The customer adds the unit based on a reliable source. The corrected record returns to 02 · Processing and goes through the same check again.

Testable acceptance in this example: A-101 becomes 250 g; A-102 remains held back without a unit. The agreed handoff can only take place after an evidence-based correction and a new check.

The rule applies only to this fictional example. Error handling, partial handoff, retries and responsibilities are agreed for each project. Passing a technical check does not replace expert approval.

Scope boundaries

Responsibility for source data quality, specialist approvals and access rights remains clearly assigned. Operations, monitoring and further development are only included if agreed separately.

FAQ

Can integration be implemented without replacing the existing PIM?

Yes. The solution usually complements existing systems with transformation, validation or additional data flows.

Which interfaces are possible?

That depends on the systems involved. APIs, file transfers and scheduled jobs are assessed for the specific scope.

How is data quality safeguarded?

Through agreed validation rules, error logs, test data and clear acceptance criteria.

Custom solution · product data

Define your task

Discuss product data integration