Moving a WooCommerce wholesale store to Shopify B2B.

What changed in April 2026

Shopify's changelog entry of 2 April 2026 moved the core of B2B out of Plus. Standard plans now get "up to 3 active B2B catalogs (assigned via Markets), company profiles, payment terms, volume pricing, ACH payments (U.S. only), and vaulted credit cards", while "unlimited catalogs for customer-specific pricing, direct catalog assignment to companies and locations, partial payments, and deposits remain exclusive to Plus".¹

From Shopify's "B2B features by plan" page.² The three-catalog limit is the number to test your pricing structure against before choosing a plan.

How the two models map

Both WooCommerce plugins attach wholesale behaviour to a user: B2BKing puts users into customer groups and layers dynamic rules on top; Wholesale Suite gives users a wholesale role and stores role prices on each product.⁸⁹ Shopify attaches it to a company: a company has locations, each location has customers, payment terms and catalogs, and the catalog carries the prices.⁷¹¹

Prices, tiers and the 3-catalog limit

A Shopify catalog does three things: it decides which products a customer can see, it sets their prices, and it holds quantity rules and volume pricing.⁴⁵ Prices are set either as an overall percentage increase or decrease on the whole catalog, or as fixed prices for a product or a specific variant; fixed prices override the percentage.⁴ Once a product has volume pricing, its price is fixed and the overall adjustment no longer applies to it.⁵ Pricing, publishing and quantity rules can be exported to CSV and imported back, which is how a migration loads them.⁴

The constraint is the count. Standard plans allow three active catalogs across all B2B markets, and those catalogs are assigned through markets rather than to a specific company.² That maps cleanly onto "three wholesale tiers", which is the common Wholesale Suite setup. It does not map onto "a different price list for each of 40 accounts", which is what B2BKing's per-user dynamic rules make easy.

When several catalogs apply to one customer, Shopify shows the lowest price, and a catalog assigned directly to a company location wins over a market catalog as the more specific one.⁴¹¹ Volume pricing and quantity rules apply per variant: a customer cannot combine five grey hats and five blue hats to reach an increment of ten.⁵ B2BKing and Wholesale Suite count quantity at the product level by default, so tiers that relied on mixing variants need to be rethought or moved to a product-level bundle.

Where the data lives

Wholesale Suite

Wholesale prices are product meta. The base price for a role sits in wholesale_customer_wholesale_price (the role slug is part of the key), an alternative percentage discount in wholesale_customer_wholesale_percentage_discount, and quantity tiers in two keys, wwpp_post_meta_enable_quantity_discount_rule set to yes and wwpp_post_meta_quantity_discount_rule_mapping, which holds the brackets and prices per role as a serialised array.⁹ The plugin's own documentation exports all of this with WooCommerce's product CSV exporter by ticking "Export custom meta", and imports it back the same way.⁹ That export is the migration source: one row per product, one column per role price.

B2BKing

B2BKing keeps groups and rules in its own structures and offers bulk CSV import and export for pricing and orders.⁸ A user's group is set when they register with a given registration role, or when an administrator approves them and picks the group.⁸ Rules are the harder export, because there are seventeen kinds, from discounts and fixed prices to hidden prices, required multiples, tax exemption, BOGO and payment-method surcharges, each targeting users, groups, products or categories with quantity or value conditions.⁸ Export the rules table and classify every rule into one of four buckets: catalog price, quantity rule or volume break, payment term, or "no Shopify field".

YITH Request a Quote and other quote plugins

Open quotes are a workflow, not a data set. Export them for reference, close what can be closed before cutover, and recreate the live ones as Shopify draft orders, which can be sent to the customer for payment with the company's terms applied.¹¹

Companies, locations and logins

• Structure. A company can have up to 10,000 locations and 10,000 customers, and a location up to 50 customers.⁷ A WooCommerce wholesale user usually becomes one company with one location and one customer; B2BKing subaccounts become additional customers on the same location, with an "ordering only" or "location admin" role.¹⁰
• Bulk creation. Shopify's help centre points to Matrixify for importing companies in bulk; its sheet carries the columns a migration needs, including Location: Checkout Payment Terms, Location: Catalogs, Location: Tax ID and Customer: Location Role.⁷¹⁰ The Admin API does the same for a scripted migration.
• One customer, one company. A customer record can belong to only one company.¹⁰ A buyer who purchases for two businesses on WooCommerce needs two Shopify customer records with different emails.
• Logins. B2B needs Shopify's current customer accounts; legacy accounts cannot place B2B orders.³ Customers sign in with an emailed code, so no passwords need to move; see the customer accounts guide.
• VAT. Validated VAT numbers from B2BKing's VIES check go into the location's tax ID, and exemptions into the location's tax settings.⁷
• Approval flows. Registration-then-approval becomes company account requests: a prospect requests an account, you approve and assign catalogs and terms.¹¹

Terms, purchase orders and quotes

Payment terms are set per company location and bulk-edited across companies: no terms (due immediately), net 7, 15, 30, 45, 60 or 90 days, due on fulfillment, or a fixed date.⁶ Customers can pay early from their account with a "Pay now" option, and cards can be vaulted at the location.⁶¹¹ Purchase order numbers are captured at checkout on every plan.¹¹ Deposits and partial payments are Plus-only.⁶

Invoice-style gateways on WooCommerce, where the order is placed and paid later by bank transfer, map to a manual payment method plus net terms; the payment is recorded in the admin when it arrives.⁶

What does not transfer

• Per-user pricing beyond three tiers on a standard plan. Either consolidate, or plan for Plus.²
• Rule types with no Shopify field: BOGO, payment-method discounts and surcharges, payment-method minimums, forced currencies, add-tax and fee rules.⁸ Some can be rebuilt with Shopify Functions or an app; the honest default is to drop them and tell the customer.
• Accelerated checkouts. B2B checkout does not offer Shop Pay, Apple Pay, Google Pay or Amazon Pay.³
• Subscriptions on B2B orders are not compatible, and gift cards and local pickup need Shopify support to enable.³
• Orders above 500 line items fail; large blanket orders need splitting.³
• Checkout customisations made in checkout.liquid are unsupported with B2B.³
• Order history migrates as ordinary orders attached to the customer; it does not recreate open invoices with terms.

Step by step

1. Inventory the tiers. Export roles or groups, the products with role prices, and every rule. Count distinct price structures, not rules.
2. Decide the plan. Three structures or fewer, and no true per-customer pricing: a standard plan. More than that: Plus, or a consolidation the customer agrees to in writing.
3. Migrate products first, then build the catalogs and import prices, publishing and quantity rules by CSV.⁴
4. Create companies with locations, customers, terms, tax IDs and catalog assignments, in bulk.⁷¹⁰
5. Rebuild the exceptions as fixed catalog prices, draft orders or Functions, and list what was dropped.
6. Test as a buyer: sign in with a migrated email, check prices per catalog, quantity rules, terms at checkout and the PO field.
7. Tell the buyers: the login changes to an emailed code, the checkout looks different, and terms are unchanged.

Frequently asked questions