Quick answer: Most Shopify ERP integration problems come from three data objects (orders, inventory and customers) and four predictable failure patterns: inventory lag, order status that doesn't flow back, pricing that lives in the ERP, and returns. Fix them by naming one source of truth for each object, then choosing native, middleware or custom to match your volume and rules.
If you run Shopify or Shopify Plus alongside an ERP such as NetSuite or Business Central, you'll probably recognise one of these: a product that sold out an hour ago is still on sale, customer service can't see whether an order has shipped, or finance spends days reconciling spreadsheets.
The good news? None of this is bad luck. Most integration projects overrun because the architecture was chosen before anyone understood the real failure modes. Get those clear first, and the right approach usually picks itself.
Let's break it down.
What breaks most often in a Shopify ERP integration?
Three data objects cause most of the trouble. If your integration gets these right, almost everything else follows.
1. Orders
Orders look simple until you add status changes, refunds, partial fulfilment and split shipments. A half-shipped order with one item refunded has to mean the same thing in Shopify, your ERP and your CRM, or your reporting and customer emails drift apart.
2. Inventory
Inventory breaks on three things: latency, multiple locations and reserved stock. Shopify thinks in "available to sell". Your ERP thinks in on hand, allocated, on order and in transit. If the mapping between the two is wrong, or slow, you'll oversell.
3. Customers
Duplicates, consent and B2B vs. B2C. Shopify might send "Jane Smith, Global Corp", while your ERP expects an account code and HubSpot expects a contact linked to a company. Get it wrong and you get duplicates, missing credit terms and mismatched marketing consent. (More in Shopify Plus and HubSpot CRM: why you need custom mapping.)
Why is my Shopify inventory out of sync with my ERP?
This is the question we hear most. It usually comes down to one of four ERP-specific patterns.
Inventory lag causing overselling
If your ERP only pushes stock to Shopify every so often, there's a window where both systems disagree. During a busy period, that window is where overselling happens. Shopify's own guidance puts it bluntly: "Inventory is where mistakes hurt fastest. Oversells lead to cancellations." (Shopify)
Multiple locations make it harder. Shopify assigns inventory to a location, and your location fulfilment settings affect which items show as out of stock and which can oversell (Shopify Help Center). If your ERP warehouses don't map cleanly to Shopify locations, the numbers won't either.
Order status not flowing back
Orders usually flow from Shopify into the ERP without much fuss. The return journey is where things go quiet: fulfilment, tracking and cancellations made in the ERP or warehouse never reach Shopify or HubSpot. The result is "Where's my order?" tickets and the wrong post-purchase emails.
Pricing that lives in the ERP
For B2B brands in particular, contract prices, customer-specific discounts and price lists often live in the ERP. Shopify notes that B2B pricing is commonly calculated in the ERP and applied by Shopify at checkout (Shopify). If your integration can't carry that logic across, someone ends up keeping two price lists in step by hand.
Returns and credit notes
Returns are the scenario that gets tested last and breaks first. A refund in Shopify needs to become the right credit note in the ERP, with stock put back in the right place, or finance and inventory both end up wrong. Shopify's own implementation checklist specifically calls out testing refunds, returns and fulfilment flows before launch (Shopify).
How do I stop overselling on Shopify?
Start with a source-of-truth decision, not a settings change.
- Pick one owner for stock. Usually that's the ERP or warehouse system, because it's the one that touches the boxes. Shopify displays what that system says.
- Map statuses on purpose. Decide exactly which ERP figure (free stock, for example) becomes Shopify's "available".
- Shorten the lag where it matters. Fast-moving or low-stock lines need event-driven updates, not an overnight batch.
- Reconcile regularly. Even good live syncs drift, so schedule a full comparison and correction.
- Check your out-of-stock setting. In Shopify, "Continue selling when out of stock" lets customers buy at zero or below. That's useful for pre-orders, but risky if it's switched on by accident (Shopify Help Center).
Where do native connectors stop?
Native connectors and certified apps are a sensible starting point. Shopify lists direct connectors for ERPs including NetSuite, Microsoft Dynamics 365 Business Central and Acumatica, designed for "standard setups with native compatibility" (Shopify).
They tend to stop at the same places:
- complex pricing and B2B price lists;
- multi-warehouse and reserved stock;
- returns logic and credit notes;
- custom fields your business relies on.
Latency and error handling matter too: how often does it sync, and who finds out when a record fails? More on this in why Shopify Plus integrations with Xero and HubSpot aren't simple.
Native connector or custom integration?
There are three routes, and each has its place. This is the short version of the build vs. buy vs. hybrid matrix in our decision guide.
| Approach | Best when | Watch out for |
|---|---|---|
| Native connector | Volume is moderate and your requirements are standard | Pricing, multi-warehouse, returns and custom fields |
| iPaaS or middleware | Complexity is moderate, or several systems need to talk | Ongoing subscription costs and who owns the mappings |
| Custom integration | Failure modes are well understood, and your volume or rules justify it | Needs clear specs, monitoring and support after go-live |
To decide, weigh four things:
- Your order volume and peak load.
- Whether you truly need real-time, or near-real-time is fine.
- How complex your pricing, inventory and fulfilment are.
- The total cost of ownership over 2–3 years, not just the build cost.
Download the Shopify–HubSpot–ERP Integration Decision Guide.
What Shopify ERP integration patterns actually hold up?
The integrations that keep working share four habits.
- A clear source of truth for each object. Inventory, orders, customers and pricing each have one named owner. Shopify's guidance says the same: decide which system owns inventory, orders, pricing and customer data (Shopify).
- Idempotent, retryable syncs. If a message is sent twice, nothing is duplicated. If a system is down, the update waits and retries rather than disappearing.
- Monitoring and alerting from day one. You hear about a failed order sync before your customer does.
- A staged rollout. Customers first, then orders, then inventory, so each layer is proven before the next depends on it.
And if HubSpot is part of your stack, the same rules apply to the HubSpot Shopify integration: decide whether Shopify, HubSpot or the ERP owns each customer field, so your CRM doesn't become a third version of the truth. Here's how we approach custom Shopify–HubSpot integrations.
What should I ask an ERP integration partner?
Before you sign off a project, any ERP integration partner should be able to answer these clearly:
- What is the source of truth for inventory and order status?
- How are failures and retries handled?
- What does monitoring look like after go-live?
- What is the expected latency under normal and peak load?
If the answers are vague, that's your answer.
Frequently asked questions
Why is my Shopify inventory out of sync with my ERP?
Usually sync lag, unclear ownership of stock, or ERP statuses (on hand, allocated, in transit) that don't map cleanly to Shopify's "available".
How do I stop overselling on Shopify?
Make one system the owner of stock, map the right ERP figure to Shopify's "available", use event-driven updates for fast-moving lines and reconcile regularly.
Should I use a native connector or a custom integration?
Native suits moderate volume and standard requirements, middleware suits moderate complexity, and custom suits well-understood failure modes with the volume or rules to justify it. Compare total cost over 2–3 years.
What should I ask an integration partner?
Ask about the source of truth for inventory and order status, failures and retries, monitoring after go-live, and latency under normal and peak load.
How long does a Shopify ERP integration take?
It depends on how many systems are involved, how complex your pricing, inventory and fulfilment are, and how clean your data is. [Nick to confirm: TGA's typical integration timeline range, if you'd like one quoted] An architecture review gives you a realistic plan for your setup.
Get your Shopify ERP integration right first time
A Shopify ERP integration isn't a commodity install. It's a set of decisions about who owns your data and what happens when something fails. Make those decisions first, and the choice between native, middleware and custom gets much easier.
We're official Shopify and HubSpot partners, and we build custom Shopify, HubSpot and ERP integrations for UK brands that need their systems to stay in sync. No hard sell. If a native app will do the job, we'll tell you.
Book an integration architecture review, or download the Shopify–HubSpot–ERP Integration Decision Guide to work through it with your team first.
