Connecting ERP and CRM to Shopify Plus starts with ownership, not endpoints. Define which system owns products, prices, inventory, customers, orders, and after-sales data. Without a master-data and recovery policy, more integrations create more duplicate orders, stock conflicts, and support confusion.
Build a master-data matrix
For each object, record owner, permitted writers, direction, version field, and manual correction path. A PIM or ERP may own product and price; CRM or Shopify may own customer consent and service context. Two systems must not silently overwrite the same field.
Events and reconciliation
Give orders, refunds, cancellations, inventory changes, and customer updates explicit events. Webhooks can be duplicated, delayed, or fail. Store event ID, retry count, and final state, then reconcile by order, SKU, and customer ID. Use Admin GraphQL API, webhooks, and orders documentation.
Launch acceptance
- Pilot a small market and SKU set to validate field mappings.
- Test price changes, stock-outs, partial fulfilment, refunds, duplicate events, and outages.
- Define rollback owner, manual correction permission, and reason logging.
- Include consent, customer deletion, and export requests in the flow.
FAQ
Should an ERP be called synchronously during checkout?
Usually not. Checkout should use controlled price, inventory, and tax data; the completed order can then sync through events.
Which system should own the customer record?
There is no universal answer. Assign ownership by account, consent, service, and order use case and document it.
How can duplicate sync be prevented?
Use stable object IDs, event IDs, idempotency keys, retry queues, and reconciliation rather than manual deletion.
Does Plus automatically solve ERP integration?
No. Plus defines platform capabilities; mappings, permissions, governance, and external reliability remain project responsibilities.