What a Shopify ERP integration actually involves

When a business asks us for an ERP integration, they usually mean something that makes the double keying stop. What they need is a small project. Decisions about who owns which data, a mapping between two systems that describe the world differently, and a plan for when things fail.

A Shopify ERP integration involves five stages. Discovery, where you agree which system owns each record. Mapping, where fields and rules are matched. The build, using a connector, middleware or a custom app. Testing against real edge cases. And monitoring once it's live. The build is often the shortest of the five.

Who needs to be involved?

Integrations fail in the gaps between people as often as the gaps between systems. Three roles need names from the start.

• An ERP owner, internal or at your ERP partner, who knows how it's configured and what can change.
• A commerce owner, who designs and builds the Shopify side. That's us, when we're doing the work.
• Someone who runs orders every day, who knows the exceptions nobody wrote down.

Joint calls between the ERP partner and the commerce team are normal. The ERP partner owns the ERP. We own the commerce layer. That clarity stops problems falling between the two.

What happens in discovery?

Discovery produces a written map of who owns what. Products, stock, prices, customers, orders, fulfilment, returns and invoices each get one system of record.

It also answers practical questions.

1. How fresh does each piece of data need to be? Stock on a fast-moving line might need near real-time updates. Product descriptions can sync overnight.
2. What volume are we dealing with, on a normal day and at peak?
3. Which ERP customisations will the integration touch?
4. What does the business do today when an order goes wrong?

The last question matters most. Today's manual workaround becomes the starting point for error handling.

How does data actually move?

There are two broad patterns, and most integrations use both.

Event-driven syncs react to something happening. An order is placed in Shopify, a webhook fires, and the order is created in the ERP within moments. This suits orders and new customer records.

Scheduled syncs run on a timetable. Every few minutes, every hour or overnight, a job collects changes and sends them across. This suits bulk price updates, product data and stock on slower lines.

Either way, a good sync is safe to repeat. If the same order arrives twice, the ERP should recognise it rather than create a duplicate. When a record fails, it goes into a queue someone can see and retry, not a log nobody reads.

Where does the time go?

Mapping and testing, almost every time.

Mapping takes time because the two systems see things differently. An ERP item might have units of measure, price groups and several warehouses. Shopify has products, variants, catalogues and locations. Every field needs a home and a rule for how it changes.

Testing takes time because edge cases are where money is lost. These are on our list for every wholesale integration.

• Split shipments and partial fulfilments.
• Partial refunds and cancelled lines.
• Discounts and how they appear on the ERP order.
• Tax across every market you sell to.
• A customer created in both systems at once.
• A sync that fails halfway through a batch.

The ERP's own state affects timing too. Fáilte Foods had only just moved to Business Central when our project started, and a lot of configuration was still in progress. We worked through the product sync carefully so everything landing in Shopify was clean from day one. The store launched with real-time order and customer synchronisation, and customer onboarding rose by over 500%.

What happens after go live?

An integration is a living system. ERPs get updated. Shopify releases new API versions. Someone adds a field, a price group or a new warehouse.

Plan for three things from the start.

• Monitoring and alerts, so failures surface the same day, not the same month.
• A reconciliation check that compares orders and stock between the systems on a regular rhythm.
• A named owner with time budgeted every month to look after it.

Without those, integrations drift. The first sign is usually a trade customer asking why their price is wrong, or a warehouse picking an order that was cancelled.

For system-specific detail, see our guides to connecting Shopify to Business Central and a Shopify Odoo integration. Some jobs are small internal automations rather than a full sync. Our note on Sidekick custom apps and Flow explains where those tools fit.

Where parallel helps

We build ERP integrations for Business Central, Odoo, NetSuite, SAP, Sage and Dynamics 365 Finance and Operations, and we can look after them after launch. See how we approach apps and integrations. Our page for distributors in the North describes the pattern we see most, with account pricing, a large catalogue and an ERP already in charge.

Tell us which ERP you run and what's being keyed by hand today. Send us a brief and we'll outline what your integration involves.