A Shopify ERP integration isn’t just connecting two systems: it’s deciding which one owns each piece of data, which way it moves and what happens when something breaks. This guide covers what gets synced and in which direction, the Shopify API rules that shape the design, the most common mistakes, and when an app, an integration platform or custom code is the right call.
Before you connect anything: who owns each piece of data
The root problem is rarely technical: if two systems can edit the same field, sooner or later they disagree. Every piece of data needs an owner:
- The ERP owns the books: stock, costs, price lists, credit and invoicing.
- Shopify owns what the customer sees: photos, descriptions, collections and the order at the moment it’s paid.
- Shared records are split by field. A product can keep its SKU and price in the ERP and its description in Shopify; each system writes only its own fields.
That ownership map is the first deliverable of an integration done right.
Who owns each piece of data, and which way it moves
- Products and variants ERP Shopify SKU, unit, weight and base price; content stays in Shopify
- Inventory ERP Shopify Per location
- B2B price lists ERP Shopify Catalogs per company
- Orders, cancellations and refunds ERP Shopify By webhook
- Customers ERP Shopify Retail into the ERP; B2B companies into Shopify
- Shipments and tracking ERP Shopify From the ERP or WMS, on fulfillment
- Invoices and CFDI ERP Outside Shopify
What a Shopify ERP integration syncs, and which way
These flows show up in almost every project, with their usual direction; if you flip one, do it on purpose.
| Data | Direction | Cadence |
|---|---|---|
| Products and variants | ERP → Shopify; content stays in Shopify | Batched |
| Inventory | ERP → Shopify, per location | Near real time |
| B2B price lists | ERP → Shopify | Batched |
| Orders, cancellations and refunds | Shopify → ERP | Real time |
| Customers | Retail: Shopify → ERP. B2B companies: ERP → Shopify | On create or change |
| Shipments and tracking | ERP or WMS → Shopify | On fulfillment |
| Invoices and CFDI | Outside Shopify: ERP or invoicing system | Per order, or in Mexico’s global CFDI |
Products
The ERP owns SKU, unit, weight and base price; Shopify owns the content. The Admin API offers productSet, a mutation built to sync a product and its variants from an external source in a single call. Store the ERP’s ID in a metafield so you can reconcile even if a SKU changes.
Inventory
Shopify splits stock into states: on_hand (what’s physically at the location), available (what can be sold) and committed (units held by orders that haven’t shipped), which Shopify manages itself. The rule: the ERP’s physical count goes to on_hand and its available figure to available. Send an available number that already nets out store orders as if it were on hand, and Shopify subtracts committed units again—you count them twice. We go deeper in how to automate your inventory.
B2B pricing
In Shopify, your ERP’s per-customer or per-segment price lists become catalogs for your companies and their locations, with price lists that support fixed prices or percentage adjustments, quantity rules and volume pricing. On Basic, Grow and Advanced you get up to three active catalogs across your B2B markets; on Shopify Plus there’s no cap, and catalogs can be assigned directly to each company or location. If your ERP keeps a list per customer, that weighs on your plan.
Orders
This is the flow that hurts most when it breaks. Orders, cancellations and refunds reach the ERP by webhook (orders/create or orders/paid, depending on when you want them). The non-negotiable part: the ERP stores the Shopify order ID and refuses a second order with the same one; otherwise every retry is a duplicate.
Invoices and Mexico’s CFDI
If you sell in Mexico, the CFDI for a Shopify sale is issued by your ERP, your invoicing system or an app, and a SAT-authorized provider certifies it. There are two paths: an invoice in the customer’s name, and the global CFDI, which groups sales to the general public and, per the SAT’s filling guide, is due no later than 24 hours after the close of the operations it covers.
Real time or batch: each type of data has its own pace
“Everything in real time” is rarely right; each type of data should move at the pace its risk calls for:
- Event-driven: orders, cancellations, refunds and inventory for low-stock items. Shopify announces them through webhooks to an HTTPS endpoint, Google Cloud Pub/Sub or Amazon EventBridge.
- Batched: catalog and price lists, which change because someone decided so, not because of a sale.
And always, reconciliation: Shopify’s documentation warns that webhook delivery isn’t guaranteed and recommends periodic jobs that fetch whatever changed. A lost webhook with no reconciliation is an order that never reached your warehouse.
A day of syncing · illustrative
Event-driven
Orders Webhook, real time
Lost webhook · 13:42
Cancellations and refunds Webhook, real time
Inventory Near real time
Batched
Catalog and pricing When someone decides
Reconciliation Periodic job
Reconciliation picks it up · 15:00
The Shopify API rules that shape the design
Shopify’s documentation sets these conditions:
- GraphQL is the way forward. The REST Admin API has been legacy since October 1, 2024, and since April 1, 2025 every new public app must use only the GraphQL Admin API.
- Limits are measured in cost. Each query costs points based on the fields it requests, and each app gets a budget per store: 100 points per second on standard plans, 200 on Advanced and 1,000 on Shopify Plus. A sync that ignores this stalls right at peak sales.
- Bulk operations for volume. Initial loads and reconciliation runs go through
bulkOperationRunQueryandbulkOperationRunMutation, which run in the background, return a JSONL file and report back through thebulk_operations/finishwebhook. Since API version 2026-01, each app can run up to five bulk queries per store at once. - Inventory with concurrency control.
inventorySetQuantitiestakes the quantity you last read inchangeFromQuantityand fails if someone changed it meanwhile. Since 2026-04 it also requires an idempotency key (@idempotent), so a retry can’t apply the same change twice. - Webhooks with strict rules. Your endpoint has five seconds to respond; on failure, Shopify retries up to eight times over four hours and, if failures continue, removes the subscription.
X-Shopify-Webhook-Idlets you drop duplicates,X-Shopify-Triggered-Atlets you order events andX-Shopify-Hmac-SHA256lets you verify the signature. - Quarterly versions. Each API version is supported for at least twelve months, so any integration, bought or built, needs an update at least once a year.
Description
Hammer drill 1/2 in 850 W
Code
TAL-4120
Unit
PC
Weight
2.1 kg
Base price
$2,349.00
Stock by warehouse
Hammer drill 1/2 in 850 W
Managed by the ERP: read-only
The mistakes that keep showing up
- Two sources of truth. Someone fixes a price in Shopify “just for now,” and the next sync overwrites it. Whatever belongs to the ERP is read-only in Shopify.
- Overselling. It comes from the lag between a sale on another channel and the store, from mixing up on-hand and available, or from items down to one or two units at a sales peak. For those, the
safety_stockstate holds units back from available without removing them from on hand. - Duplicate orders. A webhook delivered twice, or a timeout after the ERP recorded the order, creates a second one if the ERP doesn’t recognize the Shopify ID.
- Retries without idempotency. A +10 adjustment applied three times adds thirty. Inventory travels as absolute quantities with concurrency control, or as adjustments with an idempotency key.
- Out-of-order events and silent failures. A cancellation processed before its order leaves a live order in the ERP that was already cancelled. Sort by event timestamp and send every failure to a queue someone reviews.
An integration proves itself the day something fails, not the day everything works.
Store first, notify second, and give every step a stable key: it’s the pattern behind our own contact flow, written up in why we took Make out of our own site.
App, iPaaS or custom integration: when each one makes sense
None is better in the abstract; each one buys you something different.
An App Store connector
An app that already talks to your ERP. Some ERP vendors publish their own: Microsoft for Dynamics 365 Business Central, and Oracle NetSuite, whose NetSuite ERP Connector syncs products, pricing, inventory, orders and fulfillment. It fits if your operation fits its model: whatever it can’t be configured to do, it won’t do.
An integration platform (iPaaS)
A middle layer with prebuilt flows, an editor, monitoring and retries; Celigo, for instance, offers a ready-made Shopify–NetSuite integration. It fits if you connect several systems and have someone to run it. The price: the subscription, and your logic living on someone else’s platform.
A custom integration
A service of your own, with your ownership map, rules and exceptions in code, plus tests, a log of every message and alerts. It fits if the rules are yours: per-customer price lists, several warehouses, B2B on credit, an on-premise ERP with no modern API, or a volume where every retry counts.
| Connector | iPaaS | Custom | |
|---|---|---|---|
| Control over the rules | Whatever its settings allow | High, within the platform | Full |
| Maintenance cost | Low: the subscription | Medium: the subscription plus someone to run the flows | The team that maintains the code |
| Latency | The connector’s | Event-driven or batched | Whatever you design for each type of data |
| Main risk | Your operation doesn’t fit its model | Critical logic outside your repository | Building it without tests or monitoring |
What changes with your ERP
- Microsoft Dynamics 365 Business Central: ships with Microsoft’s own Shopify connector, preinstalled on new sign-ups: products, inventory across locations, customers, B2B companies and orders.
- NetSuite: Oracle NetSuite’s connector, integrations such as Celigo’s and, for the rest, SuiteTalk, its REST and SOAP web services.
- SAP Business One: the Service Layer, a REST API over HTTP and OData that speaks JSON, is the natural base for a custom integration.
- Odoo: since version 19, the external API is JSON-2; XML-RPC and JSON-RPC are deprecated and go away in Odoo 22 (fall 2028), and earlier on Odoo Online, where external API access is limited to the Custom plan.
- Aspel and CONTPAQi: check with your reseller which version you run, where it’s installed and what interface it offers to other systems. That decides whether an existing tool is enough or you need a bridge service.
At Flouvia we design and build custom integrations on these principles: an ownership map, idempotency, reconciliation and alerts. If your ERP has a good connector and your operation fits it, that’s what we’ll recommend. For a second look at your integration map, get in touch.
Frequently asked questions
- Do I need Shopify Plus to integrate my ERP?
No. Plus gives you more headroom on the Admin API (1,000 points per second versus 100 on standard plans) and, for B2B, unlimited catalogs per company. Also check the plan requirements of the connector you choose. - Can Shopify be the source of truth for inventory?
If it’s your only channel, yes. If you also sell in stores, to distributors or from a warehouse that serves several channels, the source of truth is usually the ERP or the WMS. - Can I connect Aspel, CONTPAQi or another on-premise ERP to Shopify?
It depends on your version and how it’s installed. When no connector covers your case, the path is a bridge service that talks to the ERP through your version’s interface and to Shopify through its Admin API. - How is Mexico’s CFDI issued for a Shopify sale?
Through your ERP, your invoicing system or an app, and a SAT-authorized provider certifies it.