Shopify ERP integration
An ERP integration connects your storefront with your back office so key data flows automatically instead of being retyped. Connect Shopify to your ERP to automate order processing and keep inventory accurate.
What syncs
-
Orders Shopify
Send orders to ERP to fulfillment / invoicing
-
Inventory ERP/WMS
Sync stock back to Shopify to prevent overselling
-
Products ERP/PIM
Keep catalog consistent; handle variants / bundles
-
Prices ERP
Align price lists, promos and currencies
-
Customers Shopify → CRM
Decide dedupe rules and identifiers
CHOOSE YOUR ERP
Shopify ERP integrations we build
Six systems, one connector platform. Each page below sets out the endpoints that ERP actually exposes, the data it can and cannot accept, and what a project on it looks like in practice. If yours is not on the list, the architecture is the same — tell us the system and we will confirm whether it can be reached.
Mid-market distributors and manufacturers on Sage 200 Standard or Professional. Orders, sales invoices, stock by warehouse and B2B price lists, with multi-company setups where each Shopify store maps to its own ledger entity.
Smaller catalogues and single-company accounts. Sage 50 has no public REST layer, so the connector reaches it through a secure on-site agent and moves orders and stock in scheduled batches rather than streaming them.
Multi-site, multi-entity groups on Sage X3 Version 12 and later. Its web services expose sales orders, deliveries, invoices and stock by site, so each Shopify order can be routed to the site that will actually ship it.
Dynamics 365 Business Central, cloud or on-premise. The OData and API v2.0 endpoints already cover customers, items, sales orders and posted invoices, which makes this the quickest of the six to put into production.
Ahora ERP in Spanish manufacturing and distribution. The integration runs over its web services or a staging database; production orders and stock reservations are the parts that need the most mapping work.
Factusol for small businesses that invoice from the desktop. There is no public API, so the connector reads and writes the Factusol database through an on-site agent on a schedule you set.
SAGE, WITHOUT THE CONFUSION
Sage 50, Sage 200 or Sage X3?
The three products share a name and very little else. They differ in how they hold stock, whether they expose an API at all, and how much of the integration has to run on your own hardware — and those three answers are what set the price and the timeline. Pick the wrong page and the numbers you read will be someone else’s.
Entry level. One company, desktop-first, no public API.
- One company, one warehouse in practice
- No public REST API: needs an on-site agent
- Scheduled batches rather than live events
- Comfortable below roughly 500 orders a month
Mid-market. Multi-company, hosted or on-premise, API included.
- Multi-company and multi-warehouse by design
- REST API on Standard and Professional
- Near real-time orders, polled stock
- Comfortable from 500 to 10,000 orders a month
Enterprise. Multi-site, multi-country, web services throughout.
- Multi-site, multi-entity, multi-currency
- Web services for orders, deliveries and stock
- Order routing by shipping site
- Built for volumes above 10,000 orders a month
HOW IT WORKS
How a Shopify ERP integration is built
01 · Map the data
Every field that has to travel is listed in both directions — order, line, tax, customer, product, stock — and each one is given an owner. Most integrations that fail do so because an ownership dispute was left undecided and surfaced in month three.
02 · Choose the transport
REST API, web services, database agent or file drop, depending on what your ERP genuinely exposes. This is the decision that makes the sync near real time or scheduled, and you get the answer before the project starts, not after.
03 · Build against your own data
The connector is configured against a copy of your real catalogue and a development Shopify store. Test orders travel end to end, including the awkward ones: refunds, partial shipments, cancellations and back orders.
04 · Reconcile the opening stock
Before go-live, quantities in Shopify and in the ERP are aligned once, by hand if that is what it takes. Starting an automated sync from an inaccurate baseline only propagates the error faster.
05 · Go live one flow at a time
Flows are switched on in sequence — usually orders, then stock, then catalogue — each with retries, an error queue and alerts. Nothing runs silently, and anything that fails is visible and replayable.
SCOPE, COST AND TIME
What it costs and how long it takes
There is no single price, and anyone who quotes one before looking at your ERP is guessing. Three things move the number: how many flows you need, whether the ERP offers a modern API or has to be reached through an agent, and how clean your product data already is.
A single flow — Shopify orders into the ERP, nothing coming back — on a system with a documented REST API is typically live in three to five weeks. The full set of flows on a multi-company or multi-warehouse setup usually runs eight to sixteen weeks, and most of that time goes on mapping and testing rather than on writing code.
The costs that catch people out are rarely the connector. They are the catalogue clean-up nobody budgeted for, the ERP licence module that unlocks the API, and the server that has to sit on your side when the ERP has no public endpoints. All three go into the estimate — including when the honest answer is that your current ERP version cannot do what you want without an upgrade. If you want the longer version, read how an ERP integration project runs end to end.
BEFORE YOU COMMIT
Six questions to ask any Shopify ERP connector
- Which ERP versions are supported, and what happens the day we upgrade?
- Is each flow real time, scheduled or webhook-driven — and what is the real latency?
- Who owns each field when Shopify and the ERP disagree about it?
- What happens to an order the ERP rejects: retry, queue, or silent loss?
- Can it handle partial shipments, refunds, credit notes and B2B price lists?
- Where does the data physically travel, and what does that mean for GDPR?
The fourth question is the one that separates connectors. If the answer is not a specific mechanism you can look at, the integration will eventually lose an order and nobody will notice until the customer calls. Ask to be shown the error queue before you sign anything.
FAQ
Frequently asked questions
Do I have to replace my ERP to connect it to Shopify?
No. The connector sits between the two systems and speaks whatever your ERP already exposes. An upgrade only becomes unavoidable when the version you run has no API and no supported way of reaching its database.
How real time is “real time”?
Orders normally reach the ERP within a minute of checkout, because Shopify pushes a webhook. Stock coming back is usually a scheduled job every few minutes: ERPs rarely emit an event when a quantity changes, so something has to poll them.
What happens if the ERP is down?
Messages queue and retry with backoff. Nothing is discarded, and the queue is visible, so a failed order is something you can see and replay rather than something you discover during a stock count.
Can it run B2B and B2C on the same store?
Yes, and it is one of the most common reasons to integrate in the first place. Company-level price lists, payment terms and tax rules live in the ERP; the connector applies them to the right Shopify customer or company record.
Do you connect a warehouse system too?
Yes. Stock and fulfilment often sit outside the ERP — see Shopify WMS and 3PL integration. The two coexist without fighting: the ERP stays the financial master and the warehouse system owns the physical count.
What about accounting and CRM?
If your finance team works in a separate package, start with Shopify accounting integration. If what you need is customer data rather than stock, start with Shopify CRM integration. The same platform runs all three.
Tell us your systems.