PLATFORMS · 3 min read ·

Connecting Shopify to an ERP or inventory system: Linnworks, Brightpearl, NetSuite and the decisions that matter

Which data should flow between Shopify and your ERP or inventory system, which side owns what, how connectors differ, and the edge cases — bundles, partial shipments, refunds, multi-currency — that break integrations in practice.

Shopindev Team

Past a certain size, Shopify is rarely the only system in the business. Stock, purchasing, warehouse picking, marketplaces and accounting run somewhere else, and the integration decides whether stock levels are right, orders reach the warehouse and finance can close the month without spreadsheets. Connectors exist for the common systems. None of them makes the decisions for you.

Start with data ownership

Every field needs exactly one system of record. When a price is maintained in two places, the wrong one eventually wins. A typical split that works:

DataUsually owned byDirection
SKU, barcode, cost priceERP / inventory systemERP → Shopify
Product copy, images, SEO fieldsShopifystays in Shopify, never overwritten
Selling priceERP or Shopify — pick oneone direction only
Stock levelsERP / inventory systemERP → Shopify, near real time
Orders and customersShopifyShopify → ERP
Fulfilment status and trackingERP / warehouseERP → Shopify, triggers the shipping email
Invoices and payoutsAccounting systemvia the ERP or a tool such as A2X

The most common conflict is product content. Many connectors can push descriptions from the ERP; if your marketing team edits copy and SEO fields in Shopify, the next sync erases their work. Restrict what the connector is allowed to write.

The common options

  • Linnworks: popular with UK multichannel sellers; manages stock and orders across Shopify, Amazon and eBay with a direct Shopify integration.
  • Brightpearl: retail operations and inventory for growing brands, with a Shopify integration covering products, stock, orders and fulfilment.
  • NetSuite: usually connected through Oracle's NetSuite Connector or an integration platform such as Celigo; flexible, but needs careful field mapping.
  • Accounting only: Xero and QuickBooks connect through their own apps or settlement tools such as A2X, which reconcile Shopify payouts with fees and refunds.
  • Custom integration via the Shopify Admin API: worth it for an in-house ERP, unusual processes or when a connector misses a core function.

Before choosing, read a connector's recent reviews and changelog. For an integration every order passes through, responsive support matters more than the feature list.

Where integrations break

Variants and options

Shopify allows three options and up to 2,048 variants per product. ERPs often model parent and child items with any number of attributes. A product with four attributes either fails to sync or creates duplicates. Map the structure first, and make sure every SKU is unique.

Bundles and kits

A three-item bundle is one product in Shopify and three stock lines in the warehouse. Whether the connector explodes bills of materials or treats the bundle as its own SKU decides whether stock stays accurate.

Partial shipments, cancellations and refunds

Test more than the happy path: a backordered line shipped later, a cancelled item, a return received at the warehouse, a refund issued in Shopify. Each movement has to land on both sides or stock, invoices and refunds drift apart.

Multi-currency and tax

If you sell to the EU or the US from the UK, orders arrive in several currencies and with different tax treatment. Decide whether the ERP records the presentment currency or your base currency, and check that VAT and duties map to the right ledger codes. Our guide to selling to the US after de minimis ended covers the duty side.

Sync frequency

A stock sync every 30 minutes oversells during a promotion when you also sell on marketplaces. Ask how often stock syncs and whether orders reserve stock immediately.

How we run an integration

  1. Agree data ownership field by field and write it down.
  2. Choose a connector — or decide a custom integration is needed.
  3. Clean the catalogue: unique SKUs, variants within three options, barcodes populated.
  4. Run test orders for the standard, partial, cancelled, refunded and international cases.
  5. Launch and watch the first days closely: stock variances, missing orders, error logs.

Planning a replatform at the same time? Build the integration into the migration plan — see what breaks in a Shopify migration. Where no connector fits, we build the integration as a custom Shopify app.

This article is part of The Shopify platform, explained — every article on that subject, with the questions it answers, on one page.

Chat on WhatsApp →

FAQ

Questions on this topic

Does Shopify have a built-in ERP?

No. Shopify manages products, stock per location, orders and customers, which is enough for many single-channel stores. Purchasing, warehouse operations and multichannel stock usually need an ERP or inventory system.

Which system should own stock levels?

The system closest to the physical stock — usually the ERP or warehouse system. Shopify then receives stock updates rather than calculating them.

Is Linnworks or Brightpearl better for Shopify?

It depends on the business. Linnworks is strong for multichannel marketplace sellers; Brightpearl for retail operations with wholesale and accounting needs. Test both against your own order types.

When is a custom integration worth it?

When you run an in-house or niche ERP, have processes a connector cannot model, or need data a connector does not sync. We quote it in writing after an audit.