B2B ecommerce
How to integrate B2B ecommerce with your ERP
By Julián Medina · Director of SourcingUp and creator of CommerceUp
Define which system owns customer, pricing, stock and order data, and how each exchange is acknowledged. The integration is ready when you can also identify and recover from rejected or delayed transactions.
Define the source of truth for each data type
The portal and the ERP need an explicit rule for who owns each kind of data. Specify which system creates customer records, which calculates prices and how availability reaches the buyer. Update frequency and accuracy are different: frequent checks will not fix an incorrectly defined business rule.
Follow an order from end to end
Use a test order to check the customer, products, quantities, terms and totals in both systems. Then test a rejection and a delayed response. The portal should show a clear status without confirming an order the operation has not accepted. Following the whole journey tells you more than a list of connectors.
Prevent duplicate orders and unnoticed failures
Retrying a transaction should not create a second order. Agree on a unique reference, a record of exchanges and an owner for exceptions. Define what the team sees when the ERP does not respond. In CommerceUp projects, those decisions begin with the way the wholesale business and its systems work.
Put it into practice
- Define the system of record for each type of data.
- Document statuses and confirmations.
- Test rejections, delays and retries.
- Give the team a way to resolve exceptions.
The thinking behind this guide
A guide by Julián Medina. The scenarios are illustrative, not measured customer outcomes. Explore CommerceUp.