Choosing an ERP for Shopify: Native Integrations, Connectors and Middleware Explained

Most ERP evaluations follow a similar path, and for good reason. You build a shortlist, sit through demos, compare feature lists and work through pricing. The integration usually comes up later in that process, often as a single line: yes, it connects to Shopify.

That line is worth a few more questions, because once you are live it describes the part of the setup you deal with most often. The integration carries orders into your operations system and sends stock levels back out to the storefront. It also handles the cases in between: an order edited after it was placed, a refund issued in Shopify, stock held across more than one location.

Two vendors can both say they connect to Shopify and mean quite different things by it. Here is what sits behind the word, and what to ask about it.

The Four Ways a System Connects to Shopify

1. A native integration built by the vendor

The vendor builds and maintains the connection themselves, usually published as an app in the Shopify App Store.

The main advantage is ownership. When something breaks there is one company to call, and less room for the fault to be passed between suppliers. Where the vendor maintains the connection against Shopify's API changes as part of the product, updates tend to arrive without a separate project or a separate bill.

What to check: how much of the Shopify feature set it actually covers. Native does not automatically mean complete.

2. A third-party connector

An independent app sits between Shopify and the operations system, built by a company that specialises in connecting the two.

These can be good, and are sometimes more capable than a vendor's own integration. The trade-off is a third party in the chain. You are paying two subscriptions, and when the sync fails you may be working out which side the fault sits on before anyone starts fixing it. It is worth knowing how long that connector's company has supported this particular pairing.

3. A middleware platform

An integration platform handles the mapping between systems, and typically between several others as well.

Middleware is flexible and can accommodate unusual requirements. It also adds a platform to pay for, learn and maintain, and the mappings it holds become their own body of knowledge. If one person configured them, that dependency is real. Middleware tends to suit businesses with genuinely non-standard flows rather than those who simply want orders and stock to move.

4. A custom API build

A developer or agency builds the connection for you.

It fits closely, because it was written to. The cost tends to land later: Shopify's API versions change, and a build that nobody has been paid to maintain can drift out of date until something stops working. Before choosing this route, it is worth knowing who maintains it in year three, and what happens if that agency is no longer available.

The Questions That Separate Them

Whichever route a vendor proposes, these are the ones worth asking directly.

• How often does inventory sync, and is it event-driven or scheduled? A scheduled sync every fifteen minutes is fine most weeks and can be a problem during a flash sale.
• What happens to order edits and refunds? Orders often change after they are placed. Ask whether an edit or a refund processed in Shopify creates the matching record in the operations system automatically, or whether someone re-keys it.
• How does it handle multiple Shopify locations? If you hold stock in more than one place, ask how locations map, and what happens when you add one.
• Does it support Shopify B2B and Shopify Markets? If wholesale or international selling is on your roadmap, this is worth settling during evaluation rather than after. Price lists, payment terms and market-specific pricing are where integrations tend to stop short.
• What are the throughput limits? Ask what happens when order volume is several times normal for a sustained period. Integrations have a ceiling somewhere, and peak tends to be where it is found.
• Who fixes it, and how quickly? Get the support path in writing: who takes the call, what the response time is, and whether integration faults sit inside the same agreement as the rest of the product.
• What happens when Shopify releases a breaking change? Ask how the last one was handled and how long it took.

The answers tend to matter more than the label. A well-maintained third-party connector may serve you better than a native integration that covers less of what you need.

Where the Financial Data Goes

One thing worth checking alongside the operational sync: what reaches your ledger, and in what shape.

Payouts, fees, refunds and cost of goods still have to be reconciled, and an integration that moves orders cleanly but leaves finance rebuilding the month from exports has only solved part of the problem. We covered this in more detail in bridging the gap between Shopify and your accounting software.

What a Native Shopify Integration Looks Like in Practice

Brightpearl by Sage is a Retail-First ERP System, which means inventory, orders, fulfilment and accounting sit in one system built around how retail businesses actually operate, rather than a general-purpose ERP adapted to fit.

For Shopify, it takes the first of the four routes above. The integration is built and maintained by Brightpearl and published on the Shopify App Store, so the connection sits inside the product rather than in a separate contract with a separate company to call when something goes wrong.

Put against the questions earlier in this post, here is what Brightpearl describes it as handling:

• Orders, created in Brightpearl against new or existing customers, with Shopify order edits reflected back rather than re-keyed.
• Inventory, with quantities sent to Shopify so availability stays accurate, and multi-location inventory mapping for stock held in more than one place.
• Returns, creating a sales credit and refund automatically.
• Shopify POS orders, fulfilled automatically alongside online orders.
• Pricing and currency, managed per Shopify account in that account's currency, across multiple Shopify stores.

That covers a good deal of the day-to-day, which is the point of a connection you are not maintaining yourself.

Brightpearl is also built for wholesalers as well as retailers, so if B2B is part of your mix, trade orders, price lists and multi-currency accounting sit in the same system as your DTC trade rather than in a second one alongside it.

Ready to see how the Shopify connection actually works?

Discover how Brightpearl connects to Shopify and keeps your inventory, orders and accounting in step. Book a demo today.