Blog

How to connect an eCommerce store to your ERP

Which data should flow between store and ERP, which approach to choose and how to avoid wrong stock levels and duplicate orders.

Published 17 November 2026 — Last reviewed: 17 November 2026 — Author: Roberto Di Stefano

To connect an eCommerce store to your ERP, first decide which system owns each piece of data, then choose how they talk: through the ERP's interfaces, through a ready-made connector or through file exchange. The rest is method: few flows, clear rules, an error log and a test on sample data before going live.

We write this from what we meet in projects: stores where orders are retyped by hand, stock that never matches, price lists that differ between site and ERP. The problem is almost always the same, and it is solved before any code is written. If you work with PrestaShop, see also our page on PrestaShop and ERP integration.

Which data should sync between store and ERP?

Four flows cover most cases: products, stock, orders and customers. Others, such as invoices and shipments, are added when needed.

  • Products and price lists: from ERP to store, because that is where codes, base descriptions and prices originate.
  • Stock: from ERP to store, at a cadence chosen from how fast it changes.
  • Orders: from store to ERP, with the status coming back (processing, shipped, invoiced).
  • Customers: in both directions, with a rule for duplicates and for business data such as VAT number and recipient code.

More active flows mean more points that can break. Start from the ones that save the most manual work and add the rest calmly.

Who owns the data: the ERP or the store?

For each piece of data there must be one system in charge. Sync errors almost always appear when two systems can edit the same field.

A rule that often works: the ERP owns codes, stock, price lists and invoicing; the store owns the cart, the order at the moment of purchase and the online account. Where the rule differs, for example SEO-enriched descriptions, write it down and stop the sync from overwriting them.

Direct integration, connector or file: which is better?

It depends on what the ERP offers and on how specific the way you sell is. There are three routes.

  • ERP interfaces (APIs or web services): direct, event-based exchange. The most solid choice when the ERP exposes them with clear documentation.
  • Ready-made connector or module: quicker to switch on, suited to standard flows. Check that it covers customer-specific price lists, payment terms and the custom fields you really use.
  • File exchange: acceptable for stable catalogues or older ERPs. Less immediate, and it needs checks on timing and incomplete files.

There is no answer that fits everyone. We start from what the ERP exposes and from the flows that matter, and only then pick the approach.

How do you avoid wrong stock and duplicate orders?

With three measures: a unique identifier for each exchange, a queue with retries and a log a person can read.

  • A unique identifier prevents the same order being created twice when a send is repeated.
  • A queue with retries stops a brief outage from losing orders or updates.
  • The log and an alert to a person make visible what did not go through, before a customer notices.

For stock, if the product is also sold on other channels, keep a safety margin and update more often the items that sell out fast.

Where do you start, in practice?

You start from the data map, not from code. Our path has five steps.

  1. Flow map: which data, in which direction, with which system in charge.
  2. ERP check: what it exposes, with which limits, who looks after it.
  3. Choice of approach: interfaces, connector or files, justified in writing.
  4. Test on a separate environment, with sample data and difficult cases: discounts, returns, business customers.
  5. Gradual go-live, one flow at a time, with the first days monitored.

If your store also sells to businesses, with dedicated price lists and payment terms, see our page on B2B eCommerce: the flows with the ERP weigh even more there.

When do you need a custom integration?

You need one when a standard connector does not cover your business rules: customer-specific price lists, multiple warehouses, orders that go through several approvals, poorly documented ERPs.

Before deciding, a snapshot of the current situation helps: platform, manual flows, points where data gets lost. That is what we do in an eCommerce audit, and it is often enough to see whether you need a new integration or a fix to the existing one.

Frequently asked questions on connecting eCommerce and ERP

Each piece of data has exactly one owner. As a rule the ERP owns product master data, stock, price lists and invoices, while the store owns the cart, the order at the moment of purchase and the online customer account. What matters is agreeing the rule in writing before the integration is built.

It depends on how fast stock changes and how costly a mistake is. For low-stock items or products sold on other channels, sync often or on events; for stable catalogues a slower cadence is enough. We choose from sales data, not from habit.

A well-built integration logs every exchange, retries failed sends on its own and alerts a person when something does not go through. Orders must not be lost: they wait in a queue and are processed again as soon as the connection is back.

Almost always, but the route changes. It depends on the interfaces the ERP offers and on the store platform. Before promising a solution we check what the ERP really exposes and with which limits.

Usually not. We build and test on a separate environment with test data, then switch on one flow at a time. The store stays online and go-live is planned for a low-traffic window.

Related reading

Want to understand how to connect your store to your ERP?

Request an analysis: we start from your flows and tell you which approach makes sense, with no promises.

No commitment: if now is not the right time, we will tell you.

Have a question about a specific case?

Write to us: we reply with a reading of your situation, with no sales steps.

No automatic quote: first we see whether we can help.