Shopify ERP Integration: Connector, iPaaS or Custom Build

If someone on your team still copies orders from Shopify into your ERP by hand — or watches inventory drift apart between the two systems — you already know the cost of not integrating: re-keying, oversells, and the quiet fear of double-counting revenue. The good news is that connecting an ERP like NetSuite, Dynamics 365 Business Central, Acumatica, SAP Business One, Epicor Prophet 21, or Syspro to Shopify is a solved problem. The real question is which of three paths fits your ERP, your logic, and your budget — and what each one honestly costs in the first year. This guide walks all three.

What an ERP Integration Actually Syncs

Before you compare tools, get clear on what actually moves between the two systems and, more importantly, which system is the source of truth for each piece of data. An integration isn't a magic two-way mirror — every field needs one owner, or the last write silently wins and your numbers drift.

Inventory is where source-of-truth discipline matters most. Once your ERP or a warehouse system manages stock across several locations, Shopify's locations have to map cleanly onto those warehouses so counts and order routing stay correct. Our guide to multi-location inventory on Shopify covers how that mapping and routing work once you outgrow a single stockroom.

Where naive syncs break

The place integrations fail is rarely the happy path — it's the order edit. When a customer changes an order, the two systems have to agree on the new reality, and off-the-shelf connectors are candid about where they can't. Microsoft's own Business Central documentation lists the failure modes plainly.

Celigo's NetSuite integration draws the same line from the other side: its documentation says an edited order only re-syncs while "the fulfillment process hasn't started for the order or specific line items." Once anything ships, the edit stops flowing. The lesson is universal — design for edits, refunds, and cancellations from day one, because the tools that skip them leave you reconciling by hand.

The Three Integration Paths

Almost every ERP-to-Shopify project lands on one of three paths. They differ in who builds and maintains the integration, what it costs, and how much control you keep. Find the row that sounds like your situation, then read that path's deep dive below.

Shopify itself acknowledges that ERP tooling doesn't fit neatly inside the admin — it's a named exception to the platform's usual "embed everything in the admin" rule.

Which Path Fits You?

You now know what syncs and how the three paths differ. Answer five questions about your ERP, your logic, and your team, and the quiz returns a route with a short blueprint — the app or API to reach for, the setup step that matters, and the source-of-truth rule to write down.

The Connector Route: First-Party & Certified Apps

If your ERP is on Shopify's certified list, start here. Shopify runs a Global ERP Program with five certified connector apps — a suite of certified enterprise resource planning apps that integrate directly with your store. The program launched in October 2021 and is still live as of July 2026.

Publisher and pricing from each app's Shopify App Store listing, verified July 2026. "Free to install" connectors still incur ERP-side charges billed by the vendor, separate from your Shopify invoice.

NetSuite

The NetSuite ERP Connector is published by Oracle NetSuite itself — a genuine first-party app, not a third-party bridge. It ships four pricing tiers: B2C Standard at $199.92/month, POS and B2C Premium at $249.92/month each, and a B2B tier at $916.58/month that adds invoice posting, subsequent payment handling, and B2B order and customer sync. The connector fee is billed separately from your Shopify invoice, and separately again from your NetSuite licence.

If you outgrow the first-party connector — say you need to orchestrate NetSuite alongside a 3PL and a marketplace — Celigo integrator.io is the common alternative, covered in the iPaaS section below. It imports orders and customers and syncs cancellations and refunds, with the fulfillment caveat noted earlier.

Dynamics 365 Business Central

Microsoft's Dynamics 365 Business Central connector is first-party and free to install— you need both a Business Central licence and a Shopify licence, with no separate connector fee. It syncs items, customers and companies, and imports orders with fulfillment tracking, all over the GraphQL Admin API. One caveat is worth flagging: it's online-only, not available for on-premises Business Central. It also shows why connectors carry a maintenance tax that custom builds handle differently.

A store on the October 2025 Business Central release that never upgraded has, as of today, already passed that connector's API end-of-support date. With a vendor connector, staying current means upgrading the ERP on the vendor's schedule; with a custom build, you control the upgrade cadence yourself — a real trade-off, not a winner.

Acumatica

Acumatica takes a different tack: its Shopify connector isn't a bolt-on you buy, it ships inside the Acumatica Retail Edition.

The connector syncs bi-directionally and in real time as orders are placed, covering product info, per-store inventory, and shipment tracking. Acumatica also markets its connector as the first in the ERP industry to support Shopify's B2B features — that's the vendor's own claim, not an independently verified fact, so weigh it as marketing. For mid-market deployments, one partner cites all-in costs of $2,000–$5,000/month plus a $30,000–$70,000 implementation, which are its figures, not a benchmark.

Brightpearl & Infor

The last two certified apps round out the program. Brightpearl by Sage is a retail operations system, free to install and the highest-rated of the five. The Infor eCommerce Connector links Infor's M3 ERP to Shopify and is free. Both are worth a look if you already run those systems, but neither is as widely deployed on Shopify as NetSuite or Business Central.

The iPaaS Route: Middleware Between Systems

An integration platform as a service (iPaaS) sits between your systems and orchestrates the data flow with pre-built connectors you configure rather than code. It earns its keep in two situations: when more than two systems have to stay in sync, and when your ERP has no certified Shopify connector but your logic is standard enough that a full custom build would be overkill.

Median figures are buyer-paid data from Vendr (linked below); Patchworks and Jitterbit publish no public dollar figures. Estimates and observed tiers, not market benchmarks — get a quote for your own flows.

The real numbers are sobering. Celigo's median buyer pays $14,787 a year across 253 recorded purchases, and Boomi's median buyer pays $45,147 a year. Patchworks prices by the number of systems connected and your operations volume; Alumio's entry tier starts around €499/month. That range is exactly why iPaaS is a middle path — more capable and more expensive than a connector, cheaper and faster than a bespoke build.

The Custom Build Route: Admin GraphQL API

When no connector fits — an exotic ERP, or order and pricing logic that no off-the-shelf app maps — you build directly against Shopify's Admin GraphQL API. This is the developer-led path: the most control, the most ownership, and the most responsibility. It's also the path that most often needs outside development help, because a custom integration is a real software project.

What a custom integration is made of

A production integration is built from a handful of Shopify primitives. Understanding them tells you why a credible quote is what it is — and why the cheapest bid is often the one that skips the safety net.

There's one more piece a good build plans for: backpressure. During an order spike, a naive integration that fires one API call per event will hit the rate-limit bucket — 1,000 points a second on Plus and start dropping work. A resilient build queues and buffers writes so a busy hour degrades gracefully instead of failing, which is exactly the kind of thing a bargain quote tends to leave out.

SAP Business One, Epicor P21 & Syspro: ERPs With No Certified Connector

Some of the most-searched ERPs have no first-party Shopify app at all. That doesn't mean you can't connect them — it means the route runs through middleware or a custom build rather than a certified connector.

SAP Business One is the clearest example. There is no App Store connector from SAP; the official route is SAP's own B1 Integration Framework — the middleware that lets Business One publish and consume data from external systems — which third-party Shopify apps then build on top of. Odoo, another ERP without a first-party Shopify connector, follows the same pattern of app-or-custom integration.

Cost & timeline

Custom-build pricing scales with scope. The tiers below come from agency estimates — useful for sizing, but single-source figures, not market benchmarks. Get your own quote before you budget.

Tiers from scmsoftwarelab (July 2026); a separate build put full custom ERP/PIM work at $15,000–$50,000+ plus $2,000–$5,000/mo ongoing. One chain-cited estimate puts a first-year Shopify-Plus-plus-ERP total at $100,000–$250,000 — a single second-hand figure, not a benchmark. Get your own quote.

A custom integration is one type of custom Shopify project among several, and the way you scope, staff, and price it follows the same playbook as any bespoke build. Our guide to custom Shopify development covers how those projects are scoped and where headless and Liquid fit — useful context before you commission an integration build.

What ERP Integration Costs in Year One

Put the three paths on the same year-one footing and the shapes are clear. A certified connector is mostly a recurring fee: NetSuite's B2C Standard tier at $199.92 a month works out to roughly $2,399 in year-one connector fees, with almost no setup. An iPaaS is a larger subscription — Celigo's median lands near $14,787 a year. A custom build front-loads a one-time cost, often $5,000–$15,000 for a production-grade sync, then carries maintenance. The estimator below opens on that $2,399 connector example so you can bend it to your own quotes.

One honest caveat the tool makes prominent: these are integration costs only. Your ERP licence — NetSuite, Business Central, Acumatica — is billed separately by that vendor and is usually the larger line. The estimator sizes the connection decision, not your total cost of ownership.

Do You Need Shopify Plus for ERP Integration?

A common assumption is that ERP integration — especially B2B — requires Shopify Plus. As of an April 2026 rollout, that's no longer true. Shopify made core B2B features available well below Plus.

Company profiles, up to three B2B catalogs, payment terms, volume pricing, and vaulted cards now work on the lower plans. What stays Plus-only is the high end: unlimited B2B catalogs, deposits and partial payments per fulfillment, and checkout customization. Plus also raises your API rate limit, which matters for very large syncs. The table shows where each plan lands.

Rate limits from Shopify.dev (Shopify for enterprise / Commerce Components reaches 2,000 pts/sec); plan prices in USD from shopify.com; B2B availability from the Shopify Help Center. Verified July 2026.

For the full picture of what Plus-native B2B unlocks — company accounts, price lists, and where it can replace an older ERP-era stack — see our guide to B2B on Shopify Plus. For ERP integration itself, the Admin API and core B2B run on any plan.

Red Flags in an ERP Integration Project

Whichever path you pick, the same handful of warning signs separate a project that runs for years from one you rebuild in six months. Scan these before you sign anything.

The Cutover Playbook

Going live is the riskiest moment, and the mistake is treating it as a single switch. The same staged approach applies whether you're integrating for the first time or replacing an existing connector — run the old and new flows in parallel against a reconciliation check rather than cutting everything over at once. Work the checklist top to bottom, and only tick a box when you can verify it.

When Does Integration Actually Pay Off?

Not every store needs an integration yet. Shopify deliberately publishes no numeric SKU or order threshold, because the trigger is operational, not a magic number. As Shopify's own enterprise material puts it, "as sales volume increases and inventory expands, inefficient and labor-intensive operating processes are hard to scale." The practical signals integrators cite are concrete: a month-end close that takes more than five business days, inventory the two systems disagree on that a person has to chase, or having to apologize to a customer because Shopify and your finance system disagreed on whether an order shipped.

At the other extreme, scale forces the custom path: one integrator notes that at 50,000 SKUs across 12 warehouses you're looking at roughly 600,000 inventory mutations a day — a volume only bulk operations and a purpose-built sync can handle (that's an integrator's observation, not an official Shopify figure). Between those poles, CSV imports are honestly enough — and if you're genuinely weighing a full replatform to Plus or an enterprise build rather than just an integration, that's a bigger decision covered in our guide to Shopify enterprise. One boundary worth naming: syncing sales into QuickBooks or Xero is accounting sync, a narrower job than a full ERP integration — don't conflate the two when you scope.

The Bottom Line

There is no single best way to connect an ERP to Shopify — there's the way that fits your ERP, your logic, and your team. Get the source-of-truth decisions right and design for order edits, and any of the three paths can run for years.

Frequently Asked Questions