At some point, every growing ecommerce brand hits a wall. The spreadsheets that used to manage inventory are no longer keeping up. Orders are being manually re-keyed from Shopify into the accounting system. Stock levels on the website diverge from what is actually in the warehouse. The finance team is reconciling data across three different platforms and still finding discrepancies.
That wall is the point where you need ERP integration.
ERP (Enterprise Resource Planning) systems like NetSuite, SAP Business One, and Brightpearl are designed to be the single source of truth for your business operations: inventory, purchasing, accounting, fulfilment, and financial reporting. When connected properly to Shopify, they eliminate the manual data entry, reduce errors, and give you real-time visibility across the entire business.
When connected poorly, they create a different kind of nightmare entirely. We have rescued integrations where orders were being duplicated, inventory was going negative, and VAT calculations were failing silently. The difference between a good integration and a bad one is not the technology — it is the data architecture decisions made at the start of the project.
Why ERP integration matters
The case for ERP integration is fundamentally about data integrity and operational efficiency. Without it, you are maintaining the same data in multiple systems and relying on humans to keep them in sync. Humans make mistakes. At volume, those mistakes become expensive.
The cost of manual data entry
A UK brand processing 200 orders per day spends roughly 2-3 hours of staff time manually entering those orders into their accounting system. That is 15 hours per week, or approximately £15,000-£20,000 per year in labour cost. And that is just order entry — it does not include the time spent correcting errors, reconciling discrepancies, or investigating missing orders.
The error rate on manual data entry is typically 1-3%. On 200 orders per day, that is 2-6 errors daily. Each error takes 10-15 minutes to identify and correct. The compounding effect of those errors — incorrect inventory levels, wrong financial reports, customer complaints about stock availability — creates costs that are harder to quantify but often larger than the direct labour cost.
Real-time inventory accuracy
Inventory accuracy is the most compelling reason for ERP integration. When your ERP and Shopify share real-time inventory data, you eliminate overselling (selling products you do not actually have in stock) and underselling (showing products as out of stock when they are available). Both cost revenue. Overselling creates customer service problems. Underselling is lost revenue that you never even know about.
For brands selling across multiple channels — Shopify, Amazon, wholesale, retail — centralised inventory management through the ERP is essential. Without it, every sale on one channel needs to be manually reflected on every other channel. At scale, this is impossible to maintain accurately. The integration between your ERP and Shopify is one part of a broader multi-channel commerce strategy.
Integration architecture patterns
There are three fundamental approaches to connecting Shopify with an ERP. The right choice depends on the complexity of your requirements, the volume of data, and your budget for ongoing maintenance.
Direct API integration
A direct integration connects Shopify and the ERP via their respective APIs with custom code acting as the bridge. This approach offers the most flexibility and the best performance, but it is also the most expensive to build and maintain.
Direct integrations are appropriate when your data mapping is complex, your order volume is high (thousands per day), or your business rules require logic that middleware platforms cannot accommodate. The custom code handles data transformation, error handling, retry logic, and conflict resolution.
// Simplified order sync: Shopify to ERP
async function syncOrderToERP(shopifyOrder) {
// Transform Shopify order to ERP format
const erpOrder = {
externalId: shopifyOrder.id,
customer: mapCustomer(shopifyOrder.customer),
lineItems: shopifyOrder.line_items.map(mapLineItem),
shipping: mapShippingAddress(shopifyOrder.shipping_address),
tax: calculateUKVAT(shopifyOrder),
currency: 'GBP',
channel: 'SHOPIFY_WEB'
};
// Send to ERP with retry logic
return await retryWithBackoff(
() => erpClient.createSalesOrder(erpOrder),
{ maxRetries: 3, baseDelay: 1000 }
);
}Middleware-based integration
Middleware platforms like Celigo, Patchworks, or Alumio sit between Shopify and the ERP, providing pre-built connectors, visual data mapping tools, and monitoring dashboards. They dramatically reduce development time and make the integration accessible to non-technical staff.
The trade-off is flexibility. Middleware platforms handle standard scenarios well, but they struggle with complex business logic, unusual data transformations, or high-volume scenarios where processing latency matters. They also add an ongoing subscription cost of £200-£1,000 per month, depending on the platform and data volume.
Hybrid approach
Many of the best integrations use a hybrid approach: middleware for standard data flows (orders, inventory, products) and custom code for complex business logic (tiered pricing, custom fulfilment rules, multi-warehouse allocation). This combines the speed of middleware with the flexibility of custom development.
Core data flows
Every Shopify-ERP integration handles the same fundamental data flows. Understanding these flows and their direction is essential for a successful implementation.
Product data: ERP to Shopify
The ERP is typically the master for product data. Product titles, descriptions, SKUs, pricing, and categorisation are managed in the ERP and pushed to Shopify. This ensures consistency across all channels and prevents the Shopify store from drifting out of sync with the product catalogue.
The challenge is that the ERP's product data model rarely maps directly onto Shopify's. Shopify has products with variants, metafields, and collections. Your ERP has items with attributes, categories, and price lists. The data transformation between these models is where most complexity lies.
Inventory: ERP to Shopify
Inventory levels flow from the ERP to Shopify, typically in near real-time. When stock is received, counted, transferred between warehouses, or adjusted, the ERP pushes the updated levels to Shopify. Shopify's inventory API supports multi-location inventory, which aligns with ERP warehouse structures.
The critical design decision is whether to sync total available inventory or allocate a portion to each channel. Brands selling on multiple platforms often reserve a percentage of stock for each channel to prevent overselling during high-traffic periods.
Orders: Shopify to ERP
When a customer places an order on Shopify, the integration pushes that order to the ERP as a sales order. This is typically the most critical data flow because it triggers fulfilment, generates invoices, and updates financial records.
Order synchronisation needs to handle edge cases: partial refunds, order edits after placement, exchanges, and multi-currency transactions. For UK merchants, VAT handling is particularly important — the integration needs to map Shopify's tax calculations to the ERP's VAT codes correctly, including handling zero-rated items, reduced-rate items, and the VAT registration threshold.
Customer data: bidirectional
Customer data often flows in both directions. New customers created on Shopify are synced to the ERP. Customer account changes in the ERP (credit limits, payment terms, trade pricing) are reflected back in Shopify. This bidirectional flow requires careful conflict resolution — what happens when the same customer record is updated in both systems simultaneously?
Fulfilment and tracking: ERP to Shopify
When the warehouse ships an order, the ERP generates tracking information. This needs to be pushed back to Shopify so the customer receives shipping notifications and can track their delivery. Shopify's fulfilment API supports partial fulfilment (shipping some items now and the rest later), which needs to be mapped from the ERP's equivalent concept.
NetSuite and Shopify
NetSuite is the most common ERP we see in enterprise Shopify deployments. It is a full-featured cloud ERP with strong financial management, inventory, and purchasing modules. The integration with Shopify is mature, with multiple middleware options and a well-documented API.
Where NetSuite excels
NetSuite's financial reporting is exceptional. Once the integration is running, your finance team gets real-time visibility into revenue, cost of goods, margins, and cash flow across all channels. The multi-subsidiary and multi-currency features are valuable for UK brands selling internationally.
NetSuite's SuiteScript customisation platform allows you to add custom business logic inside the ERP itself. This is useful for complex scenarios like tiered wholesale pricing, automatic purchase order generation, or custom allocation rules that depend on ERP data not available in Shopify.
Where NetSuite is challenging
NetSuite's API has rate limits and can be slow for large data volumes. Syncing thousands of products or processing hundreds of orders per hour requires careful pagination and queuing. The learning curve for SuiteScript is steep, and NetSuite consultants are expensive in the UK market (£150-£250 per hour).
The item record structure in NetSuite does not map cleanly to Shopify's product-variant model. A "matrix item" in NetSuite (equivalent to a product with variants) requires specific configuration to sync correctly with Shopify variants. Getting this mapping right at the start of the project is critical.
SAP Business One and Shopify
SAP Business One is popular with UK manufacturers and distributors. It is less common in pure retail than NetSuite, but it is the right choice for brands that manage significant manufacturing or supply chain operations alongside their ecommerce channel.
Integration considerations
SAP B1's Service Layer API is modern and REST-based, making it relatively straightforward to integrate with Shopify. However, SAP B1 is typically hosted on-premise or in a private cloud, which adds network complexity. The integration needs to handle VPN connections, firewall rules, and the potential for the SAP server to be unavailable during maintenance windows.
SAP B1's strength is in bill-of-materials (BOM) management and production planning. For brands that manufacture their own products, the integration can trigger production orders based on Shopify sales velocity, automatically generating purchase orders for raw materials when stock levels drop below reorder points.
Brightpearl and Shopify
Brightpearl (now part of Sage) is purpose-built for retail and ecommerce operations. It is the ERP that most naturally fits with Shopify because it was designed with ecommerce data flows in mind from the start.
Why Brightpearl works well with Shopify
Brightpearl offers a native Shopify connector that handles the most common data flows out of the box. Product sync, inventory sync, order import, and fulfilment tracking work with minimal configuration. This makes it the fastest ERP to integrate and the easiest to maintain.
For UK brands doing £1M-£10M in annual revenue, Brightpearl often hits the sweet spot: sophisticated enough to handle multi-channel inventory, warehouse management, and financial reporting, but not so complex that it requires a dedicated ERP administrator. The total cost of ownership is typically 30-50% less than NetSuite over a three-year period.
Where Brightpearl falls short
Brightpearl lacks the depth of NetSuite in financial management, multi-entity consolidation, and advanced manufacturing features. If you need multi-currency accounting, complex intercompany transactions, or deep supply chain planning, Brightpearl may not be sufficient. It is an excellent operational ERP for retail, but it is not a full enterprise finance platform.
Middleware platforms compared
For most Shopify-ERP integrations, middleware is the right approach. Here is how the main platforms compare.
| Platform | Best for | Shopify connector | Typical cost |
|---|---|---|---|
| Celigo | NetSuite integrations | Excellent | £500 - £1,500/mo |
| Patchworks | UK ecommerce brands | Very good | £300 - £800/mo |
| Alumio | Complex multi-system | Good | £400 - £1,000/mo |
| Make (Integromat) | Simple scenarios | Basic | £30 - £150/mo |
The middleware choice should be driven by your ERP, not your ecommerce platform. All of these tools integrate well with Shopify. The differentiator is the quality of their ERP connectors, monitoring capabilities, and error handling.
Implementation process
A successful ERP integration follows a structured process. Skipping steps — particularly data mapping and testing — is the primary cause of integration failures.
Phase 1: Data audit and mapping (2-3 weeks)
Before any development begins, you need a complete understanding of the data in both systems. This means auditing every field in the ERP that needs to appear in Shopify (and vice versa), defining the transformation rules, and documenting how edge cases will be handled.
Pay particular attention to product data models, SKU formats, pricing structures, and inventory location hierarchies. These are the areas where the two systems are most likely to disagree, and getting the mapping wrong here will cause problems throughout the integration.
Phase 2: Build and configure (3-6 weeks)
Development proceeds data flow by data flow: products first, then inventory, then orders, then fulfilment, then financial data. Each flow is built, tested independently, and validated against real data before moving to the next. This sequential approach prevents cascading errors where a problem in product sync corrupts everything downstream.
Phase 3: Parallel running (2-4 weeks)
Before going live, run the integration in parallel with your existing manual processes. Both systems process the same data, and your team compares the results. This catches edge cases that testing did not anticipate and builds confidence that the integration is working correctly.
Parallel running is where most brands try to cut corners, and it is where most integration failures originate. Two weeks of parallel running has saved us from every major integration issue we have ever encountered. As part of your broader Shopify development project, building adequate testing time into the timeline is essential.
Phase 4: Go-live and monitoring (1 week)
Go-live should be anticlimactic. If parallel running went well, switching to the live integration is a matter of turning off the manual process and monitoring the automated one. Set up alerts for failed syncs, data discrepancies, and processing delays. The first week post-launch requires close monitoring, with someone available to investigate and resolve issues quickly.
Common pitfalls and how to avoid them
We have implemented dozens of ERP integrations. The same mistakes appear repeatedly.
Treating inventory as a simple number
Inventory is not just "how many do we have". It is a complex concept that includes available stock, allocated stock (reserved for existing orders), stock in transit, stock on purchase orders, and damaged stock. Your ERP tracks all of these. Shopify needs the available-to-sell number. Getting this calculation wrong means either overselling or understating your available inventory.
Ignoring VAT complexity
UK VAT is straightforward for domestic B2C sales, but it becomes complex with zero-rated items, reduced-rate items, B2B transactions, EU and rest-of-world exports, and the interaction between Shopify's tax engine and the ERP's VAT module. The integration needs to handle all of these scenarios correctly, or your VAT returns will be wrong.
Not planning for failures
APIs fail. Networks drop. ERPs go down for maintenance. A production-grade integration handles all of these scenarios gracefully: queuing failed operations, alerting the team, retrying automatically, and providing tools to manually reprocess failed items. If your integration does not handle failures, it is not production-ready.
Underestimating data migration
If you are implementing an ERP and Shopify simultaneously, you need to migrate existing data into both systems. Historical orders, customer records, product data, and inventory levels all need to be loaded, validated, and reconciled. This process typically takes longer than anyone expects. Budget at least 2-3 weeks for data migration alone, and also consider how this connects with a custom app if bespoke data transformations are required.
Understanding the right approach for your PIM data is equally critical — if you are managing product information across systems, read our guide to PIM integration with Shopify for complementary guidance.
The best ERP integrations are invisible. The team does not think about them because they just work. Getting there requires unglamorous work: meticulous data mapping, thorough testing, and robust error handling. There are no shortcuts.
Andrew Simpson, Founder
ERP integration is one of the highest-value investments a growing ecommerce brand can make. It eliminates manual work, reduces errors, and gives you the operational visibility you need to make better decisions. But it needs to be done properly, with careful architecture, thorough testing, and realistic expectations about timeline and budget.
If you are considering connecting your ERP to Shopify, get in touch. We will assess your specific setup and give you an honest recommendation on the best approach for your business.
