eCommerce and ERP Integration: From Core Flows to Advanced Automation
An online store can sell all day and night, but every order still has to be paid for, picked, packed, shipped, accounted for and sometimes returned. That work happens in the ERP. When the store and the ERP are not connected, teams copy orders by hand, stock levels drift, customers get "sorry, it's out of stock" emails, and finance chases payments in spreadsheets.
Integrating your eCommerce platform with your ERP removes that manual layer. This guide breaks the integration into two levels: the core flows every business needs, and the advanced flows that turn a basic sync into full order-to-cash automation.
The big picture: who owns which data
A good integration starts with a clear rule: each type of data has one owner.
- The ERP owns products, prices, inventory and fulfillment status.
- The eCommerce platform owns the customer's order, the payment and the return request.
Data then flows in the direction that matches its owner.
Core integration: the five essential flows
1. Product master data and price: ERP to eCommerce
Products, descriptions, variants, units of measure and prices are maintained once in the ERP and published to the store. When a price changes, or when a new product is approved, it reaches the storefront automatically. This avoids pricing mismatches between channels and removes double entry.
2. Inventory: ERP to eCommerce
Available stock is sent from the ERP to the store, so customers only see what you can actually deliver. This is the flow that prevents overselling. Depending on your business, you can publish stock per warehouse, sum several warehouses, or hold back a safety buffer for each channel.
3. Orders: eCommerce to ERP
When a customer places an order, it is created in the ERP as a sales order, with the customer, items, quantities, prices, discounts, taxes and shipping details. This is the trigger for the whole fulfillment process. A webhook from the store is the best way to do it, because the order reaches the ERP within seconds.
4. Payment: eCommerce to ERP
The payment details, such as the method, amount and transaction reference, are sent to the ERP so finance can record the receipt and reconcile it with the order. Whether the ERP posts a payment document, a journal entry or both depends on your accounting model.
5. Shipment status: ERP to eCommerce
When the warehouse ships, the ERP sends the carrier, tracking number and shipment status back to the store. The customer gets a notification and a tracking link, and your support team gets fewer "where is my order?" messages.
Advanced integration: automating the full order lifecycle
The core flows cover a successful order. Real operations also involve cancellations, partial fulfillment, payment authorization and returns. The advanced flows handle these exceptions without manual work.
Order cancellation: ERP to eCommerce
If the ERP cancels an order, for example because stock is not available or the customer asked for it, the cancellation is sent to the store so the order status stays correct and the customer is informed.
Picked and packed status: ERP to eCommerce
Instead of only telling the customer "shipped", the ERP can send intermediate statuses when the order is picked and packed. This gives customers better visibility and lets your support team answer questions without logging in to the warehouse system.
Payment capture: ERP confirms, eCommerce captures
Many stores authorize the payment at checkout and only capture the money once the order is confirmed. In this model, the ERP confirms the order after checking stock and credit, and then sends a payment capture request to the eCommerce platform. You only collect money for orders you can actually fulfill, and you avoid charging and then refunding.
Refund for a cancelled order: ERP to eCommerce
When an order that is already paid gets cancelled in the ERP, a refund request is sent to the store so the customer's money is returned through the original payment method. Finance and the storefront stay consistent.
Return request: eCommerce to ERP
When a customer asks to return an item, the request is created in the ERP as a return or return authorization. The warehouse then knows what to expect and can inspect the goods when they arrive.
Refund after QC acceptance: ERP to eCommerce
Once the returned goods pass quality control, the ERP triggers a refund request to the store. This puts the approval where it belongs, with the warehouse and finance teams, and the customer is refunded only after the return has been verified.
The complete order-to-cash and return cycle
| Flow | Direction | Level |
|---|---|---|
| Product master data and price | ERP to eCommerce | Core |
| Inventory | ERP to eCommerce | Core |
| Order | eCommerce to ERP | Core |
| Payment | eCommerce to ERP | Core |
| Shipment status | ERP to eCommerce | Core |
| Cancel order | ERP to eCommerce | Advanced |
| Picked and packed status | ERP to eCommerce | Advanced |
| Payment capture | ERP to eCommerce | Advanced |
| Refund request for cancelled order | ERP to eCommerce | Advanced |
| Return request | eCommerce to ERP | Advanced |
| Refund after QC acceptance | ERP to eCommerce | Advanced |
Best practices
- Start with the core flows, then add advanced flows one at a time. Orders and inventory usually deliver the fastest return.
- Use webhooks for events such as new orders, cancellations and returns, and scheduled jobs for bulk data such as full price lists.
- Make every message safe to retry. Use the order number or a unique reference so a retry never creates a duplicate order or a double refund.
- Map identifiers carefully. Keep a link between each store SKU, order and customer and its ERP counterpart.
- Handle partial cases. Partial shipments, partial refunds and split payments are normal, so design for them from the start.
- Monitor and alert. A failed order message should raise an alert immediately, not be discovered at the end of the month.
- Reconcile regularly. Compare orders, payments and refunds between the store and the ERP every day.
How AllSync helps
AllSync connects your eCommerce platform and your ERP through webhooks and APIs, and handles the mapping, transformation, retries and monitoring in between. For ERP systems that sit on a local network without a public API, an offline connector installed on the local server reads the data and sends it to AllSync. You can start with the five core flows and enable the advanced flows when your operation is ready.
Conclusion
A good eCommerce and ERP integration gives you accurate stock, faster fulfillment, cleaner finance and happier customers. Start with the core flows of products, inventory, orders, payments and shipments, then automate cancellations, payment capture and returns to cover the full lifecycle.
Want to connect your online store with your ERP? Talk to us about doing it with AllSync.