Shopify ERP integration with SAP, Dynamics 365, Acumatica and Odoo

A Shopify ERP integration makes your store and your ERP agree on products, prices, stock, orders, fulfillment and money. Orders flow into the ERP. Items, prices, inventory and shipments flow back to Shopify. SAP, Microsoft Dynamics 365, Acumatica and Odoo each have connector options. A custom integration, or a custom app next to a connector, is what you need when your ERP is customized, you sell B2B with contract pricing, or the connector can't show you which records failed and why.

This page is the general guide. For NetSuite specifically, see the Shopify NetSuite integration guide.

First decide who owns what

Most failed ERP integrations fail because nobody decided which system is the source of truth for each type of data. Write this table down before choosing any tool:

Typical flows

• Orders → ERP: as sales orders with customer, lines, discounts, tax, shipping and payment method. B2B orders carry the PO number and payment terms.
• Items and prices → Shopify: new items created, prices updated, B2B price lists written into Shopify catalogs.
• Inventory → Shopify: available quantities per warehouse mapped to Shopify locations.
• Fulfillments → Shopify: shipments with tracking, including partial shipments.
• Refunds and returns → ERP: credit notes and stock returns.
• Payouts → ERP: payment settlement and fees, for finance.

ERP by ERP

SAP. SAP Business One exposes the Service Layer, a REST-style API. S/4HANA exposes OData APIs, and many landscapes route integrations through SAP's Integration Suite or another middleware layer run by the SAP partner. Expect IDs, units of measure and pricing conditions to need careful mapping.

Microsoft Dynamics 365. Business Central includes a Shopify Connector from Microsoft and has a REST API for custom work. Finance & Operations projects usually integrate through data entities and OData, often via Azure-based middleware.

Acumatica. The Commerce Edition includes a Shopify connector with configurable entity sync. Acumatica's contract-based REST API is available for custom flows.

Odoo. Several third-party Shopify connector modules exist. For custom integrations, Odoo's external API (XML-RPC/JSON-RPC) exposes models such as sales orders, products and stock. Odoo instances are often heavily customized, so check that a connector matches your version and modules.

Connector, middleware or custom app?

How a custom ERP integration is built

1. Webhooks in, queue first. Shopify order, refund, customer and company webhooks are verified and queued. The worker fetches full records through the GraphQL Admin API.
2. Idempotent writes. Every ERP document carries the Shopify ID as an external reference, and the integration checks it before creating anything. Retries are safe.
3. ERP to Shopify on change or on schedule. Price, stock and fulfillment changes are picked up from ERP events or polled on a schedule, and written with GraphQL Admin mutations. Large price or catalog updates use bulk operations.
4. B2B. Companies, locations, payment terms and catalogs are created and updated from ERP customer and price-list data. See Shopify B2B.
5. Mapping in config: locations, tax codes, payment methods, shipping services and units of measure live in editable tables, not in code.
6. Visibility. An error list with the ERP's message and a retry button, plus a daily reconciliation of order counts, totals and stock between systems.

A runbook for the failures that will happen

Every ERP integration eventually meets these. Deciding in advance what happens is part of the build:

• ERP down or in maintenance. Orders queue and retry with back-off. Nothing is lost, and staff see a banner with the queue length.
• Unknown SKU. An order contains a SKU the ERP doesn't know. The order goes to the error list, not a guessed item, and the fix is to create the item and retry.
• Customer or company not found. Create it from Shopify data, or hold the order for review, depending on your rules for B2B credit.
• Price mismatch. The ERP recalculates a B2B price that differs from the one charged. Decide whether Shopify's price wins, and flag the order either way.
• Stock drift. Daily reconciliation finds Shopify and ERP stock differ. The ERP wins, Shopify is corrected, and the SKU is logged for investigation.
• Duplicate event. The external reference check makes the second attempt a no-op.
• Bulk price update from the ERP. Thousands of changes at once are sent as a bulk operation rather than thousands of single calls.

Decision checklist

• Which ERP product and version, hosted where? Is there a sandbox?
• Who owns each data type (the table above)?
• Do you sell B2B with customer-specific pricing, terms or credit limits?
• How many locations and warehouses? Is there a WMS or 3PL in between?
• What volume at peak, in orders per hour and price updates per day?
• Who at your company will read the error list?