Shopify B2B in 2026: what every plan gets and what still requires Plus

The April 2026 change rewrote the Shopify B2B plan decision

On April 2, 2026, Shopify announced that merchants on Basic, Grow and Advanced could use key native B2B features in the admin at no additional cost. The official Shopify Changelog lists company profiles, payment terms, volume pricing, ACH payments in the U.S., vaulted credit cards and up to three active B2B catalogs assigned through Markets.

That is a material product change because older articles still describe native B2B as a Plus-only capability. In 2026, the correct first question is no longer 'Do you sell wholesale?' It is 'How complex is the wholesale operating model?'

This page owns that broad B2B architecture question. Shopify Plus Agency owns the commercial service intent, while narrower future guides can own B2B pricing or plan-comparison queries.

What Basic, Grow and Advanced can do natively

Shopify's April 2026 announcement gives non-Plus merchants a meaningful B2B baseline:

• Up to 3 active B2B catalogs assigned through Markets.
• Company profiles for business customers.
• Payment terms for wholesale purchasing.
• Volume pricing.
• ACH payments in the U.S. where supported.
• Vaulted credit cards.

For a merchant with a small wholesale program, a handful of customer segments and straightforward pricing, this can remove the need to upgrade to Plus purely to get native B2B records and terms.

What still remains exclusive to Shopify Plus

Shopify's same announcement keeps several capabilities exclusive to Plus: unlimited catalogs for customer-specific pricing, direct catalog assignment to companies and company locations, partial payments, and deposits.

Those differences look small in a feature table but matter operationally. Three catalogs can be enough for wholesale tiers such as Standard, Distributor and VIP. It is not enough when each account, region or contract needs its own price architecture.

Partial payments and deposits also change order and finance workflows. If B2B sales teams routinely negotiate terms or collect deposits, the payment model can become a stronger Plus trigger than the catalog count itself.

B2B + DTC is an architecture decision, not a theme toggle

A hybrid store has two commercial models sharing some combination of products, inventory, customers, content, fulfillment and finance. The cleanest Shopify design depends on where those models are truly shared and where they must diverge.

Start by mapping: product assortment, price ownership, customer/company identity, tax treatment, payment terms, minimums, checkout rules, inventory source, fulfillment route, returns and sales-rep workflow.

Then decide what belongs in Shopify natively, what belongs in Markets/catalogs/company records, and what must be synchronized with ERP, PIM, WMS, CRM or middleware. Building the storefront before that map is the common way B2B projects create duplicate data ownership.

Catalogs are the core of B2B pricing ownership

A B2B catalog is not just a discount list. It defines which products and prices apply to a business buying context. The 2026 plan limits therefore need to be compared against the merchant's real pricing model, not the number of wholesale customers.

Ask how many genuinely distinct price books exist today, who owns them, how often they change, whether they vary by company/location/market, and whether pricing is mastered in Shopify or an external ERP/PIM.

If an external system is the source of truth, the integration needs deterministic identifiers, update rules, reconciliation and failure handling. Otherwise catalog automation can overwrite negotiated prices or leave stale terms in Shopify.

Payment terms are only useful when operations can fulfill them

Native payment terms solve the storefront/account side of wholesale credit, but the business still needs finance ownership: who approves terms, what happens when an account is overdue, how ERP receivables reconcile with Shopify orders, and which changes sales reps are allowed to make.

The same principle applies to volume pricing, deposits and partial payments. A feature is not an architecture until the downstream order, accounting and customer-service workflows agree with it.

For merchants moving from wholesale apps or manual draft-order workflows, document the old exceptions before replacing them. The hidden exception usually creates more migration risk than the happy path.

ERP, PIM, WMS and CRM often decide whether B2B stays simple

B2B commerce creates more master-data questions than DTC: company identity, locations, credit terms, price books, purchase-order references, inventory allocation, sales reps and account-specific rules.

A good integration contract names the owner of every field and what happens when systems disagree. For example: ERP owns credit terms, PIM owns product enrichment, WMS owns available-to-promise inventory, Shopify owns checkout/session state. The exact split varies, but ambiguity should not.

If your B2B project depends on multiple operational systems, review Shopify integration services separately from the storefront build. Integration failure modes need their own acceptance criteria.

A 2026 framework for choosing the Shopify plan

Stay on Basic/Grow/Advanced when three active catalogs are enough, company profiles and payment terms cover the buying model, and the business does not need Plus-only assignment or payment capabilities.

Model Plus when catalog count or customer-specific pricing exceeds the non-Plus boundary, direct assignment to companies/locations matters, deposits or partial payments are required, or the broader business also needs Plus capabilities outside B2B.

Do not upgrade because an implementation partner still uses the pre-April-2026 feature matrix. And do not stay on a lower plan if the operational workarounds cost more than the platform difference. The Shopify Plus pricing guide owns the cost side of that decision.

B2B implementation checklist before development starts

• Define company and location identity.
• Inventory every current price list/catalog and its owner.
• Define payment terms, credit approval, deposits and partial-payment requirements.
• Map DTC vs B2B product, content and checkout differences.
• Decide sources of truth for products, inventory, customers, pricing and orders.
• Document tax, shipping, minimum-order and fulfillment exceptions.
• Decide whether sales reps need assisted-order workflows.
• Define migration and reconciliation rules for existing wholesale customers.
• Add measurable acceptance criteria before rollout.

That list determines plan and architecture more reliably than starting with a theme or a wholesale app shortlist.