Skip to main content

Shopify ERP Integration: Order and Stock Sync

  • November 2, 2026
  • 8 min read
  • By CYPHEX
Shopify ERP Integration: Order and Stock Sync
Illustrative animation with example data

A Shopify ERP integration moves orders, stock levels and shipment details between your store and the system your back office runs on. This guide is for owners and operations or IT leads who are choosing between a ready-made connector, a middleware platform and custom work. You will learn which data flows in which direction, how it fails in practice, what a sensible architecture looks like, and what to ask before anyone writes code.

What the integration actually does

Strip away the vendor language and an ERP sync is four conversations.

  1. Orders go from Shopify to the ERP, so finance and fulfilment can process them.
  2. Stock goes from the ERP to Shopify, so the store doesn’t sell what you don’t have.
  3. Fulfilment status and tracking go from the ERP or warehouse back to Shopify, so customers are told where their parcel is.
  4. Products, prices and customers move in one or both directions, depending on which system is the master.

Shopify’s own ERP integration guide lists the same flows: orders, addresses and tracking numbers, inventory by location, finance data such as invoices and refunds, customer data, product and price data, and B2B documents. It also names the main ways to connect: custom builds, native connectors, iPaaS (cloud integration platforms), ESB (middleware for large on-premises estates) and ETL (batch moves for reporting). Where a vendor-built connector fits your pair of systems, Shopify says it’s fast and low-maintenance. Custom builds give full control for niche systems but are costly to build and maintain.

Choosing: connector, middleware or custom

OptionGood whenWatch out for
Ready-made connectorYour ERP has a maintained Shopify connector and your processes are standardFields and rules it can’t change; who supports it
iPaaS / middlewareYou connect several systems, or need mappings and schedules without building from scratchSubscription cost, plus someone to own the flows
Custom integrationUnusual ERP, special pricing or approval rules, or logic no connector offersYou own the maintenance, monitoring and API changes

The pattern I see in most guides is that they stop at “pick an option”. The more useful question is who will notice and fix a failed sync at 8 am on a Monday. Choose the option whose failure mode your team can handle.

The data owner decision (do this before anything else)

For each type of data, decide which system is the source of truth. Shopify’s guide lists unclear ownership and field mappings as a cause of failures and rework, and I agree. A typical split:

DataUsual masterDirection
OrdersShopify (created there)Shopify to ERP
Stock quantitiesERP or warehouse systemERP to Shopify
PricesERP, or Shopify if you set them thereDecide and write it down
Tracking numbersERP, warehouse or carrierOut to Shopify
Customer credit terms (B2B)ERPERP to Shopify
Product content (images, copy)Shopify or a PIMUsually not ERP

When two systems both think they own stock, they overwrite each other. Don’t let that happen by default.

A reference architecture

You can draw most reliable integrations in the same shape.

  1. Shopify webhooks announce events such as a new order. Shopify’s webhook documentation describes them as near-real-time notifications that are more efficient than polling, delivered to an HTTPS endpoint, Google Pub/Sub or Amazon EventBridge.
  2. A small receiver verifies and acknowledges. It checks the X-Shopify-Hmac-Sha256 signature against the raw request body and answers with a 200 quickly. Per Shopify’s HTTPS webhook guide, it allows one second to connect and five seconds for the whole request, and treats anything outside the 200 range as an error. Heavy work belongs on a queue.
  3. A queue holds the job. This absorbs bursts such as a flash sale and lets you retry safely.
  4. A worker maps the order and calls the ERP. The ERP might have its own API, a file drop or an EDI route. Field mapping lives here.
  5. A log records every step, with the Shopify order number and the ERP document number side by side so support can trace an order in seconds.
  6. A reconciliation job runs on a schedule, comparing the two systems and fixing gaps.
  7. Stock and tracking return the other way through the Admin API.

Why webhooks alone are not enough

Shopify’s documentation is candid on this. Webhook delivery isn’t always guaranteed, so apps shouldn’t rely on it alone; Shopify recommends reconciliation jobs that periodically fetch data and use updated_at filters to pick up only what changed. It also says order across topics isn’t guaranteed and suggests using X-Shopify-Triggered-At or the payload’s updated_at to sequence events.

Other behaviours to design around, from the HTTPS guide:

  • Retries. If Shopify gets no response or an error, it retries 8 times over about four hours, and subscriptions created through the Admin API may be deleted automatically after 8 consecutive failures, with a warning email to the app’s emergency developer address. Monitor your endpoint, or you can silently stop receiving orders.
  • Duplicates. Deliveries can repeat. Use X-Shopify-Webhook-Id or make processing idempotent so one order never becomes two ERP documents.
  • Raw body for signatures. Capture the raw body before any JSON parsing, or verification fails.

Our related article on content sync pipelines with webhooks covers the same ideas outside Shopify.

Pushing stock into Shopify safely

Stock is where integrations hurt, because overselling is expensive. Shopify’s inventorySetQuantities mutation sets absolute values and needs the write_inventory scope. The documentation recommends it only for systems that are the source of truth for inventory, and otherwise points to adjusting quantities. It also describes a compare check (changeFromQuantity) so an update only applies if the stored value matches, plus an idempotency key, which it lists as required from API version 2026-04. Because requirements change by API version, build against the version in the docs and re-read them at each upgrade.

For large catalogues, don’t update item by item. Shopify’s bulk operations let you fetch big datasets asynchronously as a downloadable JSONL file instead of paging manually, and the docs state limits such as a ten-day maximum run time. Our article on large catalogues in Shopify goes into this. Rate limits also apply: Shopify’s rate-limit page explains that GraphQL limits are cost-based and use a leaky bucket, with bucket sizes varying by plan.

Fulfilment and tracking back to Shopify

Shopify models fulfilment around fulfillment orders, which represent items that ship from the same location. Its order management guidance says one order can have several, with different delivery methods, so your integration should check each rather than assume one shipment per order. When a parcel ships, the fulfillmentTrackingInfoUpdate mutation updates carrier, tracking numbers and URLs on a fulfilment and can notify the customer; it needs one of several fulfilment-order write scopes. See automating order status updates for the customer-facing side.

What goes wrong in real projects

  • Scope creep from late discoveries, the first risk Shopify’s guide names.
  • Unmapped edge cases: split shipments, partial refunds, gift cards, bundles, backorders, tax rounding.
  • Test data that doesn’t match production: ten clean orders prove little.
  • No owner for failures. Alerts go to an inbox nobody reads.
  • Hidden secondary costs: data migration and training can outweigh licence fees, according to Shopify’s guide.
  • API changes. Custom code breaks when APIs are retired, so budget for upgrades.

What to ask before you start

  • Which data does each system own, and who agreed?
  • Which of the three routes (connector, middleware, custom) fits, and why?
  • How are failed orders surfaced, and who gets the alert?
  • How are duplicates and retries handled?
  • How often does reconciliation run, and what does it fix automatically?
  • How are tests done: sample orders, edge cases, a dry run?
  • What does cut-over look like and how do we roll back?
  • Who maintains this after launch, and what’s included in support?

For cost, the drivers are the number of data flows, ERP API quality, edge cases, volume, testing, monitoring and support. I will not quote a price here; compare proposals on the points above. If you are weighing scale features generally, see Shopify Plus for enterprise scale. Our API integration development and Shopify development services cover this work.

Frequently Asked Questions

What is a Shopify ERP integration?

It’s a connection that moves orders, inventory, fulfilment data and sometimes customers and prices between Shopify and your ERP, so both systems agree. It can use a ready-made connector, an integration platform or custom code.

Should I use a connector or build custom?

Use a maintained connector if it fits your processes, because Shopify describes these as fast and low-maintenance for standard pairs. Build custom when your rules, ERP or volumes don’t fit, and plan for ongoing maintenance.

How real-time does the sync need to be?

Orders can often flow within seconds to minutes, while stock needs depend on how fast you sell. Many businesses use webhooks for speed and a scheduled reconciliation for safety. Decide per data type instead of aiming for “real time” everywhere.

Can webhooks lose orders?

Shopify says webhook delivery isn’t always guaranteed and recommends periodic reconciliation. A good integration therefore combines webhooks with a job that re-checks recent orders.

Who should own the stock numbers?

Usually the system that actually knows what’s on the shelf, which is often the ERP or warehouse system. Shopify’s inventory mutation docs recommend setting absolute quantities only from the source of truth.

Conclusion

A dependable Shopify ERP integration comes from clear data ownership, a verified and queued webhook receiver, safe stock updates, and a reconciliation job that catches what webhooks miss. Pick the connector, middleware or custom route that your team can monitor and support. Before approving a build, insist on answers about failure handling, testing and maintenance. If you would like help with this, CYPHEX can plan and deliver it for you, with one project lead as your contact.

Stock photography provided by Pexels under the Pexels License.

Want your online store to sell more?

We can review your store and show you what to fix first to turn more visitors into buyers.

Comments

  1. Loading comments...

Leave a comment

Selling online?

Turn more visitors into orders

A faster, clearer store with better product pages and checkout. We handle Shopify and WooCommerce from setup to growth.

Step 1 of 3

Tell us what you need

Three quick steps. We reply within one business day.

What do you need help with? Pick all that apply