Shopify ERP Integration: The 2026 Guide for B2B Operators

Shopify ERP integration connects your Shopify store to your enterprise resource planning (ERP) system, so products, inventory, prices, customers and orders move between them without anyone retyping them. Shopify runs the storefront and checkout. The ERP stays the system of record for finance and inventory.

This guide draws on Shopify's, Microsoft's and Infor's own documentation as it read in October 2026. It adds what Uncap, a Shopify Platinum Partner with 380+ storefronts launched on Shopify, sees on B2B builds.

Key takeaways

• Shopify is not an ERP. Shopify's own answer is "No." The two connect, and the ERP keeps the books.
• Three ways to connect: direct integrations from the App Store, iPaaS providers in the middle, or custom builds on Shopify's B2B APIs.
• B2B is the test: Shopify warns that some App Store integrations "aren't fully compatible with Shopify B2B, specifically companies and catalogs."
• Two costs: the connector or platform subscription, and the implementation.
• Decide before you build: name the system of record and sync direction for every object first.

What is Shopify ERP integration? (And is Shopify an ERP?)

ERP integration is the connection that keeps your commerce platform and your back office working from the same data. On Shopify, the store and the ERP exchange records in both directions. An order placed online becomes a sales order in the ERP. A stock change in the ERP shows up on the storefront.

Is Shopify an ERP? Shopify's own answer is short. Its enterprise blog says: "Is Shopify an ERP? No. Shopify is a commerce platform that runs the customer-facing layer: storefront, checkout, point of sale, and order capture." It adds: "The ERP remains the system of record for finance and inventory." So the thing you actually design is how the two share data.

Shopify's page on integrating external systems with Shopify B2B sets the scope. You can connect your ERP, CRM and other systems "to sync customer data, orders, inventory, product catalogs, and pricing information."

For example, a buyer at a regional distributor orders 40 cases at 9 p.m. The order reaches the ERP with the buyer's PO number, the warehouse picks it the next morning, and the tracking number shows up in the buyer's Shopify account. Nobody rekeyed the order, and nobody had to call to ask where it was. That is what ecommerce ERP integration should feel like from the buyer's side. None of it works until someone decides which system owns each record, its system of record.

What data syncs between Shopify and your ERP

In Uncap's builds, most B2B integrations move the same eight kinds of records. What changes is the direction each one flows and how fresh it must be. The usual starting point looks like this:

• Products: SKUs, units of measure and attributes start in the ERP. Shopify adds images, storefront copy and SEO fields.
• Inventory: counts flow from the ERP to Shopify, per warehouse.
• Prices and catalogs: price lists and customer-specific prices start in the ERP and land in Shopify B2B catalogs.
• Companies and customers: new accounts can start on either side, so settle this one early.
• Orders: web orders go to the ERP. Orders reps enter in the ERP often need to come back, so buyers see their full history.
• Fulfillments: shipment and tracking data flow from the ERP to Shopify.
• Payment terms and status: terms must agree on both sides, and paid invoices must update Shopify.
• Refunds, transactions and payouts: these flow to the ERP so finance can reconcile.

Connectors make these choices for you, and they differ. Shopify's Help Center lists the directions for each direct integration, such as the NetSuite ERP Connector:

• Both ways: orders and order updates, catalogs and price lists, payment status, refunds and cancellations.
• NetSuite to Shopify: fulfillments, inventory and products.
• Shopify to NetSuite: historical orders, PO numbers, payment terms, draft orders, companies and customers, transactions and payouts.

Now compare Microsoft Dynamics 365 Business Central in the same table. There, companies and customers sync both ways, while catalogs and price lists flow from Business Central to Shopify only. If your sales team opens new accounts in the ERP, Shopify's NetSuite table lists no flow that sends those companies to Shopify.

The rule we hold every project to: decide and document the sync direction for each object before the build. Changing it after go-live means re-testing every flow that touches that record.

Why B2B changes the integration

A consumer integration moves orders, stock and a thin customer record. B2B adds a data model, starting with the account. Shopify's Help Center defines a company as "the parent organization for one or more company locations," and says each location "can have its own tax ID, tax exemptions, ship-to address, billing address, pricing, payment terms, checkout settings, and contacts." Your ERP may hold that same account as a single customer number with several ship-to addresses, and someone has to decide how one maps onto the other.

Then come the B2B specifics that, in our projects, shape the integration most:

• Customer-specific prices: contract prices and quantity breaks usually live in the ERP. Our guide to how ERPs decide what a B2B buyer pays explains why they are calculated, not stored.
• POs and net terms: buyers add a PO number and check out on terms. The ERP needs both on the sales order.
• Credit limits: most distributors we work with manage credit in the ERP, so the storefront has to ask before it accepts an order on terms.
• Orders entered outside the storefront: sales reps key orders into the ERP, and large buyers send them by electronic data interchange (EDI). Buyers expect to see those orders in their account too. Our Shopify EDI integration guide covers the EDI side. A supplier can also report back on those orders with an EDI 870 Order Status Report, which X12 says can report the current status of an entire purchase order or "selected line items on a purchase order."

This is where Shopify itself urges care: "Some integrations in the Shopify App Store aren't fully compatible with Shopify B2B, specifically companies and catalogs. This means that B2B company, pricing, and customer data might not map correctly with certain integrations if the integration provider hasn't properly implemented B2B APIs or Customer Accounts."

Shopify B2B runs on the Basic, Grow, Advanced and Shopify Plus plans. Shopify's B2B features by plan page says it "isn't available on the Starter or Retail plans." For apps, Shopify adds: "To access app functionality that interacts with Shopify B2B features, your plan must support B2B capabilities." Our Shopify B2B guide covers what each plan includes.

Three ways to connect Shopify to an ERP

How do you integrate Shopify with an ERP system? Shopify's Help Center names three methods:

• Direct integrations: "You can use direct integrations from the Shopify App Store. This method is available for select ERP, accounting, and Product Information Management (PIM) systems, to quickly integrate without custom development."
• iPaaS providers: an integration platform as a service (iPaaS) sits between the systems. Shopify says these "work as intermediaries between Shopify and your external system."
• Custom APIs: you build on Shopify's B2B APIs. Shopify says this "offers maximum flexibility for unique business requirements or systems without pre-built integrations, but is more resource intensive than the other options."

The labels hide a practical question: where does the integration live? A direct connector is an App Store app built with the system's vendor. An iPaaS is a separate platform in the middle, usually called middleware. A custom build lives wherever you host it, and you own every line.

There is a fourth shape: an embedded Shopify app built for ERP sync. Uncap Connect works this way. It is embedded natively inside Shopify, with no separate middleware platform to maintain, and keeps pricing, inventory, customers and orders current on both sides. The ERP stays the system of record.

In our view, no route wins by default. A connector that fits your ERP and price model beats a custom build, and a custom build beats a connector that forces your sales team into workarounds.

Shopify's Global ERP Program and the official connectors

The App Store collection called the Shopify Global ERP Program is "A suite of certified enterprise resource planning apps to directly integrate with your Shopify store." Shopify's ERP integration article says these apps "undergo a 100-checkpoint review covering security and performance before listing."

In October 2026 the collection lists five apps. Each price below is copied from the app's App Store listing:

• NetSuite ERP Connector, developed by Oracle NetSuite: "From $199.92/month." Plans run from B2C Standard at $199.92 / month to B2B at $916.58 / month, which adds invoice posting, subsequent payment handling, B2B order synchronization and standalone B2B customer sync. The listing says "All charges are billed in USD. Recurring and usage-based charges are billed every 30 days." See our NetSuite Shopify integration page, or our post on NetSuite Connector, iPaaS or custom API for the three ways to connect the two.
• Dynamics 365 Business Central, developed by Microsoft: "Free to install." Microsoft's connector FAQ says "The organization must have both a Business Central license and a Shopify license to use the connector." See our Business Central integration page.
• Acumatica Cloud ERP, developed by Acumatica: "Free to install. Additional charges may apply." See the Acumatica Shopify integration page, or our post on where Acumatica's native connector stops.
• Brightpearl by Sage, developed by Brightpearl: "Free to install."
• Infor eCommerce Connector, developed by Infor: "Free," for Infor M3 CE. Our Infor M3 integration page covers what M3 exposes beyond it.

Two cautions. First, "free to install" describes the app, not the project. The Business Central, Acumatica and Brightpearl listings each say external charges may be billed by the vendor separately from your Shopify invoice, and the mapping and testing work still has to be paid for. Second, a security and performance review says nothing on its own about whether a connector handles your companies, catalogs and terms. You check that against the vendor's documentation.

Where official connectors stop for B2B

Official connectors are documented, so their limits are checkable. Here is what two vendors say.

Microsoft Dynamics 365 Business Central:

• Online only. Microsoft's FAQ: "It isn't available for on-premises deployments."
• Prices for a quantity of 1. Microsoft's price sync page: "Only prices and discounts that are applicable for quantity 1 are used. You can't export different prices or discounts based on quantity."
• B2B prices on Plus. The same page says B2B price synchronization "requires a Shopify Plus subscription."
• Business Central only. The connector "doesn't work with other Dynamics 365 applications, like Dynamics 365 Sales or Dynamics 365 Supply Chain Management." For Finance and Operations, NAV or GP, see our Microsoft Dynamics integration overview.

Infor M3, through the Infor eCommerce Connector:

• Built for consumer orders. Infor's integration guide, version 1.3, published March 2025, calls it "a basic integration supporting a Business-to-Consumer (B2C) engagement model."
• One customer for everyone. "All Shopify B2C accounts are mapped to a single M3 CustomerID, using the Anonymous Customer philosophy in M3."
• Prepaid orders. The guide says "all orders are deemed to be paid in full in advance."
• A daily stock file and new orders only. The guide says Shopify "receives an updated stock file each day from M3," and the listing says "Only newly created Shopify orders are synced with the ERP."

For SX.e, SyteLine and other Infor lines, our Infor integration overview explains the options.

Both connectors copy values into Shopify: a price calculated once, a stock count, a terms code. In our view, B2B runs on decisions the ERP makes when the order is placed. What does this account pay for 60 units under its contract? How many can this branch promise after this morning's counter sales? That is the gap between available to promise and on hand.

Three quick questions tell you whether a connector is enough:

• Is any price negotiated per account or tied to a quantity break?
• Must an order stop when an account is over its credit limit?
• Do reps add or edit orders in the ERP that buyers need to see?

Any yes means you should run the nine-question self-test in our guide to where official Shopify ERP connectors stop.

Connector, middleware, embedded app or custom build: how to choose

The right method depends on your ERP, how standard your B2B rules are, and who owns the integration after launch. This is how we walk operators through it.

• Your ERP has an official connector, and you sell from a list. One price per item or customer group, stock per warehouse, orders that do not change after entry. Start with the connector.
• You already run an iPaaS, or several systems move together. Middleware earns its keep when Shopify, the ERP, a warehouse system and a CRM all exchange data. Farmers Depot, below, connects its ERP through middleware.
• You want the sync inside Shopify, built for B2B. That is Uncap Connect. Field-level rules decide which system wins, every time. A live console shows every sync, flags conflicts and replays anything that fails.
• Your ERP has no connector, or your rules are unusual. Shopify says that in this case "you can build a custom integration using B2B APIs." Before you scope one, read what each ERP's API actually exposes.

SAP, the Sage 100, 300, X3 and Intacct lines, and Odoo have no app in the Global ERP Program collection. That does not make them hard to connect; the work just sits in the integration. Our pages for SAP, Sage and Odoo cover each. For Odoo, scoping a Shopify B2B integration by Odoo apps and edition goes a level deeper.

From our own projects: do not pick a connector just because one exists. A heavily customized ERP can need so many workarounds that another route would have been cheaper from the start. In our experience, picking the wrong method early is what most often forces a rebuild.

Real-time or scheduled sync, and why syncs drift

Should Shopify and the ERP sync in real time? For some records, yes. Others are fine on a schedule. Our test: what goes wrong if the storefront is an hour behind?

• Event-driven: inventory on fast movers, price changes and new orders. A stale stock count oversells. A stale price misprices.
• Scheduled: product content, slow-moving stock and historical orders usually tolerate a batch.
• The connector can set the limit. Infor's M3 guide says Shopify "receives an updated stock file each day from M3," so storefront stock there is only as current as the last file.

Uncap Connect is built for the records that need to move in real time: changes flow both directions in seconds, not overnight.

In our experience, even a well-built sync drifts when nobody owns it. Two systems write to the same stock number. A unit of measure means "each" in one system and "case" in the other. An event fails at 2 a.m. and nobody retries it. Our guide to why Shopify ERP inventory syncs fail walks through eight of these failure modes.

What we recommend is unglamorous. Log every sync, send every failure to a person who will see it, reconcile counts on a schedule, and agree in advance who gets the Saturday alert.

What Shopify ERP integration costs, and how long it takes

A Shopify ERP integration has two costs. In our experience, buyers often budget for only one.

The subscription. On the Shopify App Store in October 2026, the five Global ERP Program apps range from "Free" for Infor's connector to $916.58 / month for the NetSuite ERP Connector's B2B plan. Business Central also needs its own license.

The implementation. This is mapping, configuration, data cleanup, testing and go-live. Uncap publishes its prices on the Shopify ERP integration page for manufacturers and distributors: "Uncap Connect starts at $8,000 to set up and then a flat $390 per month. A managed iPaaS integration starts at $14,000 with a $500 to $2,000 monthly platform cost." The same page adds: "We scope the exact figure to your systems up front."

The time. Uncap Connect's product page lists a "Typical deploy" of "3-5 weeks." In our experience, what moves a date is how clean the ERP's customer, price and item data is, and how fast your team answers mapping questions.

A replatform with the architecture still open. Plan before you build. Uncap Blueprint is a fixed-price migration plan: $7,500 over four weeks, in which a senior team maps the architecture, data taxonomy, SEO preservation, ERP integration, UX prototypes, total cost of ownership and a risk register. If you build with Uncap, the $7,500 is credited one-to-one toward implementation.

Your own team's time won't show up on any invoice. Plan for it anyway, especially for whoever owns customer and price data in the ERP: on our projects, that person fields more questions than anyone else.

Before you start: an ERP integration readiness checklist

Most integration delays we see trace back to an answer nobody had at kickoff. Gather these before you pick a method:

• Your ERP, version and hosting. Connector support depends on them. Microsoft's Business Central connector, for example, "isn't available for on-premises deployments."
• Your Shopify plan. Shopify B2B, and app features that work with it, need Basic, Grow, Advanced or Plus.
• A list of objects. Products, inventory, prices, companies, orders, fulfillments, payment terms and payments, each with a named system of record.
• Your price model, written down. List prices, customer groups, contract prices and quantity breaks, and where each one is calculated today.
• Your credit and terms rules. Who may order on terms, and what should happen when an account is over its limit.
• Every order source. Web, reps keying orders into the ERP, EDI and any punchout, and which of them buyers should see in their account.
• Two owners. One person who answers data questions, and one who receives sync failures.

How to plan a Shopify ERP integration in seven steps

This is the order we work in, whatever the method. In our experience, a skipped step turns up again after go-live, when it costs more.

• 1. Name the system of record for each object. Products, stock, prices, companies, orders, payments. One owner each, written down.
• 2. Map the fields, including the B2B ones. Companies, locations, catalogs, payment terms and PO numbers, not just SKUs. Note every field that exists on one side only.
• 3. Pick the method, using the questions in the section on choosing.
• 4. Set direction and frequency per object. Event-driven where staleness costs money, scheduled where it does not.
• 5. Decide who owns failures. A failed order needs an alert, a person and a way to replay it.
• 6. Test with real accounts and edge cases. A contract-priced buyer, a quantity break, an account on credit hold, a split shipment, a cancelled line.
• 7. Go live, then watch. Reconcile stock and open orders daily for the first weeks.

Uncap Connect's product page describes the same arc in three steps: map every object and field into one shared model, sync in both directions in real time, then monitor every sync from a live console. For inventory in depth, our Shopify ERP sync design spec sets out the seven decisions to make before anyone writes code.

Shopify ERP integration in practice: Uncap projects

These published Uncap builds name the ERP, with facts as each case study states them.

• ULE Group, Epicor. ULE Group runs a B2B catalog of over 250,000 SKUs on Shopify with PIM-managed data and search with 100+ filters. The build integrates the Epicor ERP for real-time product, inventory and pricing updates. Read the ULE Group case study or our Epicor Shopify integration page.
• Kooks, Infor Visual. Shopify was integrated with Kooks' Infor Visual ERP and PDM Automotive PIM, enabling real-time inventory synchronization and vehicle-fitment search by year, make, model and engine. The replatform delivered a 22% conversion rate uplift and a 38% reduction in total cost of ownership. See the Kooks case study and our Infor Visual integration page.
• Farmers Depot, Dynamics 365 F&O. A Shopify Plus B2B build integrated with Microsoft Dynamics 365 F&O through middleware. The ERP stays the system of record while Shopify serves 14,528 customers across 13,046 companies, with about 10 company-specific pricing catalogs and 1,351 synchronized products. See the Farmers Depot case study and our Dynamics 365 Finance and Operations page.
• KBS Golf Shafts, Oracle. Uncap migrated KBS from WooCommerce to Shopify Plus, unifying D2C, B2B and POS on one platform with direct Oracle ERP integration. Read the KBS Golf Shafts case study and our Oracle integration page.
• Kodo Kids, Unleashed. HubSpot CRM, Unleashed ERP and Shopify Plus were fully integrated, and existing customer and company data was transferred without loss. Read the Kodo Kids case study.

Where to start

• Still choosing an ERP? Read our comparison of the best ERPs for Shopify B2B first.
• Already on an ERP with an official connector? Answer the three questions in the connector section. If every answer is no, install the connector and spend your budget elsewhere.
• Moving to Shopify at the same time? Settle the integration route during planning, not after the storefront is live. Uncap Blueprint lists ERP integration mapping among its ten deliverables, and if you finish it without confidence in your migration path, Uncap refunds the fee in full.
• Ready to connect? Uncap connects Shopify to the ERPs manufacturers and distributors run, "including NetSuite, Microsoft Dynamics, SAP, Acumatica, Sage, Epicor, and Infor, through either Uncap Connect or a managed iPaaS integration." The senior crew that builds the integration also supports it.

Not sure which fits? Bring us your ERP, your price model and the orders that cause trouble today. The Uncap team confirms fit for your specific ERP directly.

Talk to Our Experts about your Shopify ERP integration.

Sources

The primary sources this guide cites, each checked on October 22, 2026. Uncap's own prices, timelines and client results come from Uncap's published pages and case studies, linked where they appear above.

• Shopify: What is an ERP?, ERP integration: methods, benefits, and examples
• Shopify Help Center: Integrating external systems with Shopify B2B, Companies and customers in B2B, Shopify B2B features by plan
• Shopify App Store: Shopify Global ERP Program, NetSuite ERP Connector, Dynamics 365 Business Central, Acumatica Cloud ERP, Brightpearl by Sage, Infor eCommerce Connector
• Microsoft Learn: FAQ for technical details (Shopify connector), Synchronize prices with Shopify
• Infor: Infor eCommerce Connector integration guide (PDF)