B2B Commerce
Self-service wholesale on the same store as your consumer business.
B2B Commerce treats wholesale buyers as first-class objects on the same Shopify store as your consumer business — not a bolted-on silo. A business buyer logs in as part of a company, sees the assortment and pricing negotiated for their account, reorders in a few clicks, and pays on agreed terms. Underneath, Shopify models companies, company locations, account-specific catalogs, negotiated price lists, and payment terms natively, so the org chart of a real buyer maps directly onto the platform and wholesale runs off the same inventory and source of truth as retail.
The honest framing is that Shopify B2B is largely native. The majority of a build is configuring primitives the platform already ships — company accounts, per-location catalogs and price lists, purchase-order and payment-terms checkout — rather than bespoke plumbing. Custom development is reserved for where the platform genuinely runs out: multi-tier approval chains beyond draft-order review, deep EDI mappings past the native SPS Commerce and Crstl path, and complex split-order logic across delivery locations. Those become apps or middleware we own, and the back-office sync into OMS, ERP, and CRM follows the same integration discipline as the rest of our work.
The difficulty is rarely the platform; it is the commercial logic and correctness across systems. Overlapping tiers, account exceptions, and contract prices have to resolve to one deterministic number at checkout, and B2B order and invoice sync has to hold under failure, not just on the happy path. We frame faster reordering, fewer manual touches, and a unified back office as the expected outcomes of doing this well — not as results we have already measured for you.
Definition
B2B Commerce puts wholesale buyers on the same Shopify store as your consumer business — not a bolted-on silo. Each company logs in to see their own assortment at their negotiated price, reorders in a few clicks, and pays on agreed terms, while inventory, orders, and invoices flow into the same back-office systems as the rest of the business.
How we deliver it
- 01
Map the commercial rules
Price lists, tier breaks, payment terms, approval flows, and which system owns the truth for pricing and inventory — these are agreed in writing before any code is written. B2B programmes stall on undefined rules far more often than on code.
- 02
Configure the native B2B layer
Shopify models companies, company locations, account-specific catalogs, negotiated price lists, payment terms, and PO checkout natively on the same data model as the consumer store. We configure that layer first — for most wholesale requirements, the platform already ships the primitive.
- 03
Build where the platform runs out
Multi-tier approval chains, deep EDI mappings, and complex split-order logic go beyond native behaviour and are built as custom Shopify apps or middleware we own. Back-office sync — orders, invoices, and account data into OMS, ERP, and CRM — follows the same event-driven discipline as all integration work.
- 04
Sustain past launch
Every custom app and middleware layer is a maintenance surface. Ongoing cover moves into Hypercare so the commercial logic stays correct and the back-office connections hold under failure, not just on the happy path.
Questions, answered
Do we need a separate wholesale site?
No. B2B is a native context of the same Shopify store: companies, company locations, account-specific catalogs and pricing, and payment terms — all on the same data model and inventory as your consumer business. A dedicated B2B storefront on its own domain is an option on Shopify Plus, not a requirement.
Can buyers pay on Net 30 or by purchase order?
Yes. Payment terms (Net 30, 60, 90) and purchase-order checkout are native, configured per company location. Deposits and partial payments are a Shopify Plus capability.
We need orders approved before they are placed — can you support that?
Light approval is native: checkout can route to a draft order for merchant review. Multi-tier approval chains, conditional routing, or mirroring your ERP's authorisation hierarchy go beyond native and are scoped as a custom build — we size that explicitly before committing to it.
Do you support EDI with our trading partners?
Partly natively, as of Winter '26: purchase orders from SPS Commerce and Crstl can sync into Shopify as draft orders for review and fulfilment in admin. Other trading networks, or deeper mappings, are handled as a proven connector or custom middleware we own — decided per partner.
See how this applies to your store.
Solutions are assembled from the same disciplines, under one senior team. The fastest way to scope yours is a senior-led diagnosis that names your real constraint before any code.