In short: To connect Shopify B2B to an ERP, map how a B2B order moves through your business, give every data object one system of record, decide what must sync in near real time, then choose a direct connector, an integration platform (iPaaS) or a custom API. Confirm B2B data such as companies, catalogs and payment terms is supported, test edge cases in a sandbox, and add monitoring and reconciliation before launch.
A Shopify B2B launch can look simple from the storefront. Your customers log in, see their negotiated pricing, place an order with payment terms, and receive fulfillment updates.
Behind that experience, however, your ERP may need to coordinate inventory, pricing, customer records, accounting, purchase orders, fulfillment, returns, and payment status. If those systems are not designed to work together, the result is predictable. Inventory becomes unreliable. Sales teams start manually fixing orders. Customers see the wrong price. Finance has to reconcile two versions of the truth.
Best for: Manufacturers, distributors, wholesalers, and hybrid DTC/B2B brands that need Shopify B2B to work reliably with ERP, PIM, OMS, WMS, or 3PL systems.
A Shopify B2B ERP integration is not just a technical connection. It is an operating-model decision. You need to decide which system owns each piece of data, how information moves between systems, what happens when a sync fails, and who is responsible for fixing it.
The short answer: Start by mapping how a B2B order moves through your business, then follow seven steps: (1) define one system of record for every data object, (2) decide what needs to sync and how often, (3) choose a direct connector, integration platform or custom API, (4) map fields and sync directions before building anything, (5) confirm B2B-specific data such as companies, catalogs and payment terms is supported, (6) test normal orders and B2B edge cases in a sandbox, and (7) add monitoring, retry logic and reconciliation before launch.
The biggest mistake is treating an ERP connector like a finished integration strategy. A connector moves data. It does not decide what your data means, which system owns it, or how your team handles exceptions.
What a Shopify B2B ERP integration should accomplish
Your ERP typically holds operational and financial information. Your Shopify store handles the customer-facing commerce experience. For B2B brands, those systems need to stay aligned without requiring the sales or operations team to manually repair every exception.
A solid integration can help you:
- Keep online inventory accurate across warehouses and channels
- Send B2B orders to fulfillment and finance automatically
- Synchronize customer and company records
- Display the right products and negotiated prices for each buyer
- Maintain payment terms and payment status
- Capture purchase-order numbers
- Return shipment, fulfillment, refund, and cancellation updates to Shopify
- Reduce duplicate data entry
- Give the sales team and customer-service team a clearer view of account activity
The goal is not to force every process into Shopify. The goal is to put ecommerce workflows in Shopify while allowing the ERP to keep doing what it does best: finance, procurement, inventory valuation, supplier management, planning, and operational control.
Start with the business process, not the connector
Before evaluating apps or custom development, map the buyer journey and the operational journey that follows it. For a typical B2B order, ask:
- How does a buyer get assigned to a company and location?
- Where does customer-specific pricing originate?
- Which system determines product availability?
- How does an online order get transmitted to the ERP?
- Who reserves inventory?
- How does the warehouse receive the order?
- Where does the shipment confirmation originate?
- How is payment status returned to Shopify?
- How are refunds, cancellations, or partial fulfillments handled?
- What happens when an order fails to sync?
If your team cannot answer these questions, an integration project is not ready to build.
Step 1: Define your system of record
Every important record needs one clear owner. Without a system-of-record model, Shopify and the ERP can overwrite each other, creating inconsistent inventory, duplicate customers, incorrect pricing, and broken order updates.
A common model looks like this:
| Data object | Typical system of record | Why |
|---|---|---|
| Product financial data | ERP or PIM | Cost, supplier, purchasing, and financial records often originate here |
| Customer-facing product content | Shopify or PIM | Storefront copy, images, merchandising, and collections belong close to commerce |
| Inventory | ERP, WMS, or 3PL | The system handling physical inventory has the most reliable count |
| B2B company and buyer access | Shopify or ERP | Depends on whether sales operations or ecommerce manages account setup |
| Catalogs and customer pricing | ERP or Shopify | Depends on how negotiated pricing is maintained |
| Online orders | Shopify captures, ERP fulfills | Shopify receives the order while the ERP manages downstream operations |
| Fulfillment status | ERP, WMS, or 3PL | The system shipping the order should report shipment events |
| Payment terms | Shopify or ERP | Must be assigned to the correct company location and kept consistent |
| Financial records | ERP | General ledger, accounts receivable, tax records, and reporting remain in the ERP |
This table is only a starting point, and your business might need a different model. For example, an ERP may own every price list, while Shopify publishes those prices through B2B catalogs. Another company may maintain online-only merchandising and promotional logic in Shopify while the ERP owns base pricing.
The important rule is simple: one system owns each field. Do not let two systems update the same record without documented conflict rules.
Step 2: Decide what needs to sync
Not every piece of data needs real-time synchronization. Real-time syncing can create cost and complexity where a scheduled batch process would work perfectly well. Prioritize the information that affects revenue, order fulfillment, and customer trust.
Data that often needs near-real-time sync
These records can directly affect the buying experience:
- Inventory availability
- Product availability
- Orders and order updates
- Customer and company account changes
- Catalog access
- Customer-specific pricing
- Payment terms
- Fulfillment status
- Order cancellation status
Data that can often run in scheduled batches
These records usually do not need to update every second:
- Financial reconciliation
- Historical order exports
- Analytics data
- Older customer history
- Archived product records
- Some reporting feeds
The sync frequency should reflect the operational risk. If you sell high-volume inventory across multiple channels, inventory may need to update very quickly. If you update customer price lists monthly, a scheduled job may be completely sufficient.
Step 3: Choose the right integration approach
Shopify B2B supports three broad integration methods: direct integrations, integration platforms (iPaaS), and custom APIs. For which B2B features come with each Shopify plan, and an example of a wholesale setup connected to an Infor ERP, see our Shopify B2B wholesale setup guide.
Option 1: Direct ERP connector
A direct connector is a prebuilt integration between Shopify and a specific ERP. It is often the best starting point when your ERP is supported and your requirements are standard.
Shopify's B2B help center lists direct B2B integrations for:
- Oracle NetSuite (NetSuite ERP Connector)
- Microsoft Dynamics 365 Business Central
- Acumatica Cloud ERP
- Fulfil
- QuickBooks Online
Brightpearl and Infor also connect to Shopify through certified connectors, but they are not on Shopify's B2B direct-integration list, so check that they support B2B before you commit.
Depending on the connector, available sync capabilities can include:
- Companies and customers
- Products and variants
- Inventory
- Catalogs and price lists
- Orders and order updates
- Payment terms and payment status
- Purchase-order numbers
- Fulfillments
- Refunds and cancellations
- Transactions and payouts
Best for: Standard workflows, a supported ERP, a manageable number of systems, and a team that does not need highly customized transformation rules.
Watch out for: Connector features vary. Shopify's own B2B external integrations documentation warns that some App Store integrations "aren't fully compatible with Shopify B2B, specifically companies and catalogs." Confirm the specific connector supports Shopify B2B companies, catalogs, customer accounts, payment terms, and pricing before committing.
Option 2: Integration platform as a service
An integration platform as a service, often called an iPaaS, sits between Shopify and the ERP. It can connect multiple systems while handling field transformations, routing, retries, and error handling in one place.
This is useful when your stack includes more than Shopify and an ERP. For example:
- Shopify storefront
- ERP
- PIM
- WMS
- 3PL
- CRM
- Marketplace feeds
- Multiple regional stores
An iPaaS can make it easier to orchestrate those workflows without building every connection from scratch.
Best for: Multi-system environments, moderate transformation complexity, multiple storefronts, or workflows that require routing and orchestration.
Watch out for: An iPaaS still needs ownership, documentation, monitoring, and a team that understands how to troubleshoot failures.
Option 3: Custom API integration
A custom integration uses Shopify's APIs and webhooks to connect Shopify directly to your ERP or middleware layer. This provides the greatest flexibility. It also creates the greatest long-term responsibility.
Use a custom build when the requirement is genuinely unique, such as:
- Proprietary pricing logic
- Complex product configuration
- Custom account approval rules
- Nonstandard procurement workflows
- Specialized manufacturing or fulfillment events
- An ERP with no viable connector
- A B2B workflow that cannot be supported by a connector or iPaaS
Best for: Unique business requirements that create real competitive value.
Watch out for: Do not build custom integrations just because the business has always done something a certain way. Custom code requires ongoing maintenance, monitoring, version management, testing, and technical ownership.
How long an ERP integration takes
Shopify's ecommerce ERP integration guide puts a basic integration at 4–8 weeks, a standard two-way integration at 8–16 weeks, and a complex enterprise integration at 16–52+ weeks. Where your project lands depends mostly on how many systems are involved and how much B2B-specific data has to move.
Step 4: Map the data flows before implementation
An integration plan should define exactly how data moves between systems. Do this before any code is written. For every data object, document:
- Source system
- Destination system
- Sync direction
- Sync frequency
- Trigger
- Field mapping
- Transformation rules
- Validation rules
- Failure behavior
- Retry behavior
- Operational owner
Here is a simplified example.
| Data object | Direction | Trigger | Frequency | Owner |
|---|---|---|---|---|
| Inventory | ERP or WMS to Shopify | Inventory adjustment | Near real time | Operations |
| Product data | ERP or PIM to Shopify | Product create or update | Scheduled or near real time | Merchandising |
| B2B price list | ERP to Shopify | Price update | Scheduled or near real time | Sales operations |
| Company records | ERP to Shopify | New customer or account update | Scheduled or near real time | Sales operations |
| Shopify order | Shopify to ERP | Order created | Event driven | Ecommerce operations |
| Fulfillment status | ERP or WMS to Shopify | Shipment confirmation | Event driven | Fulfillment |
| Payment status | ERP to Shopify | Invoice or payment update | Scheduled or event driven | Finance |
| Refund or cancellation | Shopify and ERP | Refund or cancellation event | Event driven | Customer service |
The exact workflow will change based on your business. What matters is that there is no ambiguity.
Step 5: Handle B2B-specific data correctly
B2B data is where standard ecommerce integrations often fail. A connector might synchronize customer records and orders correctly while mishandling the data that actually determines the buyer experience.
Before launch, validate support for:
- Companies
- Company locations
- Buyer permissions
- Customer accounts
- Catalog assignments
- Customer-specific pricing
- Quantity rules
- Volume pricing
- Payment terms
- Purchase-order numbers
- Draft orders
- Tax-exempt status
- Refunds and cancellations
- Fulfillment status
- Transaction and payout data
Shopify documents that external integrations can sync customer data, orders, inventory, product catalogs, and pricing information for Shopify B2B. But compatibility varies by app. Do not assume an existing ERP connector supports all B2B workflows.
Ask the provider directly whether its current version supports Shopify B2B APIs, companies, catalogs, customer accounts, pricing, and payment terms. Get the answer in writing before finalizing the architecture.
Step 6: Test edge cases before launch
Testing one successful order is not enough. You need to test the situations that create operational problems after launch. At a minimum, test:
Customer and account tests
- New company creation
- New buyer added to an existing company
- Buyer permissions changed
- Company assigned to a new catalog
- Customer-specific pricing update
- Tax-exempt buyer
- New payment terms assigned
Order tests
- Standard B2B order
- Order with a purchase-order number
- Order placed on net terms
- Order with a discount
- Large order with quantity rules
- Partial fulfillment
- Split shipment
- Order cancellation
- Refund
- Draft order
- Failed payment or payment-status update
Inventory tests
- Inventory decrease after an order
- Inventory increase after a return
- Stock update from the ERP
- Inventory across multiple locations
- Oversell prevention
- Backorder or preorder rules
Failure tests
- ERP is unavailable
- Shopify API request fails
- Duplicate order event
- A required field is missing
- A product SKU does not exist in the ERP
- A customer record fails validation
- A price list contains an invalid value
A good integration does not simply work when everything is normal. It fails safely, alerts the right people, and gives them a clear way to recover.
Step 7: Add monitoring, reconciliation, and ownership
An ERP integration is never fully finished. Records will fail. Credentials will expire. A team member will change a field without realizing it affects the sync. A new warehouse, marketplace, or product type will introduce a new edge case. Plan for it.
Set up alerts
Your team should receive alerts for:
- Failed order syncs
- Failed inventory updates
- Failed fulfillment updates
- Duplicate order attempts
- Catalog or price-list errors
- Authentication failures
- API rate-limit errors
- Data-validation failures
Alerts should route to a real owner, not an inbox nobody checks.
Add retry logic
Temporary errors happen. Your integration should retry transient failures automatically where it is safe to do so. But it should not endlessly retry a bad record without telling anyone. Use a dead-letter queue, error log, or exception report for records that require human review.
Reconcile data regularly
At least weekly, compare key records between systems:
- Order counts
- Inventory totals
- Fulfillment status
- Customer counts
- Company records
- Catalog assignments
- Payment status
- Refunds and cancellations
Reconciliation catches problems before they become customer complaints or accounting issues.
Common Shopify B2B ERP integration mistakes
Mistake 1: Starting with technology instead of workflows
Teams often begin by asking which connector to install. The better question is what must happen when a buyer places an order. Map the workflow first. Then choose technology that supports it.
Mistake 2: Letting two systems own pricing
Pricing is one of the most dangerous fields to manage poorly. If Shopify and the ERP can both overwrite the same price, you will eventually show the wrong amount to a customer. Assign one owner and define the publication process.
Mistake 3: Ignoring company and catalog support
A connector can work perfectly for DTC orders and still fail for B2B companies, catalogs, payment terms, or customer-specific pricing. Validate B2B compatibility before development starts.
Mistake 4: Treating inventory as a simple field
Inventory may be split across warehouses, reserved for existing orders, allocated to specific customers, or affected by backorder rules. Your integration needs to reflect how your operations team actually manages stock.
Mistake 5: Skipping failure planning
Every integration fails eventually. The question is whether your team sees the problem quickly and knows how to fix it. Build monitoring, retries, reconciliation, and ownership into the project from the start.
How Kirkby, White Consulting approaches Shopify B2B ERP integrations
Kirkby, White Consulting helps 7–9 figure DTC and B2B brands connect Shopify to the systems that keep their business running.
Best for: Manufacturers, distributors, wholesalers, and hybrid DTC/B2B brands with complex catalogs, customer-specific pricing, ERP or 3PL dependencies, and a need for senior technical leadership from strategy through launch.
Our Shopify B2B development work starts with your existing operating model. That means understanding how sales, operations, fulfillment, finance, and customer service use the current systems before proposing an app, connector, or custom build. Our process covers:
- System and workflow audit
- Product, customer, price, inventory, and order-data mapping
- ERP, PIM, OMS, WMS, and 3PL integration planning
- Shopify B2B company and catalog architecture
- Connector and middleware evaluation
- Custom API requirements where necessary
- Sandbox testing and launch preparation
- Monitoring, reconciliation, and post-launch support
If the ERP work is part of a move off Magento, our Magento to Shopify Plus migration guide covers the full migration, and Shopify Plus vs. Magento for mid-market B2B brands covers whether to make the move at all.
The goal is not to create more technology. The goal is to create a reliable order, inventory, pricing, and fulfillment flow that your team can operate without constant manual repair.
The bottom line
Connecting Shopify B2B to an ERP is not primarily an app-selection exercise. It is a process of deciding how your business handles products, customers, pricing, inventory, orders, fulfillment, and finance.
Start with the workflow. Assign a system of record. Use the simplest integration method that reliably supports the job. Then test the edge cases your customers and operations team will actually encounter.
If your business needs Shopify B2B to work with an ERP, PIM, WMS, 3PL, or custom pricing model, Kirkby, White Consulting offers a free Shopify store audit and a 30-minute scoping call. We will help you determine what should connect, where the data should live, and whether a direct connector, integration platform, or custom build is the right approach.
Frequently asked questions
Can Shopify B2B connect to an ERP?
Which ERP systems integrate with Shopify B2B?
What data should sync between Shopify B2B and an ERP?
Should Shopify or the ERP be the source of truth?
Should I use a Shopify ERP connector or a custom integration?
Sources
- Shopify B2B external integrations (Shopify Help Center)
- Ecommerce ERP integration guide (Shopify)
- How to integrate cloud applications (Shopify)
Spotted something wrong or out of date? Email hello@kirkbyconsulting.com with the details and we will correct it.