Shopify Integrations

We connect Shopify to the systems UK merchants run their business on: ERPs such as Sage 200, NetSuite and Microsoft Dynamics, accounting packages like Xero, warehouses and 3PLs, PIMs and custom APIs. We set up connector apps where they fit, and build custom integrations where they do not.

What do we integrate Shopify with?

• ERPs. Sage 200, NetSuite, Microsoft Dynamics 365 Business Central and others. Usually the ERP is the master for products, prices and stock, and Shopify is the master for orders.
• Accounting. Xero, QuickBooks and Sage Accounting. Orders, refunds, payouts and fees posted so the books reconcile against Shopify Payments or your payment provider.
• Warehouses and 3PLs. Sending orders for picking, getting tracking numbers back, and keeping stock in step across locations. Shopify's fulfilment orders model lets a 3PL accept, reject or partly fulfil an order.
• PIMs. Product data, imagery and translations managed in Akeneo, Plytix or similar, pushed into Shopify products, metafields and metaobjects.
• Custom and legacy systems. Bespoke trade portals, CSV drops on an SFTP server, SOAP APIs, or a supplier's stock feed.

Connector app, middleware or custom integration?

There are three ways to do this, and the right one depends on how standard your processes are.

	Connector app	Middleware / iPaaS	Custom integration
Examples	An App Store app for your ERP	Celigo, Make, Alumio, Patchworks	Code written for your systems
Setup	Configure and map fields	Build flows on a platform	Designed and built from scratch
Fits unusual processes	Poorly	Reasonably, with scripting	Fully
Ongoing cost	Monthly subscription	Platform licence, often by volume	Hosting and support
Visibility when things fail	Depends on the app	Usually good dashboards	Whatever logging and alerts we build in

Choose a connector app when one exists for your ERP, your processes are close to standard, and its field mapping covers what you need. This is often the cheapest route, and we will tell you if it is the right one.

Choose middleware when you have several systems to connect, want a dashboard where non-developers can see and retry failed syncs, and are comfortable paying for the platform.

Choose a custom integration when your data model does not fit a connector, such as trade pricing held per customer in Sage, kits and bundles, or stock pooled across warehouses in a particular way. It also makes sense when the connector's monthly fee at your order volume outweighs building and running your own.

We also do hybrid work: a connector for the standard flows, plus a small custom service for the one thing it cannot handle.

Where Shopify integrations go wrong

Most integrations work on the happy path. The problems turn up weeks later with a refund, a split shipment or a busy weekend. These are the failure modes we design for from the start.

Stock drift

Shopify and the ERP slowly disagree about stock. Common causes are full stock pushes overwriting sales that happened during the sync, or the ERP sending on hand figures when Shopify expects available. Shopify tracks several inventory states (available, committed, on hand, reserved and more), so we agree which number is the source of truth and sync adjustments, not just totals, where the ERP supports it.

Duplicate orders

Shopify webhooks are delivered at least once and can be retried, so the same order can arrive more than once. Without an idempotency check keyed on the Shopify order ID, the ERP creates two sales orders and the warehouse ships twice. Every handler we write records what it has already processed.

Refunds, edits and partial fulfilments

A refund of one line, an order edit after payment, an exchange or a part-shipped order all change the order after it has been sent to the ERP. Many connectors only handle the original order. We map each of these events to the right document in the other system, such as a credit note or an amended sales order.

VAT and rounding

Shopify can show prices including VAT while the ERP calculates VAT per line or per document. The result is penny differences that stop invoices reconciling. Discounts, shipping VAT, zero-rated products and sales to Northern Ireland or the EU add more cases. We agree the calculation rules with your accountant or finance team before writing any mapping.

Multi-location inventory

Shopify supports multiple locations and decides which one fulfils an order. If the ERP has its own warehouse logic, the two can make different decisions. We map Shopify locations to ERP warehouses explicitly, and decide which system chooses where an order ships from.

Rate limits and volume

The GraphQL Admin API uses a cost-based rate limit, with higher limits on Shopify Plus. A sync that updates thousands of variants one at a time will hit it, particularly during a sale. We batch updates, use bulk operations for large reads, back off and retry when throttled, and queue work so a spike does not drop data.

How an integration project runs

1. Discovery call. We talk through the systems involved, which one owns which data, and what goes wrong today.
2. Written scope and fixed quote. A data map showing each field and direction of sync, the events covered, and a fixed price.
3. Build against test environments. A Shopify development store and, where possible, a sandbox or test company in your ERP. We test with real data copied from production.
4. Review. We run through refunds, edits, split shipments and stock scenarios with you, not just new orders.
5. Launch. We switch on in a controlled way, check every synced order for the first few days, and fix discrepancies.
6. Support. Monitoring, alerts on failed syncs, and upgrades when Shopify or the ERP changes its API.

Integrations often go alongside a custom Shopify app for admin tools or checkout rules. If the integration is part of a wider system, such as a trade portal, see web application development. For everything else on Shopify, see our Shopify development page.

FAQs

Can you integrate Shopify with Sage 200?

Yes. Sage 200 is usually the master for products, trade prices and stock, with Shopify sending orders and customers back. There are connector apps and middleware platforms that support Sage 200, and we will recommend one if it fits your setup. Where trade pricing, kits or warehouse rules are more complex, we build a custom integration.

What does a Shopify ERP integration cost?

It depends on the number of systems, the volume of orders and products, and how many events need handling beyond new orders. We do not publish set prices. After a discovery call we send a written scope with a data map and a fixed quote. If a connector app would do the job, we say so.

Why does our stock keep going out of sync?

The usual causes are full stock pushes overwriting recent sales, the ERP sending on hand stock when Shopify expects available stock, or failed syncs that nobody is alerted to. Locations that are mapped incorrectly between Shopify and the ERP are another common one. We can audit an existing integration and tell you which applies.

Can you fix an integration someone else built?

Yes. We start by reviewing the code or connector configuration, the logs, and a sample of orders that went wrong. You get a written list of the problems and what each fix involves. Sometimes it is a small change to idempotency or mapping. Sometimes it is cheaper to rebuild the integration than to keep patching it.

How do you handle failed syncs?

Every message is queued and retried with backoff, so a short outage on either side does not lose data. Anything that still fails goes into a dead letter queue and triggers an alert with the order or product affected. Failed items can then be fixed and replayed, rather than re-entered by hand.

If you need Shopify talking reliably to another system, tell us what you are connecting.