Shopify’s B2B features — introduced in 2022 and significantly expanded since — have moved wholesale operations onto the Shopify platform for a growing number of merchants. For businesses running NetSuite as their ERP, this creates an integration architecture question that differs substantially from the D2C case.
What B2B on Shopify Adds to the Integration Problem
D2C Shopify integration with NetSuite is a solved problem in 2026. The record types are well-understood, the data flows are documented, and the patterns for order creation, inventory sync, and fulfillment are stable. B2B adds complexity across several dimensions:
- Customer-specific pricing — Shopify B2B supports price lists per customer/company. NetSuite has customer-specific pricing through price levels and customer pricing records. Keeping these in sync requires bidirectional price management, not just one-way sync.
- Net payment terms — Shopify B2B supports Net 30/60/90 payment terms. NetSuite tracks payment terms on customer records and invoices. The integration needs to create invoices rather than sales receipts, and map payment terms consistently.
- Company hierarchy — Shopify B2B has a Company > Location > Contact hierarchy. NetSuite has Customer > Sub-customer and Contact structures. The mapping is not 1:1 and requires deliberate design decisions before implementation.
- Draft orders and quotes — B2B buyers frequently negotiate. Shopify Draft Orders map to NetSuite Estimates/Quotes. The workflow from quote to order to invoice to payment needs to be mapped across both systems.
The Credit Limit Problem
NetSuite enforces credit limits on customers. Shopify B2B has a credit limit feature but it is managed independently. Without integration, a B2B buyer can exceed their NetSuite credit limit by placing orders through Shopify that have not yet been reflected in their NetSuite balance.
Real-time credit checking adds latency to the checkout process. Exception-based review adds operational overhead. Which is appropriate depends on order volume, average order value, and the cost of processing an order that ultimately cannot be fulfilled due to credit issues.
Starting Point: Scope the Data Model First
The mistake in B2B integration projects is starting with the technical implementation before resolving the data model questions. How does a Shopify Company map to a NetSuite Customer? What happens when a buyer has multiple locations with different pricing? How are returns and credits handled across both systems?
These questions take days to answer correctly and weeks to fix if answered wrong after implementation has started. A structured data model design session — mapping every Shopify B2B entity to its NetSuite equivalent, documenting the mapping decisions and the edge cases — is the highest-leverage activity in the first week of a B2B integration project.