Shopify B2B on Basic vs Grow vs Advanced vs Plus: When Procurement Software Still Matters

Start with the current Shopify B2B baseline, not an old Plus assumption

Shopify's current feature-by-plan table puts a surprisingly broad B2B foundation on Basic, Grow, Advanced, and Plus. All four list companies and company locations, Ordering only and Location admin permissions, quantity rules, quantity price breaks, net payment terms, payment reminders, vaulted credit cards, draft-order invoicing, checkout-to-draft, easy reorders, PO numbers, sales-staff permissions, Quick order list, and Shopify Flow using B2B objects. That is enough to support many real wholesale storefronts without inventing a separate system for every business buyer.

This matters because plan selection should follow the exact missing feature. A distributor that needs company accounts, case-pack rules, Net 30, purchase-order numbers, a fast reorder path, and seller review of submitted orders may already have the native building blocks on a non-Plus plan. Upgrading simply because the store is 'B2B' would confuse business model with feature requirement.

There is still an important setup condition. Shopify says stores using B2B catalog features on Basic, Grow, or Advanced must use the new Shopify Markets. Confirm that architecture before promising a migration path to buyers, especially if an older store has accumulated custom market or catalog logic.

The biggest catalog difference is three market catalogs versus unlimited and direct company assignment

On Basic, Grow, and Advanced, Shopify currently allows up to three active catalogs across all B2B markets. That is a shared ceiling, not three catalogs per market. Plus raises the B2B market-catalog count to unlimited and adds direct catalog assignment to a specific company or company location. Direct company catalogs are not listed for Basic, Grow, or Advanced.

Turn that into an account-design question. A wholesaler with one domestic trade catalog and one export catalog may fit comfortably below the non-Plus ceiling. A manufacturer with hundreds of negotiated customer-specific price books has a very different requirement. The second merchant should evaluate Plus because the missing capability is customer-level native catalog assignment, not because its buyers happen to use purchase orders.

Do not use procurement software to pretend a platform catalog limitation disappeared. B2B Procurement OS is built on Shopify orders, draft orders, companies and billing according to its current listing. Its procurement controls can sit around the buying process, but this article does not claim the app unlocks Shopify Plus-only direct catalog assignment or unlimited B2B market catalogs.

Advanced and Plus add contextual experiences, while Plus owns the advanced native payment layer

Shopify's current plan table lists contextual checkout and contextual storefront experiences through Markets on Advanced and Plus, but not Basic or Grow. If your B2B architecture needs market-specific storefront or checkout context, that difference can justify looking above the entry plans even when your catalog count is modest.

The payment split is sharper. Net terms are listed across all four plans, but deposit requirements for companies and draft orders, partial payments, and payment requests per fulfillment are Plus-only in Shopify's current documentation. Shopify's payment-terms guide also makes the distinction concrete: a percentage deposit can be required up front while the remaining balance follows payment terms, and the deposit requirement itself is a Plus feature.

Keep those payment capabilities separate from credit policy. Net 30 tells an accepted buyer when payment is due. A deposit reduces how much is left unpaid. A credit limit constrains the seller's exposure. They can work together, but one does not replace another. If the business specifically needs native deposits or partial payments, that is a Shopify plan decision before it is an app decision.

B2B Procurement OS solves procurement controls that are orthogonal to the Shopify plan ladder

The app's current Shopify App Store listing centers on buyer self-service and internal procurement control. It advertises multi-level approval workflows with conditional rules based on order amount, using Purchasing, Manager, and CFO as example stages. It also advertises per-company credit limits and net terms that automatically block over-limit or overdue orders. Those controls answer who may authorize a purchase and how much open exposure the seller will allow.

The same listing covers repeat-order and exception work: buyers can reorder from saved lists or CSV, request volume quotes priced from merchant data, and edit unfulfilled orders for quantity, shipping address, PO number, or cancellation. That is different from Shopify's native plan segmentation. A merchant can have the right Shopify plan and still lack the buyer-side approval chain its enterprise customers expect.

The boundary matters. B2B Procurement OS is not being presented as a substitute for every Plus-only feature. It does not become direct company catalog assignment merely because it uses company data, and this guide does not claim it supplies Shopify's native deposit or partial-payment capabilities. Treat it as a procurement layer when its verified workflow features match the gap you actually have.

Scenario 1: a straightforward wholesaler may already have enough on Basic or Grow

Imagine a regional packaging wholesaler with two B2B markets, a standard trade catalog, case-pack quantity rules, published volume breaks, Net 30 for approved accounts, and frequent reorders. Shopify's current matrix places those core building blocks across Basic, Grow, Advanced, and Plus. If buyers can duplicate previous orders or use Quick order list and the merchant only needs simple seller review, the native stack may already cover the operating model.

Adding procurement software here should be evidence-led. If larger customers begin asking for saved purchasing lists, CSV-based replenishment, amount-based approval chains, or account credit enforcement, B2B Procurement OS has a clear additional job. If those requests never appear, an app would be extra administration rather than automatic sophistication.

The decision principle is economical even without inventing savings: pay for the control layer only when the control exists in the real process. Do not turn a clean wholesale flow into a miniature ERP because an enterprise checklist looked impressive.

Scenario 2: an Advanced store can need procurement depth without needing every Plus feature

Consider a commercial equipment seller using Advanced because contextual Markets experiences matter, while its catalog model still fits inside three active B2B market catalogs. The company's enterprise buyers, however, prepare large baskets that must pass Purchasing, management, and finance before submission. They also want reusable lists and the merchant wants account-level credit blocks.

That merchant has two independent decisions. Advanced may remain the correct Shopify platform tier for its storefront and catalog architecture. A procurement app may still be justified because buyer authorization and credit exposure are not the same problem as contextual storefronts. B2B Procurement OS fits this specific gap through its verified multi-level approvals, saved-list or CSV reorders, quotes, and credit controls.

Before adopting it, use Shopify's compatibility check for the actual store and validate the exact workflow you intend to run. The App Store listing confirms the advertised feature set and current plans; it does not give us permission to claim every Shopify configuration, external ERP file, or custom approval policy will work without verification.

Scenario 3: Plus and a procurement app can be complementary rather than substitutes

A larger manufacturer may genuinely need Plus for unlimited B2B market catalogs, direct company catalogs, deposits, partial payments, or payment requests per fulfillment. Those are platform capabilities. The same manufacturer may also sell to customer organizations whose buyers need multi-level internal approval and whose accounts require explicit credit limits before an order should proceed.

In that case, the architecture is additive. Plus handles the Shopify-native catalog or payment requirement; B2B Procurement OS handles a buyer-procurement requirement when its documented controls match the policy. Trying to force one layer to impersonate the other usually creates brittle workarounds and confusing ownership.

Write the responsibilities down: Shopify plan features control storefront, catalog, checkout, payment and company-account capabilities; procurement policy controls buyer authorization, repeat-purchase process, quote exceptions and seller credit exposure. Once the boundary is visible, software decisions become much easier to defend.

Use a requirement matrix before changing either your Shopify plan or app stack

Make one row for every real requirement, then assign it to a layer. Examples include direct company-specific catalog, more than three B2B market catalogs, deposit at checkout, partial payment, contextual storefront, buyer-side approval by order amount, saved-list reorder, CSV reorder, volume quote, unfulfilled-order correction, per-company credit ceiling, and overdue-order hold. Mark whether Shopify already provides the requirement on your current plan, whether a higher plan is required, or whether the requirement is a procurement workflow rather than a platform feature.

This prevents two expensive category errors. The first is upgrading Shopify to solve a buyer-approval problem the plan ladder does not describe. The second is installing an app and assuming it grants a Plus-only native feature that its listing never promised. Both happen when teams compare product names instead of capabilities.

For B2B Procurement OS specifically, the official listing currently shows Starter at $79 per month, Growth at $199, and Enterprise at $499, with a 14-day free trial on each listed plan. B2B Procurement OS is available in English. Evaluate that subscription against the verified procurement work you need, not against the abstract idea that every B2B store should have more software.

• Basic/Grow/Advanced: up to three active B2B market catalogs across all B2B markets.
• Plus: unlimited B2B market catalogs and direct company/company-location catalog assignment.
• Advanced/Plus: contextual storefront and checkout experiences through Shopify Markets.
• Plus: native B2B deposits, partial payments, and payment requests per fulfillment.
• B2B Procurement OS: evaluate for amount-based multi-level approvals, credit limits, saved-list/CSV reorders, quotes, and controlled unfulfilled-order editing.

Pilot the workflow at the boundary where your current setup actually breaks

Do not pilot with a fictional perfect order. Choose one company that exposes the reason you are considering a change. If catalog personalization is the issue, test whether your required assignment model fits the plan. If deposits are the issue, validate the Plus payment workflow. If procurement is the issue, use an account with at least two approvers, a repeat order, a credit-sensitive case, and one quote or order-change exception.

Document where the order starts, who can edit it, who must approve it, which Shopify company location and catalog apply, when payment becomes due, what happens when credit policy blocks the purchase, and who can recover a rejected or incorrect order. A successful pilot should make ownership clearer, not merely add more screens.

Then keep the neighboring ShopRadar workflows close. The order-approval guide separates Shopify permissions, merchant draft review, and buyer-side approval; the net-terms-versus-credit-limits guide separates payment timing from exposure; and the repeat-order guide separates native reorders from saved-list and CSV procurement. Those are the operational details behind the plan-level decision made here.

Apps mentioned in this guide

Frequently asked

Do I need Shopify Plus to use Shopify B2B?

Not according to Shopify's current September 2026 documentation. Shopify B2B is available on Basic, Grow, Advanced, and Shopify Plus, but the feature set differs by plan.

What are the main B2B limits below Shopify Plus?

Shopify currently lists up to three active B2B market catalogs across all B2B markets on Basic, Grow, and Advanced, with no direct company catalog assignment. Plus offers unlimited B2B market catalogs and direct catalog assignment to companies or company locations.

Which native B2B payment features require Shopify Plus?

Shopify's current plan table lists company and draft-order deposit requirements, partial payments, and payment requests per fulfillment as Plus-only. Net payment terms are listed across Basic, Grow, Advanced, and Plus.

Does B2B Procurement OS replace Shopify Plus?

No universal replacement claim is appropriate. B2B Procurement OS adds documented procurement workflows such as multi-level approvals, company credit controls, saved-list or CSV reorders, quote requests, and unfulfilled-order editing. It should not be treated as a way to unlock Shopify Plus-only native catalog or payment features.

Is B2B Procurement OS available in English?

Yes. B2B Procurement OS is available in English. ShopRadar uses the authentic b2b-procurement-os App Store slug and requests the English listing with locale=en.