Follow the order beyond checkout
A successful checkout is only the start. The order needs to reach the right ERP company, reserve the right stock, reach fulfilment and reconcile with payments. We scope those handoffs together, including what happens when one step fails.
- Products and stock: match products and variants, map inventory locations, agree sellable stock and prevent conflicting updates.
- Orders and customers: preserve source references, shipping details, discounts and the tax treatment agreed with your finance team.
- Fulfilment: return dispatch status and tracking, handle split shipments, and agree which system owns cancellation decisions.
- Refunds and finance: connect refunds, fees and settlements to the records used for reconciliation. Do not assume an order total is the same as a bank deposit.
Shopify with NetSuite or Business Central
NetSuite
Plan item and customer matching, subsidiary and location mappings, order creation and fulfilment updates around your NetSuite configuration. Custom fields and existing workflows can change the required mapping. Our Shopify–NetSuite integration guide covers this platform pair in more detail.
Microsoft Dynamics 365 Business Central
Assess the available Shopify connector and API capabilities against your companies, items, variants, customer pricing and posting process. Confirm which requirements the standard connection covers before adding extensions or middleware. Test the full order lifecycle in your setup, including returns and partial shipments.
For other ERPs, start with the same ownership and record-matching questions. See our ERP integration scope for the decisions to settle before a build.
Choose the smallest approach that covers the process
A native connector can be appropriate when its supported workflows fit. Celigo can suit a wider estate with transformations, several destinations and shared monitoring. A custom API connection may be needed for a proprietary system or a rule that the available connectors cannot express.
Compare coverage, maintenance ownership, licensing, failure recovery and the cost of future change. We can assess the options through ERP-connected eCommerce consultancy and platform selection, or review an existing Celigo account before extending it.
Test the exceptions before launch
Use representative Australian orders: postcode values with leading zeroes, location stock, inclusive and exclusive tax fields as configured, discounts, refunds and split fulfilment. Include out-of-order events, an unavailable destination and a duplicate notification. Confirm that a retry cannot create a second order or refund.
Agree a cutover window, reconciliation checklist and rollback decision. During initial trading, compare source and destination record counts and totals, investigate unmatched records and measure stock-feed delay. Scope and timing depend on your data quality, customisations, volumes and available test environments.
Support for an integration you already have
If stock drifts or orders disappear, preserve the source references and trace the path before adding another automation. We review the current connector, flow history and mapping rules, prioritise the failures affecting customers and agree a repair plan.
Ongoing support should name the owner, support hours, alert destination and escalation route. For a Celigo-based connection, see our Celigo integration support. For ERP configuration and customisation issues, see ERP implementation and support.
Questions before you connect Shopify
Can Shopify connect to our existing ERP?
Often, yes. The scope depends on your ERP's APIs, customisations and business rules. We assess the required records, available endpoints, access permissions and transaction volumes before recommending a native connector, Celigo flow or custom integration.
Do we need Shopify Plus for ERP integration?
ERP integration is not by itself a reason to choose Plus. Assess your actual API throughput, checkout, B2B and operational requirements against Shopify's current plan features. We test the required workflows before recommending a plan change.
Can you repair an existing Shopify integration?
Yes. Start with a review of missing or duplicated records, mappings, sync schedules, access permissions and error handling. Agree a recovery and validation plan before replaying orders or changing stock feeds in production.
Will inventory always update instantly?
The practical delay depends on each system's events, API limits, processing time and sync schedule. Agree an acceptable freshness target, stock buffers and reconciliation checks. A scheduled stock feed should not be described as instantaneous.
What should we prepare for the first conversation?
Bring the Shopify plan, ERP and fulfilment systems, the records you need to move, peak volumes, existing connectors and examples of failures. Do not send passwords or API tokens through the enquiry form. Access can be arranged securely after the scope is agreed.
Related integration work and guidance
These delivered projects explain wider ERP and commerce decisions; they are not presented as Shopify implementations.