Key points
- Each data type needs one official source.
- Order processing must be idempotent so retries do not create duplicates.
- Published stock should account for reservations and delay.
What moves between ecommerce and ERP
The catalog may start in ERP, PIM or the store, depending on who manages it. Orders usually start in ecommerce and enter ERP for validation, reservation, documents and delivery.
For each field, define who creates it and who can change it. Two sources rewriting the same price or address create conflicts.
- Products, variants and codes
- Prices and promotions
- Available inventory
- Customers and addresses
- Orders and payments
- Invoices, shipments and returns
Identifiers and duplicate prevention
Product code, customer identifier and order number need consistent mapping. Names are not safe identifiers, and customer email can change or repeat.
If the store sends the same order after a timeout, ERP must recognize that it has already been processed. A retry must not create another order or invoice.
Publishing the right stock
The store should not automatically display every physical unit. Subtract reservations, blocked stock and a safety buffer appropriate to synchronization speed.
Fast-moving products need event-based or frequent updates. Define what the store does when ERP is temporarily unavailable.
From payment to delivery
Integration should distinguish authorized, captured, refunded and failed payments. ERP applies commercial rules, reserves products and sends work to the warehouse.
After dispatch, tracking and status return to ecommerce. Partial shipments, cancellations and returns need explicit workflows.
Monitoring and error handling
Every exchange needs a log with time, identifier, outcome and reason for failure. The team should safely retry after correcting data.
Alerts need to reach the person who can act. A technical report nobody reads does not protect a blocked order.
Testing before launch
Test simple and variant products, discounts, existing customers, failed payments, duplicate orders, insufficient stock, partial delivery and returns. Compare totals and tax in both systems.
Start with controlled volume and inspect the first orders. Expand only after the important exceptions have a verified response.
Relevant Webmate resources
Continue with guides, services and examples directly connected to the topic of this article.
Frequently asked questions
How often should stock synchronize?
It depends on volume and overselling risk. Fast-moving products need more frequent updates or near-real-time events.
Should ERP or ecommerce issue the invoice?
Choose one official source for the fiscal document and send the result to the other system.
What happens when integration fails?
Orders should remain queued, retry without duplicates and alert the team. Document a temporary manual process.
