Mon – Sat: 9:00 AM – 7:00 PM IST
Integrations

ERP and Shopify integration explained

Which data moves in which direction, where the conflicts are, and what has to happen when the connection drops.

In short

A Shopify integration connects the storefront to the ERP so orders flow in and stock, pricing and fulfilment status flow out. The ERP remains the system of record for inventory and finance; Shopify is the sales channel. The hard parts are not the API calls — they are deciding which system owns each field, and what happens when one of them is unavailable.

Why It Matters

Why this matters in practice

Most integrations are specified as a list of things to sync and discover the real questions later. Who owns the price when it differs? What happens to an order received while the ERP is down? If stock sells out between sync cycles, who absorbs the oversell? Answering these before building is the difference between an integration that runs quietly and one that needs daily attention.

Orders flow in automatically instead of being re-keyed
Stock positions stay aligned, reducing oversells
Fulfilment and tracking flow back without manual updates
Finance posts from one source rather than reconciling two
How It Works

How it works in practice

1

Orders into the ERP

New orders create sales orders, with customer matching or creation, tax treatment and payment status mapped correctly.

2

Inventory out to Shopify

Available-to-promise pushed on a schedule or on change. The interval is a commercial decision about oversell risk.

3

Products and pricing

Usually ERP-owned, pushed outward. Deciding this clearly prevents the two systems disagreeing about price.

4

Fulfilment and tracking

Despatch in the ERP writes fulfilment and tracking back, which triggers Shopify's customer notification.

5

Returns and refunds

Often the least-specified flow and the one that causes the most reconciliation work later.

Worked example

A worked example: the duplicate order problem

An integration imports orders by webhook. It works for weeks, then a network blip causes Shopify to retry a delivery it believes failed. The ERP receives the same order twice and creates two sales orders. Both get picked. The customer receives two parcels.

This is not an edge case — webhook delivery guarantees are at-least-once by design, so retries are normal operation rather than a fault. Any integration that assumes each message arrives exactly once will eventually duplicate. The fix is idempotency: store the Shopify order identifier against the ERP sales order and check for it before creating anything, so a repeat delivery is recognised and acknowledged rather than processed.

Two related habits belong in the same design. Acknowledge the webhook quickly and process asynchronously, because slow responses cause the retries in the first place. And reconcile daily by polling for orders in a window and comparing against what the ERP holds, so a genuinely missed webhook is caught the next morning rather than at month-end.

Key terms

The vocabulary, briefly

Term What it means
Webhook A callback Shopify sends when an event occurs, so the ERP learns about an order immediately.
Variant A specific purchasable version of a product — size, colour — and the level that maps to an ERP item.
Fulfilment The Shopify record of goods shipped, usually written back from the ERP with tracking.
Idempotency Handling a repeated message without creating a duplicate. Essential, because webhooks retry.
Rate limit The cap on API calls per interval. Integrations that ignore it fail under load, not in testing.
What Goes Wrong

Common mistakes worth avoiding

No single owner per field

If both systems can change price or stock, they will, and the last write wins silently.

Sync interval too long

A long interval means overselling. Shorten it on fast-moving lines or push on change.

No retry and error queue

APIs fail. Without a retry mechanism and a visible error queue, failures are discovered by customers.

Ignoring tax edge cases

Tax treatment by destination and customer type is where order mapping most often goes wrong.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Orders in Shopify vs ERP The daily reconciliation. Any gap is a missed or failed message.
Duplicate orders created Idempotency failures. Should be zero; anything above it is a design fault.
Stock sync lag Minutes between an ERP stock change and the storefront reflecting it. Drives oversell risk.
API error rate by type Rate limiting, authentication and validation errors each mean something different.
FAQ

Questions we are asked about this

The ERP, in almost every case. It sees purchasing, production and all other channels; Shopify sees only its own sales. Push availability outward from the ERP.
As often as the oversell risk justifies. Fast-moving, low-stock lines may need push-on-change; a slow catalogue can tolerate scheduled sync.
The ERP, in nearly all cases, because it sees every channel including offline sales, returns, goods in transit and production. Shopify should receive an available-to-sell figure rather than compute one. Where businesses let the storefront own stock, the predictable outcome is overselling as soon as a second channel exists — and the second channel always appears eventually.
It depends on how close you run to zero. For deep stock, every fifteen minutes is fine. For scarce, fast-moving or single-unit items, push updates on change rather than on a schedule, because a fifteen-minute window is long enough to sell something twice. A common compromise is event-driven updates for low-stock items and scheduled batches for the rest, which keeps API usage reasonable.
Match on email rather than name, and expect to handle the same person appearing with variations — different casing, different addresses, guest checkout. Decide the de-duplication rule before go-live and apply it consistently, because merging duplicate customer records afterwards is tedious and touches financial history. Treat the storefront address as the delivery address for that order rather than as a master update, unless the customer explicitly changed it.
A packaged connector is faster and cheaper where your processes are close to its assumptions, and it is maintained for you against API changes. Custom is right where your fulfilment, pricing or tax logic is genuinely unusual. The question worth asking first is which of your requirements the connector cannot meet — often the list is shorter than expected, and the honest answer is a connector plus a small amount of custom logic rather than a build.
Related

Where to read next

Shopify and WooCommerce integration

Read more

Our eCommerce integration services

Read more

What is order to cash?

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.