Shopify ERP Integration: Connector vs iPaaS vs Custom Middleware

Once you know what needs to move between Shopify and your ERP, the next question is how. There are three serious options: a prebuilt connector, an integration platform, or custom middleware. There is also a fourth, home-made scripts, which is where many businesses already are.

A disclosure before we start: we build custom middleware, including our own ECX platform, so weigh our view accordingly. We also recommend connectors regularly, because building custom where a connector fits is expensive for no benefit.

The Options at a Glance

	Prebuilt connector	Integration platform (iPaaS)	Custom middleware
Examples	Business Central's Shopify Connector, Oracle NetSuite Connector	Celigo, Patchworks	Built for you; ECX in our case
Time to start	Fastest	Moderate	Slowest
Fit to unusual rules	Whatever it supports	Configurable, within the platform	Anything you can specify
Cost shape	Subscription	Subscription, often by flow or volume, plus setup	Build cost, then hosting and maintenance
Multiple systems	Usually one ERP to one store	Designed for it	Designed for it
Who fixes it	The vendor, on their timeline	You or a partner, within the platform	Whoever built and maintains it
Changing ERP later	Start again	Rebuild the ERP side	Rebuild the ERP side only

Prebuilt Connectors

A prebuilt connector is the right choice when your processes match what it expects and the ERP vendor or Shopify's certified program already covers your ERP.

The ERP vendors have moved into this space themselves. Microsoft Dynamics 365 Business Central includes a Shopify Connector that synchronizes products, stock, customers, B2B companies and orders, and supports more than one Shopify store. Oracle sells NetSuite Connector, the former FarApp, for NetSuite. Shopify also certifies ERP apps through its own program, currently including Business Central, NetSuite, Infor, Acumatica and Brightpearl.

Choose one when your order flow, pricing and fulfillment look like what the connector expects, and one ERP talks to one or two stores.

Walk away when the demo needs caveats. If the answer to "can it handle our customer-specific pricing?" is "with a workaround", count the workarounds. Each one is a small custom build you now maintain on top of a system you do not control.

Then test what demos skip. In our experience, bundles and kits, and custom fields the connector has nowhere to put, are the problems most likely to appear only after launch: the demo and the test orders use plain products, and the first real order with a kit or an unmapped field fails or posts wrongly in the ERP. The other two we see most are B2B and retail orders that need different records in the ERP, and stock counted twice when the ERP sends inventory back before Shopify has shipped the order.

Integration Platforms (iPaaS)

An integration platform is a hosted service with prebuilt flows between common systems, which you configure and extend. Its strength is breadth: an ERP, a warehouse, a marketplace tool and a CRM can all be connected and monitored in one place.

Choose one when three or more systems are involved, your team or partner will actively manage the flows, and your rules fit what the platform can express.

Watch for pricing that scales with the number of flows or transactions, which can grow faster than the business, and for logic so customized inside the platform that only one person understands it.

Custom Middleware

A layer built for your business between Shopify and the ERP. It receives events, queues them, transforms the data, retries failures without creating duplicates, and alerts someone when things go wrong. It is more work up front, and it is the only option with no ceiling on what it can handle.

Choose it when any of these are true:

• The ERP is old or in-house. We connected KOL Foods' AS400 system through ECX, including real-time pricing for products sold by the pound. No connector expects that.
• The rules are unusual. Customer-specific pricing with exceptions, kits, units of measure, or a checkout that is not Shopify's. For PayJoy on BigCommerce, a custom gateway carried every credit application to their own financing engine.
• The data lives in more than one place. Richloom keeps fabrics and finished goods in two separate AS400 databases with different specifications. Our ECX middleware feeds both into one storefront catalog and converts imperial measurements to metric on the way in, because that is business logic, not display logic.
• You expect to change ERP. See below.

Connector and Custom, Together

The options are not exclusive. QC Supply runs both: a connector built by an integration partner moves data between Microsoft Dynamics NAV and Shopify, and our custom B2B portal handles company accounts, saved product lists and ordering rules on top. We consulted on the integration and worked on the Shopify side. Most of the work in a setup like this sits at the seams:

• Which system creates a customer. The connector creates an ERP customer for each new Shopify customer. Wholesale buyers added through the portal already existed in the ERP, so the connector needed a reliable marker to tell them apart and skip them.
• Where settings live. Payment terms and catalogs were assigned to each company by the connector, but a location a company added later did not pick them up, and a buyer at that location could not check out until it was fixed.
• How discounts arrive. The same discount reached the ERP with a different subtotal depending on whether it was set up as an automatic discount or a code, because Shopify applies the two at different points. Staging used a code and matched. Production used an automatic discount and did not.

None of these were bugs in either system. They were decisions nobody had written down. Settle the field ownership map before the connector is configured, not after the first wrong invoice.

Home-Made Scripts

Many businesses arrive with an integration already running, built by someone on the team with a workflow tool and some code. One prospect sent every Shopify order through a webhook into a hosted automation tool, where custom JavaScript matched products to their accounting system and created an invoice. Shipping details came back through a separate warehouse integration.

It worked, which is exactly why it is risky. It moved data in one direction only, nobody else understood it, and when they needed orders to flow from the ERP into Shopify, there was nothing to extend. Scripts are fine for proving a flow works. Before they carry real volume, they need queueing, duplicate protection, monitoring and an owner.

If You Might Change ERP, Decide Now

One manufacturer we scoped was planning to replace its ERP within two years. That single fact changes the recommendation. A connector ties you to the current ERP: replace the ERP and you start the integration again. Middleware, whether custom or on an integration platform, puts a layer between the systems, so when the ERP changes only that side is rebuilt, and Shopify, the warehouse and everything else stay untouched.

Costs That Do Not Show Up in the Demo

Every option carries costs the demo leaves out, and over five years they matter more than the subscription price.

• Growth pricing. Subscriptions priced by orders, flows or connected systems rise as you grow.
• Workarounds. Every gap a connector cannot handle becomes a custom build or a manual task.
• API changes. Shopify releases a new API version every quarter, and ERPs update too. Someone has to keep the integration current, whichever option you choose. This year Shopify gave one of our clients a July 1 deadline to move their custom portal app to a newer API version; we updated it, and a second app that had not been flagged yet.
• Upkeep of custom code. Middleware is software, and it ages. Our own ECX needed two framework upgrades in twelve months, one of them to clear a high-severity vulnerability in a supporting package, and one client's integration server reached the end of its operating system's support. Budget for that every year.
• Monitoring. Knowing that sync has drifted before customers notice is a feature you have to ask for. Platforms give up quietly, too: BigCommerce switched off one client's order webhook after 48 hours of failed deliveries, and nothing else would have said so.

How to Decide

1. Write down which system owns each field, using our data ownership map as a starting point.
2. Take that map to a connector demo and ask it to handle each row. Count the caveats.
3. Before launch, run real test orders that include a bundle or kit, a B2B order and any custom fields you rely on.
4. Count the systems involved. Three or more points towards a platform or middleware.
5. Ask whether the ERP will still be there in three years.
6. Price all three options over three years, not just the first.

Our Shopify ERP integration guide covers the rest of the project around this choice.

Not Sure Which Fits?

Tell us your ERP, your other systems and the rules that make your business different. We will tell you honestly whether a connector will do the job. Talk to us directly.

Frequently Asked Questions

Should I use a Shopify ERP connector or custom integration?

Use a prebuilt connector when your processes are standard and one ERP connects to one or two stores. Use custom middleware when your pricing or product rules are unusual, your ERP is old or in-house, your data lives in more than one system, or you expect to change ERP.

What is an iPaaS for Shopify?

An integration platform as a service is a hosted platform, such as Celigo or Patchworks, with prebuilt flows between common systems that you configure and extend. It suits businesses connecting three or more systems, such as an ERP, a warehouse, a marketplace tool and a CRM, from one place.

Does Microsoft Business Central have a Shopify connector?

Yes. Dynamics 365 Business Central includes a Shopify Connector from Microsoft that synchronizes products, inventory, customers, B2B companies and orders, and supports more than one Shopify store.

What happens to my Shopify integration if I change ERP?

With a direct connector you usually start the integration again. With middleware, whether custom or on an integration platform, only the ERP side is rebuilt, and Shopify, the warehouse and other connected systems stay as they are.

Can I use a connector and custom development together?

Yes, and it is common. A connector can handle the standard flows between the ERP and Shopify while custom development covers what it does not, such as a B2B portal or unusual pricing rules. Decide which system owns each field first, because most problems in a mixed setup appear where the two overlap.

Are home-made Shopify integration scripts good enough?

They are fine for proving a flow works. Before they carry real order volume they need queueing, protection against duplicates on retry, monitoring and a named owner, or they tend to fail silently and resist being extended.

What usually goes wrong with a Shopify ERP connector after launch?

Bundles and kits, and custom fields with no place in the connector's mapping, are the most common, because demos and test orders rarely include them. B2B and retail orders that need different ERP records, and stock counted twice when the ERP updates Shopify before an order ships, are the other usual causes. Test each with real orders before go-live.