Skip to content

// Insights / Practical Shopify guidance

Shopify ERP integration: define ownership and failure handling

Sonder Sites · First published · Updated

An ERP connection needs agreed data ownership before it needs more automation. Start by deciding which system is authoritative for products, stock, prices, orders, returns and finance.

Make a data-flow map

For each object, record the originating system, identifier, destination, update timing and person responsible. Include the manual exceptions the team handles today. A revenue threshold does not decide whether an ERP or connector is necessary.

Evaluate the actual connector

Whether the business uses NetSuite, Dynamics, SAP, Acumatica, Cin7, MYOB or another system, check the supported data objects and version, contract, vendor support and failure behaviour. Do not assume a named connector covers every workflow.

  • Which stock locations and price rules are supported?
  • How are cancelled, refunded and partially fulfilled orders handled?
  • How are duplicate or delayed events reconciled?
  • Who can inspect and recover a failed sync?

Plan for limits and retries

Shopify's API limits differ by API and plan. Use the current documentation for the chosen interface and design controlled retries, queues and reconciliation around it. Do not apply one request-rate number to every integration. Shopify API limits.

Prove the difficult cases before release

Use representative data and an authorised test environment. Include stock changes, partial orders, returns and outages. Check both the customer surface and the records received by operations. Agree cutover, rollback and support responsibilities before connecting live workflows.

Make ongoing ownership explicit

A successful initial sync does not prove long-term reliability. Keep monitoring, exception review and provider updates in the operating scope. Report failures recovered and records reconciled separately from any claimed commercial benefit.

Discuss Shopify development with the data map and connector requirements. The cost register includes the integration support the business will actually pay for.

Sources and review

Guidance checked on 7 October 2026. Features and commercial terms can change; confirm availability for your own account and scope. These planning checks are recommendations and do not replace an assessment of the actual implementation.

Back to all insights