Shopify B2B organises business sales through company profiles, catalogues, payment terms and authorised buyers' orders. Available features depend on plan and configuration. B2B should no longer be described as exclusive to Shopify Plus.

The important question is fit with your selling model: negotiated distributor prices, frequent replenishment and multiple company locations can require different rules.

What it resolves and what it does not replace

A B2B channel can reduce emailed orders and help buyers consult catalogues and reorder. It does not itself replace sales work, credit control, invoicing or an ERP.

NeedElement to prepareBusiness question
Identify buyersCompanies, locations and contactsWho may buy for each destination?
Show offers and pricesCatalogues and quantity rulesAre terms negotiated by group or customer?
Collect paymentTerms and methodsImmediate payment, due dates or deposits?
Prepare ordersInventory, logistics and integrationWhich system confirms stock and delivery?

What changes by plan?

The official plan feature table includes B2B on Basic, Grow, Advanced and Plus. Differences include catalogues, direct company assignments, advanced payments and experience contextualisation.

Compare requirements with the current table rather than an old fee comparison. Company-specific prices and a few shared lists are different needs. A particular turnover alone does not justify Plus.

For B2B without Plus, see the standard-plan B2B guide. For spreadsheet-based processes, the wholesale orders guide focuses on that work.

Define rules before importing customers

  1. Classify companies and destinations: one legal entity can have several locations and buyers.
  2. Identify pricing groups and exceptions worth retaining.
  3. Define minimums, increments and units: single, box, bundle or pallet.
  4. Decide who approves accounts and payment terms.
  5. Document taxes, documents and obligations for adviser review.
  6. Assign ongoing data maintenance ownership.

Do not automatically transfer every historical exception. Some remain necessary; others are old workarounds complicating the new catalogue without value.

How the ERP should fit

Define authority over company records, credit risk, prices, availability and order status. If two systems edit the same field, establish priorities and conflict handling.

A Shopify order does not mean the ERP approved credit or reserved goods. Customer status must match actual operations.

  • Map company and location identifiers.
  • Check quantity pricing, taxes and rounding.
  • Design updates and retries without duplicate orders.
  • Provide alerts sales staff can use.

Blended store or separate experience

A blended store combines consumers and businesses; a separate experience isolates parts of operations. This affects catalogue, content, analysis and maintenance. Test navigation changes on B2B sign-in and what remains public.

Do not merely hide prices with CSS when product or condition access needs control. Verify permissions in system behaviour and integrations.

Test representative orders

Select real scenarios: new customers, multiple destinations, minimum orders, volume pricing, payment terms and partial returns. Add an operation needing human review and another that must be blocked.

Tests finish where the process ends: ERP recognition, correct fulfilment and coherent documentation. A confirmation screen does not prove the entire operation.

A launch the team can maintain

Pilot with a small company group and controlled catalogue. Explain access requests, reorders and incident reporting. Review remaining manual tasks, errors and handling times with sales and operations.

We can translate current rules into implementation scope through Shopify consulting. For an agreed migration, our Shopify migration service plans data, dependencies and launch.

Editorial review: the Migraciones.io team · 30 October 2026. Features, plans and availability are checked against the linked sources.