Shopify ERP integration

What moves between Shopify and an ERP

Whichever ERP sits behind the store, the same records move, and each has one owner.

A Shopify product holds up to 2,048 variants over three options. Stock is kept per location: 10 locations on the Basic, Grow and Advanced plans, 200 on Plus.

What Shopify's API allows

The budget

The GraphQL Admin API charges every query a cost in points and refills the budget at a fixed rate per second. A query that asks for more than 1,000 points is refused before it runs. A throttled call comes back as HTTP 200 with THROTTLED in the error body, so an integration that only looks at status codes misses it. The cost of each call is in the response:

{
  "extensions": {
    "cost": {
      "requestedQueryCost": 502,
      "actualQueryCost": 386,
      "throttleStatus": { "currentlyAvailable": 614, "restoreRate": 100 }
    }
  }
}

The REST Admin API has been a legacy API since October 1, 2024, and since April 1, 2025 new public apps have to use GraphQL. REST is still metered the old way: 2 requests per second with a bucket of 40, or 20 per second with a bucket of 400 on Plus. Products with more than 100 variants are only reachable through GraphQL. An integration still on REST has a migration ahead of it.

Shopify releases an API version every quarter and supports each for at least 12 months. When a version is retired Shopify answers with the oldest version still available, so an integration that nobody touches for a year is served by an API it was not written for.

Four patterns

Worked through for 50,000 variants. Reading them page by page takes 200 queries of 250 variants. At an assumed 500 points per page that is 100,000 points: 1,000 seconds on a standard plan, 100 seconds on Plus, with nothing left for orders in that time. A bulk operation reads the same 50,000 in one request, runs on Shopify's side, and returns a JSONL file whose link stays valid for a week. From API version 2026-01 an app can run five bulk operations of each type at once; before that, one.

Changes go the other way. A webhook reports a new order within seconds. Shopify waits five seconds for the answer, retries 8 times over 4 hours, and guarantees neither order nor a single delivery. So the webhook is treated as a notification, not as the record: the handler stores the ID, answers 200, and the queue does the work. A reconciliation run compares both sides and picks up what never arrived. Writes go out for changed records only: 300 changed stock levels are 2 calls of inventorySetQuantities. The cost model in full is in Shopify API rate limits.

Which ERP

Every ERP limits its API in its own unit. These are the numbers that decide how the other half of a Shopify ERP integration is built.

NetSuite. The account concurrency limit is shared by every integration on the account, and creating and saving a sales order in a script costs 30 governance units. The pair has its own page: Shopify NetSuite integration, with B2B on Shopify and NetSuite next to it.

Microsoft Dynamics 365 Business Central. Business Central online accepts only OAuth 2.0; access keys stopped working on October 1, 2022. Above 6,000 requests in five minutes a user gets a 429, and a request that runs longer than 8 minutes is cut off. Microsoft ships its own Shopify connector for Business Central online. Its documentation states its limits: it exports one price per product, only prices for quantity 1, and it cannot create variants for a product whose variant matrix combines two or more options. See Shopify Business Central integration.

SAP Business One. The Service Layer is an OData API with a login that returns a B1SESSION cookie, valid for 30 idle minutes. It returns 20 rows per page unless the request sets odata.maxpagesize. It runs on SAP HANA, and on Microsoft SQL Server since version 10.0 PL01. Older installations offer the DI API, a Windows COM library without multithreading, which means software running inside the customer's own network. Customers are BusinessPartners keyed by CardCode, items are Items keyed by ItemCode. See Shopify SAP integration.

Acumatica. Each license sets three API limits: sessions, concurrent requests and requests per minute, visible on the License Monitoring Console (SM604000). At half the per-minute limit Acumatica starts delaying requests. A request is declined when more than 20 are waiting or when it has waited 10 minutes. See Shopify Acumatica integration.

Sage Intacct. The XML API has one endpoint and needs a Web Services subscription with a sender ID. Sage recommends its REST API for new work and releases new objects only there. Concurrent requests are limited per company; above the contracted level the gateway answers 429. More on the Sage Intacct page.

Odoo. Odoo 19 introduced the JSON-2 API at /json/2/<model>/<method>. The XML-RPC and JSON-RPC endpoints are scheduled for removal in Odoo 22, in fall 2028. On Odoo's hosted plans the external API is available on the Custom plan only. More on the Odoo page.

What to sync and what to leave

Every field that is synced is a field somebody has to keep correct in its source. Three choices keep an integration small.

History stays where it is. An app reads the last 60 days of orders by default. Open orders, open returns and current stock go to the ERP at go-live; closed orders from past years stay queryable in Shopify.

Content stays in Shopify. ERP item descriptions are usually written for purchasing, in capitals and abbreviations. Titles, images and SEO fields are owned by the store and excluded from the sync, so that an item update in the ERP cannot undo a merchandiser's work.

ERP fields go to metafields only when the storefront shows them. An app can define 256 metafields per resource type, and metafieldsSet writes 25 per request. Material, country of origin and lead time belong in a metafield; the costing method does not. The note on what not to sync works this out per data type.

Do you need Shopify Plus?

The Admin API, bulk operations and webhooks are the same on every plan. Plus changes numbers, not capabilities.

Since April 2026 B2B companies, catalogs and net payment terms are available on Basic, Grow and Advanced as well. A company holds up to 10,000 locations, and a price list takes 250 fixed prices per request. An ERP with more than three price levels for B2B customers needs Plus, or a mapping that combines price levels into three catalogs. See customer catalogs.

Where Shopify ERP connectors and apps stop

A Shopify ERP app from the App Store, an iPaaS template and the connector an ERP vendor ships share one design: fixed flows with settings. Their documentation states the limits.

• One price. Microsoft's connector exports one price per product and ignores quantity breaks. A common NetSuite template takes one price level for the price and one for the compare-at price.
• Locations mapped, not allocated. Locations map one to one or many to one. Which warehouse serves which order, and how much each sales channel may see, is not a setting.
• Schedules instead of events. Order flows commonly run on a schedule with a lag of 10 to 15 minutes, and stock every 15 to 30 minutes.
• Flows tied to objects by ID. One template installs 30 saved searches in NetSuite and breaks when one of them is renamed.

Integration services from Shopify ERP partners configure those products. We build the integration itself, to your price model, your locations and your ERP's limits, and we run it. The technical comparison is in custom integration vs iPaaS.

When it goes wrong

A record that still fails after its retries is kept with its original payload and can be sent again once the cause is fixed. Before go-live the integration runs as a dry run that writes nothing and shows what it would change, and after that every run leaves a diff per record. That is the same for every e-commerce ERP integration we build; the Shopify side is described on the Shopify page, and EDI with retailers on Shopify EDI integration. Tell us which ERP you run.