Skip to main content

What we found and fixed for ecommerce brands. Learn more about what we found and fixed for ecommerce brands

All resources

Guide16 min read

Shopify ERP Integration: How It Works and How to Choose

Shopify ERP integration is the connection that moves orders, stock, customers and money between your Shopify store and the system that runs purchasing, inventory and accounts. It can fail quietly: an order goes missing, a stock count drifts, and nobody notices until month end. This guide covers when a store needs an ERP, what syncs, why orders stop syncing, how to choose between a connector, middleware and a custom build, how long it takes, what drives cost and how to choose a partner.

By Maksudur Rahman, FounderPublished Last reviewed

Key takeaways

  • An ERP integration moves orders, stock, customers and money between Shopify and your system of record, and breaks quietly when nobody owns it.
  • A store needs an ERP for back-office complexity such as locations, purchasing and several legal entities, not for storefront traffic.
  • Pick the method by how standard your flows are: a connector first, middleware when several systems share data, custom only when nothing fits.
  • Orders go missing for specific, checkable reasons. Shopify says webhook delivery isn't always guaranteed, so run a daily reconciliation count.
  • Choose a partner on proof for your own ERP and flows, and ask for a read of your data before a proposal.

What is Shopify ERP integration, and what does it sync?

Shopify ERP integration keeps your store and your ERP (enterprise resource planning system) agreeing on the same orders, stock and money. Without it, inventory counts would have to be updated manually in both the ERP and the ecommerce application. Together, ERP and Shopify can exchange orders, inventory, customer, and financial data between systems.

Shopify's table lists the core flows. Shopify's advice is to agree on sync frequency for each data type.

The core data flows between Shopify and an ERP, with Shopify's sync pattern for each
FlowSystems connectedData that movesSync pattern
Order management and fulfillmentEcommerce platform, ERP, WMS, 3PLOrders, addresses, tracking numbersReal time, event-triggered
Inventory syncERP, ecommerce platform, point of saleStock levels by locationReal time or scheduled
Financial recordsEcommerce platform, ERPInvoices, payments, refunds, taxReal time or daily batch
B2B order intakeEDI network, ERP, ecommerce platformPurchase orders, invoices, shipping noticesBatch or real time
Customer recordsEcommerce platform, ERP, CRMContacts, order history, credit termsReal time

Source: Shopify Enterprise, ERP Integration: Methods, Benefits, and Examples

Who owns each field?

Every field needs one owner. When two systems can both edit a price or a stock count, whichever wrote last wins by accident. Write down who owns each data type and what happens when they disagree. This table is our recommendation, not a standard. A stock number can also be wrong with no error anywhere, as the phantom stock guide shows.

A system of record for each data type, with a rule for disagreements (our recommendation)
DataOwnerRule when the two systems disagree
Product master, SKU and unit costERPCreate a new SKU in the ERP first, then push it to Shopify.
Selling priceOne system, your choicePick one. A change in the other system is overwritten on the next sync.
Available to sellERP count, fed to ShopifyShopify says incoming inventory isn't available to sell until it has been received, so an open purchase order never counts.
OrderShopify until accepted, then ERPAfter export, edits happen in the ERP and flow back as fulfillment and tracking.
CustomerShopify for contact details, ERP for credit termsThe ERP receives the record and never creates a second customer for one email.
RefundShopify, with the journal entry in the ERPRefund once, in Shopify. The ERP gets the accounting entry, not a second refund.

When does a Shopify store need an ERP?

A store needs an ERP when back-office complexity, not storefront traffic, is what breaks: stock in several places, purchasing outside Shopify, or a month-end close that waits on exports. If the problem is conversion or slow launches, an ERP will not help.

Signs an ERP may help

Shopify lists several signs, five of which are below. We add two more.

  • Inventory spread across multiple locations.
  • Complexity in procurement.
  • Issues with manufacturing or wholesale operations.
  • Difficulties with multi-entity finance.
  • Lack of unified operational reporting.
  • Purchase orders that live in spreadsheets.
  • The same order typed into two systems.

A checkable trigger: your location limit

Shopify caps active locations by plan. Its help center lists 2 on Starter, 10 on Basic, Grow and Advanced, and 200 on Shopify Plus. If your stock lives in more places than your plan allows, you have outgrown the default setup.

Signs you do not need one yet

Shopify itself lists signs that the commerce platform is the real problem: a low storefront conversion rate compared with your benchmark, slow product launches despite effective project management, and heavy manual work during merchandising or new promotions.

One consultancy puts it bluntly: "Most brands at that point don't need an ERP. They need inventory software, a defined source of truth for stock, and clean SKU data."

Rushing is risky. Shopify quotes Gartner: by 2027, more than 70% of recently implemented ERP initiatives won't fully meet their original business case goals, and as many as 25% will fail catastrophically.

Try a lighter fix first, or look at an ERP (our guidance)
SymptomTry this firstERP signal
Stock counts drift between channelsOne owner for the count, clean SKUs, an inventory appSeveral locations, with purchasing outside Shopify
Manual steps after every orderA workflow tool such as Shopify Flow, n8n or MakeThe steps reach into finance, purchasing or a warehouse system
Month-end close waits on exportsA scheduled accounting syncSeveral legal entities or currencies to consolidate
Reports disagreeOne written definition per metricNo single system holds purchasing, stock and finance
Low conversion or slow launchesFix the storefrontNone. An ERP is the wrong tool

Connector, middleware or custom build: which should you use?

Start with a connector if one exists for your ERP and your flows are standard. Use middleware when three or more systems share the data. Build custom only when nothing else fits.

Three ways to connect Shopify to an ERP, summarised from Shopify's comparison table
MethodCostTime to deployMaintenanceLikely use case
Native connector (vendor-built)Low: often included with SaaS licensesFast: out-of-the-box connectorsLow: the vendor manages core updatesStandard pairs, like Shopify and NetSuite
iPaaS (middleware)Medium: subscription, pays for usage and flowsShort: prebuilt connectors cover standard flows, but mapping remainsLow to medium: the provider handles upgradesReal-time sync across several systems, such as ERP, WMS and CRM
Custom integrationHigh: costly build plus ongoing engineeringLong: multi-month, with coding and QAHigh: every API change requires manual recodingNiche legacy systems with no connectors

Source: Shopify Enterprise, ERP Integration: Methods, Benefits, and Examples

Connector: when your flows are standard

Shopify says native integrations often cost nothing beyond your existing subscription, while custom builds can cost far more. That is why a connector comes first. NetSuite's connector automatically syncs product, pricing, inventory, sales order and fulfillment data between NetSuite and Shopify, and its plans differ, so check the vendor's page. Microsoft ships a Shopify connector for Business Central.

The limit: a connector maps to the vendor's data model. Unusual pricing, bundles and wholesale terms are where connectors run out.

Middleware: when several systems share the data

Middleware sits between the systems. Celigo describes its iPaaS as the middleware layer that connects Shopify with leading ERP platforms, supporting both prebuilt and custom integrations. Choose it when your ERP, a 3PL and a helpdesk all need the same order data.

Custom build: when nothing fits

Custom builds avoid subscription fees but are costly to maintain, and Shopify says they are best reserved for niche systems with no alternatives. The wrong method can lead to brittle code that breaks with every update.

The cost people forget is platform change. Per Microsoft, Shopify releases a new API version every three months and supports each version for 12 months. A Business Central connector released in April 2026 relies on API version 2026-01, which is accessible until December 31, 2026. Whoever owns the integration owns that calendar.

What about Odoo and other ERPs?

We build and connect Odoo setups for sales, inventory and support data, and link them to the tools around them. Morsegrid is an Odoo Partner. See the integrations page.

Third-party Shopify connectors for Odoo exist on the Odoo Apps Store. One listing says it will connect Shopify to Odoo and sync everything automatically, and also warns that Odoo Online does not allow third-party apps and is not supported. Check which Odoo edition you run before you pick a connector.

Why do Shopify orders stop syncing with your ERP or accounting software?

Check the sync log first, then the order itself. Seven of these eight causes come from Microsoft's Business Central pages and Shopify's own help and developer docs. The SKU row is our own view.

Eight reasons orders do not sync, and how to check each
CauseWhat you seeHow to check
The order is archivedThe order is in Shopify and missing in the ERPPer Microsoft, orders might be archived in Shopify and the connector can't import archived orders.
The order is older than the last sync dateOld orders are missing, new ones arriveThe connector only imports orders created or modified after the last sync.
Something cannot be mappedThe order arrives with an error, or no sales document is createdOpen the order. The error reads "Not everything can be mapped", and the result is recorded on the Shopify order instead of an error dialog.
A missing or duplicate SKU (our view)Items fail to match, or the wrong item postsSearch the SKU in both systems. One SKU, one item. This row is our experience, not a vendor page.
A sync request takes too longA QuickBooks Desktop error on the Shopify sideShopify says it appears when a sync request takes longer than 30 seconds to receive.
The desktop app is closedError 0x8004041DShopify says it appears when the QuickBooks Desktop app isn't open to allow data sync. Open the app.
A webhook is missed or arrives out of orderSync works for days, then a gap appearsCompare order counts by date. Shopify says webhook delivery isn't always guaranteed.
Shopify throttles the requestsFailures in burstsIf the bucket fills, you get a throttle error and have to wait. Shopify's recommended backoff time is one second.

Sources: Microsoft Learn, Business Central troubleshooting, Shopify Help Center, QuickBooks Desktop, Shopify developer docs, webhooks and API limits

The fix that prevents the next one: reconcile every day

Shopify's developer docs say your app shouldn't rely on receiving data from webhooks, and advise reconciliation jobs that periodically fetch data. It also doesn't guarantee ordering. A connector should handle that already, so ask.

The simplest control is a daily count. Compare the orders created in Shopify yesterday with the orders received in the ERP, and alert on any mismatch. It catches the quiet failures no error message reports.

Check for duplicates before you re-key a missing order

Check first: the order may be queued, flagged with a mapping error or already posted under another customer. A manual copy creates a duplicate that finance must unwind.

How long does a Shopify ERP integration take?

It depends on which project you mean. Connecting an ERP you already run to Shopify is one project. Rolling out a new ERP is a bigger one. Panorama's 2026 sample had a median project length of nine months, and that is a full ERP implementation, not a connector.

For the integration alone, the only timelines we found come from a consultancy, so read them as one firm's view.

Timeline by approach, with whose figure each one is
ScenarioTypical durationWhose figure
A full new ERP implementationNine months (median)Panorama's 2026 sample, quoted by Shopify. A survey median.
Pre-built connectorDays to weeksAnchor Group, a Shopify consultancy. An opinion.
iPaaS (middleware) projectWeeks to monthsThe same Anchor Group page. An opinion.
Custom buildMonthsThe same Anchor Group page. An opinion.

Sources: Shopify Enterprise, ERP Budget and ERP Implementation, Anchor Group

What stretches the timeline

Data is the usual culprit. Panorama's 2026 report found that data issues drove 36.8% of timeline overruns. People matter too: almost a quarter of ERP implementation projects surveyed ran over schedule, and of those, 58% blamed organizational issues.

The fastest way to shorten a project is to clean your SKUs and settle field ownership before the build. Another consultancy warns: "Any vendor promising a few weeks is describing a licence activation, not an implementation.".

Phased or big-bang go-live

Phased go-lives are more common: 46.4% used some form of phased implementation, compared with 15.9% that used a pure big-bang implementation, per Panorama's 2026 data as quoted by Shopify.

A parallel run helps with stock and money. Shopify says a parallel cutover, sometimes called a shadow run, keeps the legacy ERP operating while the new system runs alongside it.

How organizations went live with a new ERP

Phased implementations were used far more often than a pure big-bang cutover.

  • Some form of phased implementation46.4%
  • Pure big-bang implementation15.9%

Source: Panorama Consulting Group 2026 data, quoted by Shopify Enterprise

A realistic sequence

Our working order for an integration. We give no durations: we have no neutral source for them.

  1. Map the data flows and name an owner for each field.
  2. Clean the SKUs and product data.
  3. Build the sync in a sandbox, not on live orders.
  4. Test the awkward orders: partial fulfillment, a refund, a cancellation, an exchange.
  5. Run old and new in parallel and compare the numbers.
  6. Go live, then watch the daily count closely.

What does a Shopify ERP integration cost?

Cost has four parts, and the connector is only one: the ERP licence, the connector or platform fee, the implementation work, and upkeep. Shopify's range is wide: native integrations often cost nothing beyond your existing subscription, while custom builds can cost far more. Connector plans differ, so read the vendor's page for current pricing.

We found no neutral source for consultant hourly rates or project fees, so we print none. Treat a rate table without a named source as a guess.

Overruns are common. More than a quarter of organizations surveyed said their ERP implementations had exceeded their project budgets, per Panorama's 2026 report. Shopify says the biggest reasons for overruns include additional technology that needed to be purchased, expanding the original project scope, and technical issues during integration.

How to get a quote you can compare

A quote is comparable only if every partner prices the same scope. Ask each for five things in writing.

  1. The flows in and out of scope, row by row.
  2. Who owns upkeep after go-live, including API upgrades.
  3. The test orders that must pass before go-live.
  4. What is documented, and who is trained.
  5. What happens when a sync fails, and who is told.

How we quote

We do not publish a price list. The pricing page explains how a quote happens.

How do you choose a Shopify ERP consultant or partner?

Choose on proof for your exact ERP and flows, not on a ranked list, which cannot know either. A good partner can show a read of your own data before proposing anything, and can answer six practical questions without a pitch.

Six questions that sort partners

Use these in a first call.

Questions to ask a Shopify ERP consultant, and what a good answer sounds like
QuestionA good answer
Have you connected this ERP and this kind of store setup before?Names the pattern, the tool used and what went wrong last time.
Who owns each data type, and what wins in a conflict?Shows a written table like the one earlier in this guide.
What happens when a sync fails, and who is told?Describes alerts, a daily count and a named person, not just a log file.
How will you test refunds, partial shipments and cancellations?Lists the test orders before they build.
Who maintains it when Shopify changes its API?Knows the quarterly API releases and says who owns the upgrade.
What do I own at the end?Documentation, a runbook and training for your team.

Ask for a diagnosis before a proposal

This is how we work. We read your Shopify, helpdesk and ERP data before we propose anything, work inside the tools you already use, write it down and train your team. A partner who quotes before looking at your data is guessing. Our guide to choosing an operations partner has the wider checklist, what an operations diagnosis looks at shows the method, and the ecommerce page shows what we cover.

Can the same consultant cover your help desk?

Yes, if they treat the helpdesk as a third system with its own owner. Gorgias documents it: if your integration fetches customer data from an external system, you can surface it in the ticket sidebar as a custom widget.

Ask who handles the handoff between the ERP and the helpdesk, such as a return that should create a credit memo.

How do the help desk, accounting and reporting connect to the same data?

They connect through the same system of record, and each breaks when the owner of a field is unclear.

Help desk

Order status, stock and tracking in the ticket sidebar mean fewer "where is my order" tickets. See where is my order automation and why order confirmation emails show up as helpdesk tickets. Our customer support workflows guide covers routing.

Accounting

Payouts, refunds, fees and tax need mapping to ledger accounts. An unmapped item is one documented reason a sync fails: Microsoft's troubleshooting page tells you to open the order and resolve the missing information when it reads "Not everything can be mapped".

Reporting and ERP data

One set of numbers needs one owner per field. If Shopify, the ERP and the ad platforms define revenue differently, no two reports agree. Settle the ownership table first. The ecommerce reporting guide covers profit per order, and the inventory management guide covers stock accuracy.

What does a 30-day plan to get your integration under control look like?

Four weeks can bring an existing integration under control. This is our framing, not a benchmark.

  1. Week 1: list every system that touches orders, stock or money, and name an owner for each data type.
  2. Week 2: clean the SKUs and write down the mapping for tax, payment methods and refunds.
  3. Week 3: switch on the daily reconciliation count and a mismatch alert.
  4. Week 4: write the failure runbook, test one refund and one cancellation, and train the team.

To see where your operations stand first, take the free 3-minute score. To turn the plan into procedures, use the ecommerce SOP template.

Frequently asked questions

When does a Shopify store need an ERP?
When back-office complexity is the problem, not storefront traffic. Shopify's signs include inventory spread across multiple locations, complexity in procurement, manufacturing or wholesale issues, multi-entity finance and no unified operational reporting. If the problem is conversion or slow launches, an ERP will not fix it.
How long does a Shopify ERP integration take?
A full new ERP implementation had a median of nine months in Panorama's 2026 sample. For the integration alone, Anchor Group, a consultancy, says days to weeks for a pre-built connector, weeks to months for iPaaS and months for a custom build. That is one firm's opinion.
Why are my Shopify orders not syncing with QuickBooks or my ERP?
Check for archived orders, an order older than the last sync date, an item or tax that cannot be mapped, a QuickBooks Desktop request that took longer than 30 seconds, or a missed webhook, because Shopify says delivery isn't always guaranteed.
Should I use a connector, middleware or a custom build?
Start with a connector when your flows are standard. Shopify says native integrations often cost nothing beyond your existing subscription, while custom builds can cost far more. Use middleware when several systems share the data, and keep a custom build for niche systems with no alternatives.
Can a Shopify consultant connect our ERP and help desk too?
Yes, if they treat the helpdesk as a third system with its own owner. Gorgias documents that customer data fetched from an external system can appear in the ticket sidebar. Tell any consultant which ERP and helpdesk you use, and ask who owns the handoff between them.

If an integration is running and you do not trust the numbers, start with the daily count and the ownership table. If you want a second pair of eyes on your Shopify, helpdesk and ERP data, book a diagnosis call and we will read it before we propose anything.

How well does your store run?

Score six areas of your store, from stock to support, and see the three to fix first.

Take the Free Assessment About 3 minutes. Results instantly.