ERP and ecommerce integration means your store and your ERP share orders, inventory, prices, customers and fulfillment status automatically, with clear rules for which system owns each piece of data and what happens when the two disagree. Done well, nobody retypes a web order into the ERP, the store stops selling stock the warehouse no longer has, and finance closes the month from one set of numbers.
The money problem shows up first. Someone spends the morning copying orders. A popular item oversells on Friday and support spends Monday issuing refunds. A wholesale buyer sees retail prices. Each is a sync that is missing, too slow, or has no conflict rule.
Below: what should sync and how often, how B2B accounts change the job, where a CRM fits, connector app versus built integration, and how to catch a sync that has quietly stopped. Platforms are named only as examples.
Signs your store and ERP are not really connected
Orders are rekeyed by hand
Someone exports web orders or copies them line by line into the ERP. Every order waits for that person, and every typo becomes a wrong shipment or a wrong invoice.
Overselling during busy periods
Inventory updates once a day or on a manual upload, so a promotion sells units that were already committed to a wholesale order or a marketplace.
Wholesale buyers see the wrong price
Customer-specific price lists live in the ERP but never reach the store, so staff fix orders after they are placed or B2B buyers email instead of ordering online.
Customers ask where their order is
Tracking numbers and ship status sit in the ERP or warehouse system and do not flow back to the store, so the support inbox fills with status questions.
Two customer records for one buyer
The store, the ERP and the CRM each create their own customer, so sales, service and finance each see a different history for the same account.
What ERP and ecommerce integration should sync
Start with five data flows, because they carry most of the money and most of the errors: orders, inventory, prices, customers and fulfillment status. Products and catalog content are a sixth flow for some businesses, usually when the ERP is the master record for item numbers, weights and units of measure.
For each flow, write down three things before anyone picks a tool: which system is the source of truth, which direction data moves, and how fresh it needs to be. That one table is most of the scope. It also exposes the hard parts early, such as bundles that exist on the store but not in the ERP, or tax and discount lines the ERP expects in a different shape.
- Orders: store to ERP, near real time, including line items, discounts, tax, shipping and payment reference.
- Inventory: ERP or warehouse system to store, as often as your sell-through rate demands.
- Prices and price lists: ERP to store, on change, including customer-specific and tiered prices for B2B.
- Customers: usually created on the store and matched in the ERP, with account terms owned by the ERP.
- Fulfillment: ERP or warehouse to store, with tracking numbers, partial shipments and backorders.
Orders, inventory, pricing and customers in detail
Orders look simple until the exceptions arrive: edits after checkout, cancellations, partial refunds, split shipments, gift cards and invoice payment. Decide whether an edited order updates the ERP record or creates a new one, because finance will care.
Inventory is where speed matters most. Sync available to sell, not on hand: on hand minus units already committed to open orders, wholesale allocations and any safety buffer. If you sell the same stock on more than one channel, the buffer is your protection against the minutes between syncs.
Prices should almost always be owned by the ERP when the ERP holds customer terms. Promotional prices are the common exception: marketing sets them on the store, and the integration must not overwrite them on the next run. Customers need a matching rule, usually email plus company for B2B, so a returning buyer is linked to their existing account instead of creating a duplicate.
Sync direction, timing and conflict rules
Every field needs one owner. Two-way sync of the same field is where integrations go wrong, because when both systems change a value between runs, something has to win, and the default in many tools is whichever ran last. Write the rule down: the ERP wins on price and credit terms, the store wins on shipping address for a web order, and so on.
Timing follows the cost of being wrong. Orders should move within minutes, triggered by the store's webhook, a message the platform sends when an event happens. Inventory needs to be fast enough that you rarely oversell at peak, which for a fast-moving catalog means minutes and for a slow one may mean hourly. Product descriptions and images can sync nightly.
Many older on-premise ERPs cannot send events and only allow polling or a scheduled file export. That is workable, but it sets a floor on how fresh the data can be, and the design should say so.
B2B ecommerce ERP integration and wholesale accounts
B2B ecommerce ERP integration is a different job from retail, because the ERP holds the commercial relationship. A wholesale account has a price list, payment terms, a credit limit, sometimes several ship-to addresses and several buyers who may order on its behalf. The store has to show that account's price, respect its terms and route the order back to the right customer record.
The usual pattern: the ERP is the master for accounts, price lists and terms; the store receives them and keeps buyers logged in to the right company; orders flow back tagged with the account number and purchase order reference. Credit holds deserve a decision. Either the store blocks checkout for an account on hold, or the order is accepted and parked for a person in finance to release.
Keep a human in the loop for anything that changes money owed: new account approvals, credit limit changes and orders over a threshold you set. The integration should route those to a person with the context attached, not decide them.
CRM integration with ecommerce
CRM integration with ecommerce answers a different question from the ERP sync. The ERP needs the order to ship and bill it. The CRM needs it so sales and service see what an account bought, when, and how often, and can act on it: a reorder reminder, a lapsed wholesale account, a large first order worth a call.
Keep the CRM downstream of the store and the ERP for transactional data. Send it order summaries, lifetime value and last order date rather than every line item, and let it own contacts, deals, tasks and outreach. The HubSpot automation page covers that side.
Connector app or built integration
If your ERP and store have a well-reviewed prebuilt connector, and your process is close to standard, start there. For an ERP integration, Shopify merchants can often find a listed connector app for their ERP and set it up far faster than a build. The trade-off is that you accept its data model, its sync schedule and its handling of edge cases. When those fit, you should not pay anyone to build what already exists.
A built ecommerce API integration makes sense when the connector does not cover your rules: customer-specific pricing it cannot map, bundles and kits, several warehouses, a marketplace channel, or an ERP with no connector at all. Benian builds these as workflows in an automation tool such as n8n, which can be self-hosted, running in an account your business owns with credentials you hold. You can read every run, and your next developer can change it without starting over.
Some businesses use both: the connector moves standard orders and stock, and a small built workflow handles the one exception it cannot, such as wholesale price lists.
Monitoring and failure handling
Every integration fails sometimes: an API times out, a token expires, someone renames a product code. The question is whether you find out in minutes or at month end.
Failed records should go to a retry queue, not disappear. After a set number of retries, a person gets an alert naming the record and the reason. A daily reconciliation compares order counts and totals between the store and the ERP, and inventory spot checks catch drift before customers do.
- Measure orders synced versus orders placed, every day.
- Measure time from checkout to ERP record, and alert when it stretches.
- Track oversell incidents and manual corrections per week.
- Log every failed record with its error, so fixes are traceable.
What drives the cost of an ERP integration
Benian publishes no price for any integration; every engagement is scoped. The drivers are predictable, though. Cost rises with the number of systems involved, the number of data flows, how much of it is two-way, the quality of the ERP's API, how many exceptions your order process carries, and how dirty the existing product and customer data is.
Data cleanup is the most underestimated part. Duplicate customers and inconsistent SKUs must be fixed or mapped before anything syncs reliably. Running cost depends on the automation tool's pricing model, per execution or self-hosted, and any connector subscription you keep.
When not to hire Benian: if a standard connector fits your process and your volume is modest, install it and configure it yourself. If your ERP is about to be replaced, wait and integrate the new one. If you cannot yet say who owns price and inventory internally, settle that first, because no integration fixes an ownership argument.
How an ecommerce website integration with ERP gets built
- Map the data flows. List orders, inventory, prices, customers and fulfillment, with the owner, direction and required freshness for each.
- Check the APIs and the data. Confirm what each system's API allows, whether it sends events or must be polled, and how clean the SKUs and customer records are.
- Decide connector, build or both. Test whether an existing connector handles your rules. Build only the flows it cannot.
- Build and test with real exceptions. Run edited orders, partial refunds, split shipments, B2B accounts and a deliberate outage against a test environment before go-live.
- Go live with reconciliation on. Start with daily order and inventory reconciliation and alerts, and run the old manual check in parallel for the first weeks.
- Hand over and support. You keep the workflows, the logs and the credentials, with documentation that names each flow and its owner.