Shopify ERP Integration: NetSuite, Business Central and Brightpearl Compared

You have outgrown the spreadsheet and your accountant's patience. Orders arrive from Shopify, a marketplace and a wholesale channel, stock lives in two places, and month-end takes a week. Shopify ERP integration is the fix everyone points to, and it is also the least well explained thing you will price up this year.

This is an honest comparison of the three systems UK Shopify brands most often weigh up: NetSuite, Microsoft Dynamics 365 Business Central and Brightpearl by Sage. None of them wins outright. Each suits a different kind of business, and the integration decisions you make in week one decide how much pain you have in year two.

What a Shopify ERP integration actually moves

Strip away the vendor language and an integration moves seven kinds of data. For each one you need to decide which system owns it. That decision, the direction of truth, causes most of the problems people later blame on the connector.

Products and variants. Usually the ERP owns the catalogue master (SKU, cost, supplier) and Shopify owns the merchandising layer (titles, images, descriptions). Letting both systems edit both is a common mess.Inventory across locations. The ERP or warehouse system should own stock. Shopify receives available-to-sell quantities, it does not decide them.Orders. Shopify creates them, the ERP receives them. Edits after the fact, such as address changes or added items, are where the flow gets untidy.Fulfilments. The ERP or WMS ships, then pushes tracking back so Shopify can send the customer notification on time.Returns and refunds. Usually initiated in Shopify or a returns app, financially settled in the ERP. Decide who triggers the restock.Customers. Shopify creates them. The ERP may need them for credit terms and B2B. Decide early whether guest checkouts become ERP customers at all.Financial postings. Sales, payouts, fees, tax and refunds land in the ledger, ideally as summarised daily journals rather than one entry per order.

If you write nothing else down before talking to vendors, write down that list with an owner against each line. It will save you a lot of money.

NetSuite and Shopify: the enterprise default

NetSuite is where brands go when they have multiple entities, multiple currencies and a finance team that wants proper consolidation. Oracle's own NetSuite ERP Connector, previously FarApp, is a SuiteApp with a basic tier listed at around $200 a month and a B2B tier at roughly $900 a month that adds invoice posting and wholesale order sync. Celigo is the other common route. It prices by integration flow, and a Shopify to NetSuite setup typically lands between $1,500 and $3,000 a month.

Timelines follow the amount of bending you need. Expect 2-4 weeks for a pre-built connector configured as it comes, 5-8 weeks for a standard Celigo implementation, 8-14 weeks with customisation, and 12-24 weeks or more for custom SuiteScript. Budgets follow the same curve. The connector is the cheap part. The NetSuite licence and the partner implementation are what you are really paying for, and a brand doing under a few million in revenue rarely gets that money back.

Fit: multi-entity, multi-currency, wholesale plus DTC, and a finance function that needs the ERP to be the general ledger. Not a fit if what you mainly need is stock control and order routing.

Business Central and Shopify: the mid-market option people underrate

Microsoft built its own Shopify Connector into Business Central in 2022 and includes it at no extra licence cost with Essentials or Premium on the cloud version. It syncs products, variants, barcodes, prices, inventory, orders (online, POS and B2B), fulfilments with tracking, returns, refunds and cancellations, and it can run several Shopify stores from one Business Central company. Microsoft updates it with every release wave, and the October 2025 version moved to Shopify's newer inventory API with Business Central treated as the source of truth for stock.

The honest caveats. It is a connector, not a full commerce operations layer. Complex bundles, sophisticated returns workflows and heavy customisation of the sync usually mean a Business Central partner writing extensions, or a middleware layer on top. And because Microsoft owns the connector, you follow their roadmap rather than paying a vendor to prioritise your feature. It also only works with the cloud version, so on-premise Business Central is out.

Fit: UK brands already in the Microsoft ecosystem, or moving off Sage 50 or Xero because finance has outgrown them, with one entity or a handful and a warehouse they run themselves. For a lot of Scottish and UK mid-market retailers it is the most cost-effective serious option on this list.

Brightpearl and Shopify: retail operations first

Brightpearl is not really an ERP in the NetSuite sense. Sage, which bought it in 2022, calls it a retail operating system: order management, inventory, purchasing, warehouse, returns and accounting, designed around multichannel retail rather than general business finance. Its Shopify and Shopify Plus integration is first-party and handles multiple stores under one account, and the automation rules for order routing and drop shipping are genuinely strong.

Pricing is no longer published. Industry estimates put it at roughly $1,000 to $3,000 a month with implementation from $10,000 to $50,000, and the entry tier has caps (around 1,500 orders a month, five users, five channels) that push costs up as you grow. Brightpearl positions itself for retailers trading about $1M a year and above.

Fit: multichannel retailers of finished goods who want operations and finance in one place without the weight of NetSuite, and who value retail workflows over ledger depth. Less of a fit if you manufacture, have multiple legal entities or need serious financial consolidation.

Three ways to connect: connector, iPaaS or custom

Whichever system you choose, the connection route is a separate decision, and it matters as much.

Vendor or app connector. Cheapest and fastest. Right when your data model is standard and you are willing to bend your process to the connector rather than the other way round. Wrong when you have bundles, kits, complex pricing or unusual fulfilment logic.iPaaS platform (Celigo, Patchworks, Boomi and similar). A monthly platform fee buys mapping flexibility, retries, error queues and alerting. Right when you are joining three or more systems or transforming data between them. Wrong when you are paying a platform fee for two flows a connector would handle.Custom build. Right when your process is genuinely unusual and is part of your competitive advantage. Wrong for almost everyone else, because you now own an integration nobody outside your team understands. If you go this way, treat it as a product with an owner, not a project with an end date. Our Shopify app development work often starts with talking people out of this.

Where Shopify ERP integrations actually break

The comparison above is the easy part. The failure modes below are what should shape your scoping call, because every one of them has cost a real brand real money.

SKU mismatches. Different casing, a trailing space, a variant that exists in one system and not the other. The customer pays in Shopify, the ERP rejects the order, and nobody notices until the complaint arrives.Multi-location stock. If the ERP pushes one total but Shopify has three locations, orders route to a location with no stock. Map ERP locations to Shopify locations explicitly, and decide what happens to in-transit and reserved stock.Partial fulfilments and split shipments. Many integrations were built for one order, one shipment. Two parcels from two warehouses, or three of five items shipped today, need different logic.Bundles and kits. A bundle sold as one SKU in Shopify may need to explode into three components in the ERP for stock deduction. We covered the storefront side in Shopify bundles and kits. The back office side has to match it.Exchanges. An exchange is a refund and a new order pretending to be one thing. Decide which system creates the new order and how the ERP sees the money.Tax and multi-currency. Shopify Markets sells in euros, the ERP reports in sterling, and someone has to decide which exchange rate wins and how UK VAT and EU VAT post. Settle this before go-live, not at year end.The 2am sync failure at peak. A token expires, an API rate limit hits, a webhook is missed. Whatever you build, you need answers to three questions: how will we find out, who gets woken up, and can we replay the missed orders without creating duplicates?

Most integration problems are process problems wearing a technical costume. The sync did what it was told. The problem is nobody agreed what to tell it.

Which one suits you

NetSuite: multi-entity, multi-currency, wholesale and DTC together, finance-led, and a budget for a proper partner implementation.Business Central: one or a few entities, Microsoft ecosystem, own warehouse, wants a serious ledger at a sensible cost.Brightpearl: multichannel retail operations first, finished goods, wants retail workflows and accounting in one place.

If you also sell wholesale, read what is actually involved in Shopify B2B before you choose. Company accounts, price lists and payment terms change the integration scope considerably.

One last unglamorous point. An ERP integration does not sell anything. It stops you losing money and time in the back office, which is worth doing, but it will not lift a plateaued store. Most Shopify brands we meet in Glasgow and across the UK do not have a traffic problem, they have a conversion problem, and the ERP project has a habit of absorbing a year of attention the storefront needed. Get the integration right, then get back to the front end. Our Conversion Growth Retainer exists for that second half.

If you are scoping an ERP integration and want a second opinion on direction of truth, connection route or a vendor's quote, get in touch. Twelve years and a hundred-plus projects have taught us where these go wrong, and we would rather you found out from us than from your first peak season.