Shopify ERP Integration: Connector, iPaaS, or Custom Build
Shopify has no built-in ERP. Here's how direct connectors, iPaaS, and custom API builds compare, and which one fits your store's data flows.

Shopify doesn't include an ERP, so a Shopify ERP integration always comes down to one of three methods: a direct connector from the Shopify App Store, an iPaaS or middleware platform, or a custom build against the Admin API and webhooks. Which one fits depends on how standard your data flows are and how much in-house engineering capacity you have to maintain it.
What a Shopify ERP Integration Actually Involves
Structurally, a Shopify ERP integration is three things: the business systems themselves (your ERP, your Shopify store, and often a WMS or CRM), the tools that move data between them (APIs or middleware), and the integration method you choose to connect them (native, iPaaS, or custom). Shopify doesn't ship this connective layer by default — it's something every merchant running an ERP has to add.
The practical difference an integration makes is between event-based sync and manual re-entry. In an integrated setup, placing an order on Shopify updates the ERP the moment checkout completes, with no one retyping the order into a second system. For example, integrating NetSuite with a Shopify store means orders and customer data move from Shopify into NetSuite at checkout, and a connector can then push that same information on to a third-party logistics (3PL) partner for fulfillment. Without that integration, inventory counts would have to be updated manually in both the ERP and the storefront, and the gap between them widens as order volume grows.
The Three Integration Methods, Compared
Each method trades cost, deploy time, and ongoing maintenance differently:
- Direct (native) connector — listed on the Shopify App Store for a specific ERP, this is the lowest-cost, fastest-to-deploy option: setup is largely configuration rather than code, cost is often bundled into the ERP's own subscription, and the vendor maintains the core connection going forward. The tradeoff is coverage — a native connector only handles the data flows its vendor built, so you're limited to that vendor's roadmap.
- iPaaS (integration platform as a service) — a middleware provider that sits between Shopify and your ERP, handling data transformation and synchronization. It costs more than a native connector (typically a subscription priced on usage or flows) and needs real setup work — mapping, flows, sync schedules — but the provider handles security and upgrades, and it can cover several systems at once rather than one fixed pair. Shopify's B2B integration partners in this category include Pipe17 (which works with NetSuite, marketplaces, and third-party logistics providers), A2X Sync for QuickBooks and Xero, two separate Webgility connectors for QuickBooks Desktop and Online, and Patchworks (built for NetSuite or Brightpearl).
- Custom API build — built directly against Shopify's Admin API and webhooks. This is the highest-cost, longest-to-deploy, highest-maintenance option of the three, since every API change has to be handled by your own engineering team rather than a vendor. It's meant for exactly one situation: a data flow or business rule that neither a native connector nor an iPaaS template covers.
When a store's requirements genuinely don't fit a packaged option, a scoped custom build is the fallback — our Shopify integrations team builds against the Admin API and webhooks for stores whose workflows don't match a standard connector. Shopify's own B2B documentation recommends having a technical resource involved in setting up and launching any of these three methods, not just the custom build — even a native connector's field mapping and sync settings benefit from someone who understands both systems.
Which ERPs Have a Direct Connector Today
Shopify's Global ERP Program certifies connectors through a 100-checkpoint security and performance review before they're listed, and currently partners with Microsoft Dynamics 365 Business Central, Oracle NetSuite, Infor, Acumatica, and Brightpearl by Sage.
Separately, Shopify's B2B documentation lists the direct integrations it has confirmed compatible with Shopify B2B specifically, each syncing a different mix of data in both directions:
- Acumatica Cloud ERP — companies and customers, orders, inventory, products, payment terms and status, plus historical orders, fulfillments, and catalogs from Acumatica to Shopify.
- Microsoft Dynamics 365 Business Central — companies and customers, orders, products, fulfillments, and payment status, plus historical orders, inventory, and catalogs from Business Central to Shopify.
- NetSuite ERP Connector — orders, catalogs and price lists, payment status, and refunds, plus fulfillments, inventory, and products from NetSuite to Shopify.
- Fulfil — companies and customers, orders, PO numbers, fulfillments, payment terms and status, products, catalogs and price lists, and refunds, with draft orders and inventory syncing from external systems to Shopify.
- QuickBooks Online — companies and customers, payment terms and status, inventory, and products, plus historical orders, order updates, PO numbers, catalogs, and refunds from Shopify to QuickBooks.
- Syndigo PIM Connector and Akeneo PIM — both narrower, product-information-management-focused connectors syncing products and catalogs in both directions rather than orders or payments.
One caveat worth checking before you commit to any of these: not every App Store integration is fully compatible with Shopify B2B's companies and catalogs features. If a provider hasn't properly implemented the B2B APIs or Customer Accounts, B2B pricing and customer data may not map correctly, so it's worth confirming compatibility directly with the provider if you run a B2B store. For a closer look at how these certified options compare against each other, see our breakdown of the best ERP options for Shopify stores.
How the Custom API Path Actually Works
A custom integration runs on two Shopify mechanics. The Admin API handles requests your systems make — reading an order, updating an inventory level. Webhooks handle the reverse: Shopify sends a notification to your endpoint the moment something happens in the store, scoped to a named topic. The orders/create topic fires when a customer checks out; inventory_levels/update fires when stock changes. Subscribing to the relevant topics means your integration reacts to events as they happen instead of polling the Admin API on a schedule to check whether anything changed. Webhook subscriptions are scoped only to the app that registers them — another app installed on the same store can't view, modify, or delete a webhook subscription that isn't its own, which matters if a store runs more than one integration against the same data.
One detail matters for anyone starting a build today: the REST Admin API became a legacy API as of October 1, 2024, and as of April 1, 2025, all new public apps must be built exclusively on the GraphQL Admin API. A custom integration started now should be built on GraphQL from the outset rather than the REST endpoints older tutorials still reference. Our walkthrough of a Shopify-NetSuite integration build covers what this looks like in practice for one of the more common ERP pairs.
Syncing Data in Bulk Instead of Record-by-Record
For a large product catalog or years of order history, record-by-record API calls aren't practical. The GraphQL Admin API's bulk operations are built for this, and they come with specific limits worth planning around:
- Bulk operations are only available through the GraphQL Admin API — they can't be run against the Storefront API.
- In API version 2026-01 and later, each app can run up to five bulk query operations simultaneously per shop. In versions before 2026-01, each app could run only one operation of each type — bulkOperationRunQuery or bulkOperationRunMutation — at a time per shop.
- A bulk query has to complete within 10 days; after that, Shopify stops it and marks it failed. If a query runs into this limit, the fix is usually to reduce the query's complexity and depth rather than wait longer.
- Instead of polling for completion, an app can subscribe to the bulk_operations/finish webhook topic, which fires once a bulk operation completes, fails, or is cancelled.
Designing a sync job around these limits — batching by product count rather than running one query per SKU, for instance — is usually the difference between a sync that finishes overnight and one that times out.
Compliance Webhooks and the Security Baseline Every Method Shares
Whichever method you choose, Shopify requires every app to subscribe to three mandatory compliance webhook topics, configured in the app's configuration TOML rather than through the Webhook API: customers/data_request (requests to view stored customer data), customers/redact (requests to delete customer data), and shop/redact (requests to delete shop data).
These three topics are a baseline every app has to meet, not a certification, and they're distinct from the business-logic webhooks like orders/create that an integration subscribes to for its own sync logic — compliance webhooks exist specifically so merchants and customers can request or revoke data access, regardless of what the integration otherwise does. The Global ERP Program's certified connectors go through a separate, more thorough 100-checkpoint security and performance review before Shopify lists them — a considerably higher bar than the compliance webhooks alone, which is one reason the certified list stays short relative to the number of ERPs on the market.
Choosing the Right Method for Your Store
No single method is universally the right call — the fit depends on how standard your data flows are and how much ongoing maintenance your team can realistically own:
- A certified direct connector covers common, well-defined pairs like Shopify and NetSuite, with the vendor maintaining the core connection.
- An iPaaS platform suits stores syncing several systems at once — ERP, WMS, and CRM together — where no single native connector covers every leg.
- A custom build is reserved for workflows that neither a connector nor an iPaaS template addresses: a non-standard field, an unusual approval step, or a system with no App Store presence at all.
Whichever method you pick, the same groundwork applies across all three. Field mapping — matching each field in one system to its counterpart in the other — is where most of this work lives, because two systems rarely describe the same thing the same way: product identifiers, tax codes, date formats, and units of measure each need an explicit rule. Document every field that moves between systems and name the system of record for each one. Assign an owner to each integration and each data domain, so someone is accountable when a sync breaks. Agree on sync frequency per data type up front, since orders and inventory usually need to move in real time while reporting data can wait for a scheduled batch. And define error handling and alert thresholds before go-live, including what happens when the two systems disagree, rather than after the first failed sync surfaces as a customer complaint.
For B2B stores specifically, it's also worth asking a connector's provider directly whether they've implemented Shopify's B2B APIs and Customer Accounts, rather than assuming App Store presence is enough — Shopify's own documentation flags this as a common gap, not an edge case.
If you're weighing which of these fits your store, talk to our team.
Frequently asked questions
What's the fastest way to connect an ERP to Shopify?
Installing a certified direct connector from the Shopify App Store is the fastest path when one exists for your ERP — it needs no custom development and the vendor maintains the core connection. If your ERP isn't one of the Global ERP Program's certified partners, an iPaaS platform is typically faster to set up than a custom API build.
Do I need custom development to integrate an ERP with Shopify?
Not necessarily. A direct connector or an iPaaS platform covers standard data flows without custom code. Custom development against the Admin API and webhooks is only needed when your ERP has no direct or iPaaS integration, or when your business has a specific workflow that neither standard option addresses.
Which ERPs have direct, native Shopify connectors?
Shopify's B2B documentation lists direct integrations for Acumatica Cloud ERP, Microsoft Dynamics 365 Business Central, NetSuite ERP Connector, Fulfil, QuickBooks Online, Syndigo PIM Connector, and Akeneo PIM. Separately, the Shopify Global ERP Program partners with Microsoft Dynamics 365 Business Central, Oracle NetSuite, Infor, Acumatica, and Brightpearl by Sage.
Can I still build an ERP integration on Shopify's REST Admin API?
The REST Admin API became a legacy API as of October 1, 2024, and since April 1, 2025, all new public apps must be built exclusively on the GraphQL Admin API. Existing REST integrations keep working, but any new custom build should start on GraphQL.
How much data can a Shopify-ERP integration sync at once?
Through the GraphQL Admin API's bulk operations, each app can run up to five bulk query operations simultaneously per shop in API version 2026-01 and later (one per operation type in earlier versions), and each bulk query has up to 10 days to complete before Shopify marks it failed.