Getting an enterprise resource planning (ERP) system connected to a Shopify store is pretty straightforward. The real challenge is building an integration that stays reliable through inventory changes, order edits, system outages, API updates, returns, B2B pricing rules, and years of business growth and change. 

Shopify supports several approaches to ecommerce ERP integration, including prebuilt connectors, integration platform as a service (iPaaS) middleware, and custom API integrations. Each can be the right choice depending on the merchant and its technology stack.

Even before choosing a connector, there are questions you’ll need to ask yourself:

1. Which system owns each piece of data?

2. How should changes move between systems? 

3. What happens when they disagree? 

4. …And how will the business know when a sync silently fails?

In this blog, we’ll go over everything you need to know about successfully integrating an ERP with your Shopify store. From the decisions that need to be documented before development begins to ensuring the integration remains solid through the natural changes and growth your business will see over time. 

How Should Shopify Integrate with an ERP?

A good ERP integration architecture gives every important piece of data an authoritative owner. For example, your ERP could own SKUs, costs and inventory; Shopify might own the original ecommerce order and storefront-specific merchandising, while a PIM like Akeneo might own enriched product descriptions, specifications and digital assets.

Other systems can keep copies of all that information, but allowing multiple platforms to independently edit the same field creates too much risk for conflict. Ensure there is a single source of truth for everything, and decide which platform owns what before starting any integration. 

Shopify describes webhooks as a way to receive near-real-time data, but also warns that webhook delivery isn't guaranteed and events may arrive out of order. Because of this, Shopify recommends periodic reconciliation jobs to identify changes an integration missed. For production webhook delivery, Shopify recommends Google Cloud Pub/Sub and also supports Amazon EventBridge as alternatives to managing webhook delivery directly over HTTPS.

Decide which system owns your ecommerce data

As we mentioned earlier, it’s important to map out which app or service will own what kind of information long before you start working your ERP into the mix. There isn't one universal ecommerce system of record. Ownership often needs to be decided at the domain or even field level.

For example, your operational product data might live in the ERP, while enriched content, when applicable, should come from your PIM. The same applies to order information: Shopify can own the original transaction, while the ERP owns the downstream sales document. 

Consider product information: a retailer with a large catalogue might keep SKU, cost, and logistics attributes in its ERP, while Akeneo manages descriptions, specifications, images, and other enriched data. At Blue Badger, we’re familiar with setting up this type of architecture for clients, including Akeneo implementations and custom middleware that connects Akeneo with Shopify.

Should Shopify or the ERP own inventory?

For many ERP-led omnichannel businesses, the ERP or WMS should own physical inventory and available-to-sell calculations while Shopify receives the quantity appropriate for each Shopify location. What’s really important is ensuring your sync logic is sound, or you’ll quickly run into problems. 

Imagine an order reduces stock in Shopify. Middleware sends that reduction to the ERP. The ERP recalculates inventory and sends another decrement to Shopify. Without carefully designed Shopify inventory sync logic, both systems can end up reacting to one another instead of working from a single authoritative value.

Instead, a better, safer flow looks more like this: 

Shopify order → ERP processes demand → ERP calculates authoritative availability → Shopify receives the current sellable quantity.

Location mapping also matters. A warehouse, retail store and returns quarantine location might all appear in the ERP, but that doesn't mean every location should feed sellable inventory into Shopify.

Shopify's current inventorySetQuantities mutation includes compare-and-swap concurrency protection through changeFromQuantity. An integration can provide the quantity it expects to be changing from, allowing Shopify to reject the operation if another process has modified that quantity in the meantime.

If you’re in an industry like hardware, powersports, home goods, etc., where SKU counts can easily reach the thousands and multiple warehouses and stores are the norm, these rules become essential to keep everything in check. 

Native connector vs iPaaS vs custom Shopify integration

As we mentioned earlier, there isn’t a universally “best method” for a Shopify Plus ERP integration. 

Shopify currently groups common ERP architectures into prebuilt or certified connectors, middleware/iPaaS platforms and custom API integrations. Prebuilt connectors are generally best suited to standardized system pairings, while Shopify iPaaS can be useful when several applications need orchestration. Custom development gives businesses greater control, but also creates more software to maintain.

Before choosing Shopify middleware, ask: 

1. Can it support the required data ownership and sync directions?

2. Can it store durable Shopify-to-ERP ID mappings?

3. Can support staff identify one failed order and replay it safely?

4. Can it distinguish a temporary API timeout from an invalid SKU?

5. Can it stop stale inventory data from replacing newer information?

6. Can it support unusual B2B pricing, bundles, locations or legacy ERP workflows?

This will help you narrow down which method best suits your ERP implementation. 

Shopify NetSuite integration

Oracle's NetSuite Connector uses SKU values to match storefront items with NetSuite records and recommends keeping the SKU mapping consistent across product and order synchronization. Oracle also recommends keeping complex business logic in NetSuite rather than burying it inside connector mappings that can become difficult to troubleshoot.

For a Shopify NetSuite integration, validate item structures, location mappings, kits, refunds, fulfilment logic and pricing behaviour before assuming a standard connector covers the whole workflow.

Shopify Microsoft Dynamics 365 Business Central Integration

Microsoft's Business Central Shopify Connector can synchronize products, inventory, customers and Shopify sales orders. Its current tools also expose synchronization errors and conflicts and allow specific Shopify orders to be reimported after problems are corrected.

For any Shopify-Microsoft Dynamics integration, evaluate the recovery tools as carefully as you evaluate the list of entities the connector can synchronize.

Shopify SAP integration

For SAP environments, a Shopify SAP integration may involve SAP Integration Suite as the connectivity and orchestration layer. SAP currently provides a Shopify GraphQL Receiver Adapter to connect Integration Suite to Shopify's GraphQL Admin APIs.

The same ownership rules still apply, however. Middleware should move, transform, orchestrate, and monitor information without unintentionally becoming another authoritative source for business data.

Design your Shopify order sync logic

When designing your Shopify order sync logic, integration records should retain the Shopify order ID, corresponding ERP sales-order ID, synchronization status and relevant timestamps at minimum.

This will prevent a common failure scenario where Shopify creates an order, the ERP successfully receives it, but the middleware times out before receiving confirmation. If the middleware simply tries another "create order" operation, the ERP can end up with a duplicate.

Certain Shopify GraphQL mutations support or require idempotency keys so an uncertain request can be safely retried without executing the same logical operation twice. Shopify advises using the same idempotency key when retrying the same operation.

ERP-side integrations should implement equivalent safeguards, usually using a durable Shopify identifier as the external reference.

Customer-specific pricing integration for Shopify B2B

If you also run a B2B store on Shopify, you’ve got another ownership question to answer: where should negotiated prices originate? 

Shopify B2B supports company locations, catalogues and associated price lists, allowing different B2B buyers or locations to receive specific product assortments and pricing.

When contractual pricing is maintained in an ERP or dedicated pricing engine, that system will often remain authoritative while the resulting prices are synchronized into Shopify.

That said, keep the distinction between contractual pricing and storefront promotions clear. A promotional discount applied during checkout shouldn't automatically become the new price in the ERP. This type of customer-specific pricing integration can become much more sophisticated than a basic price feed. 

What Happens When a Shopify ERP Sync Fails?

Obviously, when adding an ERP system to Shopify, you should cover your bases and do your best to ensure the connected systems work together as expected, but you should still anticipate and plan for failures in most long-running integrations. 

Any production-ready integration needs a recovery workflow. This could be something similar to:

1. Receive and verify the Shopify event.

2. Check whether the event has already been processed. Shopify provides X-Shopify-Webhook-Id to identify individual webhook deliveries.

3. Store the event in a durable queue or log.

4. Validate mappings and required information.

5. Attempt the ERP operation.

6. Retry temporary failures using controlled backoff.

7. Refetch current data when a stale-state conflict occurs.

8. Move non-recoverable data or mapping errors to a visible exception or dead-letter queue.

9. Alert the responsible support team with enough context to diagnose the problem.

10. Correct the issue and safely replay the original transaction.

Note that retries and reconciliation serve different purposes. Retries recover operations that the integration knows failed, while reconciliation can uncover events or updates the integration never received. Shopify recommends reconciliation jobs because webhook deliveries can be missed or mishandled.

How Often Should Shopify and an ERP Reconcile Data?

This is another area where there isn’t necessarily one single correct answer for every merchant. 

For time-sensitive information such as orders and inventory, a good architecture generally combines event-driven real-time data synchronization with frequent delta checks and a broader scheduled reconciliation.

As a starting point, orders, fulfilment, and returns/refunds can be event-driven, checked through frequent delta reconciliations, and then subject to a broader nightly reconciliation. B2B pricing, financial data, and slower-changing product information may suit scheduled or daily checks.

That said, high-volume businesses might need tighter controls, while slower-moving product data can likely tolerate longer windows. You just need to ensure that your reconciliation process is independent of the normal sync path. After an ERP outage, middleware deployment or mapping change, teams should also be able to immediately run a targeted reconciliation.

Conclusion

A successful Shopify Plus ERP integration is just as much an exercise in governance as development. 

Every important field needs an owner, every integration path needs a defined direction, and every failed transaction needs somewhere visible to go. This becomes even more important as your ecosystem grows to include things like Shopify POS, B2B, a PIM, warehouse systems, multiple locations, and custom integrations/applications. 

For merchants planning a new Shopify ERP integration or dealing with unreliable syncs in an existing environment, we at Blue Badger can help map system ownership, evaluate native connectors and iPaaS platforms, build custom Shopify middleware, and provide ongoing integration support across Shopify, POS, PIM, B2B and ERP environments. Get in touch with us today to learn more.