What Shopify ERP integration actually involves
Connecting Shopify Plus to an ERP is not a plugin install. It is deciding how product data, stock levels, pricing, customer accounts, orders, and invoice status should move between two systems with different data models, different update cadences, and different ownership boundaries. The integration sits between your commercial team (who live in Shopify) and your finance and operations team (who live in the ERP), and it is where most ecommerce projects overshoot their timeline.
The pattern is consistent: teams underestimate the data work and overestimate how much off-the-shelf connectors cover. A connector handles the API plumbing. What it does not handle is your specific catalog structure, your pricing logic, your multi-warehouse setup, or the edge cases in your order flow. That work falls on the integration architecture, and it is what separates an integration that works for six months from one that still works after two years.
The four data flows that matter
Every Shopify ERP integration has to decide how these four flows work. Get them right and most downstream problems disappear.
Product and catalog sync. Who owns the product? If the ERP is the source of truth, products flow from ERP to Shopify. If the merchandising team owns products in Shopify, they flow the other way. Most Nordic B2B setups sync from ERP to Shopify. Most pure D2C setups own product data in Shopify or in a PIM that syncs to both. See our PIM for ecommerce guide for when a dedicated PIM makes sense.
Stock levels. The single most visible flow to customers. Out-of-stock products that show as available trigger order cancellations and support complaints. Real-time stock sync is possible but adds complexity. Most stores can accept 5 to 15 minute lag, which is much easier to implement. The question is not whether to sync, but at what frequency and with what fallback when the ERP is unavailable.
Customer-specific pricing. B2B stores need this natively. The ERP owns the price lists. They attach to company accounts in Shopify Plus B2B. Pricing updates push on a schedule (daily) or on demand via webhook. For complex contract pricing with many dimensions (customer, product family, volume tier, promotion period), the sync logic is where the integration budget goes. See our Shopify B2B guide for how pricing fits into the broader B2B setup.
Orders and invoices. Orders placed in Shopify need to reach the ERP for fulfilment, invoicing, and accounting. The return path carries invoice status, shipping updates, and order adjustments back to Shopify so customers see accurate history. This flow is where most projects have their longest debugging tails. Partial shipments, backorders, refunds, and order modifications all need explicit handling.
Nordic ERP systems and how they connect
Each Nordic ERP has its own integration characteristics. The choice of ERP often predates the ecommerce project, so the question is how to work with what you have rather than what to choose from scratch.
Microsoft Dynamics 365 Business Central. The most common ERP for Nordic mid-market. Strong API support through Business Central web services and OData. Integrates cleanly through middleware or direct custom connectors. Works well with Shopify for both B2B and D2C. Customer-specific pricing, multi-warehouse inventory, and multi-company scenarios are all supported natively.
Fortnox. Dominant for Swedish SMB. Fortnox has a well-documented API and integrates with Shopify through multiple patterns, middleware being the most common. For smaller D2C stores on Shopify, the integration is straightforward. For B2B with complex pricing, Fortnox is lighter than Business Central and requires more integration-side logic.
Visma.net. Cloud-based Nordic ERP with modern API. Integrates well with Shopify through middleware. Multi-market support is one of its strengths, which pairs well with Shopify Markets for multi-country setups.
NetSuite. Enterprise ERP with comprehensive REST and SOAP APIs. Strong fit for mid-market to enterprise Shopify Plus merchants, especially those operating across multiple markets. Real-time sync is possible and often expected.
SAP Business One. Common for Nordic manufacturers and distributors. Integration is heavier than Business Central but well-documented. Fits Shopify Plus for B2B scenarios with complex product configurations.
Integration patterns, direct vs middleware
Two architectural choices cover most Shopify ERP integrations.
Direct point-to-point. Shopify talks to the ERP through a dedicated connector or custom-built integration. Lower initial cost, fewer moving parts. Works well when Shopify is the only commerce system and the ERP is the only business system. Breaks down when you add a WMS, a PIM, a marketing platform, or a second sales channel. Every new system needs its own connector, and maintaining a web of point-to-point integrations becomes expensive fast.
Middleware or iPaaS. A middleware layer (like Junipeer) sits between Shopify and the ERP, with standard connectors on both sides. Adding a WMS means one new connector, not another full integration. Monitoring, error handling, and data transformation happen in one place. Higher initial setup but significantly lower ongoing maintenance as the stack grows.
The tipping point is usually when you have more than two systems to connect, or when the business expects to add systems over time. For a Shopify plus ERP setup that will stay that simple, direct integration is fine. For anything more, middleware pays back within 18 to 24 months.
Real-time versus scheduled sync
Real-time sync is often a requirement people state without fully understanding the cost. It is technically possible for most flows but adds complexity, monitoring overhead, and dependency on both systems being available.
Real-time is worth it for: stock levels in high-velocity stores, customer-specific pricing at login, order status updates that customers expect to see immediately. These flows have direct customer impact when they lag.
Scheduled sync is sufficient for: product catalog updates (hourly or daily), invoice status updates (hourly), customer data sync (daily), historical reporting data. The lag does not affect the customer experience.
The practical middle ground is event-driven sync with a scheduled fallback. Orders push immediately via webhook. Stock updates batch every few minutes. Daily jobs catch anything that failed. This handles real-world API availability issues without making every flow real-time.
Edge cases that break integrations
The integrations that break after launch usually break on the same set of edge cases. Plan for these during architecture, not after.
Multi-warehouse inventory. Stock lives in multiple locations. A product is in stock overall but out in the warehouse serving a specific region. Allocation logic needs to match what the ERP expects.
Backorders and partial fulfilment. Order creates in Shopify with 10 items. ERP can ship 7 now, 3 in a week. How does the customer see this, and how does the payment capture work?
Refunds and returns. Customer returns 2 of 5 items. Refund calculation, stock adjustment, and accounting all need to update across both systems.
Price changes during an active session. Customer puts a product in cart. Price updates in ERP while cart is open. Which price is charged at checkout?
ERP downtime. ERP goes offline for 2 hours during maintenance. Does Shopify keep accepting orders? If yes, how are they synced when the ERP is back? If no, how do customers know?
What Nordic Web Team brings to the integration
We use Junipeer as the integration layer for most Nordic ERP-to-ecommerce setups. Junipeer is an iPaaS purpose-built for ecommerce integration, with connectors for the main Nordic ERPs, WMS, PIM, payment and shipping providers. It replaces the point-to-point pattern with a managed middleware layer that we own and maintain.
But the integration is only one part. A successful Shopify ERP project also involves platform selection (is Shopify the right choice for this B2B model?), data quality review (is the ERP data clean enough to expose to customers?), checkout and account UX design, QA across the full order lifecycle, and a rollout plan that minimises risk. See our general ERP integration guide for the broader picture across platforms.
Timeline and cost
A standard Shopify ERP integration with one commerce platform, one ERP, and standard data flows typically runs €25,000 to €60,000 and takes 2 to 4 months. Add B2B pricing complexity, multi-warehouse inventory, or a second business system and the range moves to €60,000 to €150,000 over 4 to 7 months. For enterprise scenarios with real-time requirements, multi-market setups and custom order logic, budgets from €150,000 upward are realistic.
The cost driver is almost always the complexity of your existing data and business logic, not the Shopify side of the work. Contact us for a scoping conversation tailored to your current ERP and business model.