Connect eCommerce, ERP, PIM and WMS through reliable flows

An eCommerce operation does not live in isolation. Products and prices may come from a PIM or ERP, stock from a WMS, orders from the shop and documents from the ERP. The problem is not simply “connecting two APIs”; it is defining a reliable flow when data, systems and responsibilities do not line up.

Operational situations to resolve

• The same data is entered or corrected in several systems.
• Stock and prices differ across the shop, ERP, marketplaces and warehouse.
• Orders or documents stop moving without a clear place for the team to intervene.
• An integration exists but has no owner, monitoring or recovery procedure.

The intended operating model

Each data domain needs an authoritative source, destination, frequency and transformation rules. Errors need to be visible, classifiable and recoverable; the team needs to know who intervenes and how systems are reconciled.

What I examine

• Sources and destinations for product, price, stock, customer, order and document data.
• Events, frequencies, volumes, dependencies, edge cases and system constraints.
• Manual steps, duplication and points where an error can remain hidden.
• Available APIs, exchange formats, legacy access and operational ownership.

What delivery can include

• Synchronisation of catalogues, prices, availability, customers, orders and documents.
• Middleware where systems cannot communicate directly.
• Webhooks, queues and scheduled jobs aligned with frequency and reliability needs.
• Retries, idempotency, notifications, operational logs and reconciliation tools.
• Documentation of flows, dependencies, ownership and intervention procedures.

Decisions that define the integration

Before code, the work defines authoritative sources, direction and frequency, duplicate handling, retry rules, expected consistency, access security and ownership. Without these decisions, an integration merely moves manual work elsewhere.

How the work proceeds

I map the current flow, define architecture and acceptance criteria, delimit a verifiable first release and move the system into production with monitoring and documentation. The broader process is described on the Method page.

What I handle personally

I handle data mapping, architecture, specifications, implementation and verification. Where internal teams or suppliers are involved, I make technical boundaries and responsibilities explicit.

Relevant published work

The Portfolio documents Kikkiline’s Shopify migration with Danea Easyfatt integration and a JSON feed export. These are facts already published in the project entry.

Technologies and systems

REST and GraphQL APIs, webhooks, RabbitMQ, Symfony Messenger, PHP/Symfony, Node.js, Golang, Akeneo, ERP, PIM, WMS and JSON, XML or CSV formats. Technology is selected after the flow and its requirements are defined.