B2B on Shopify Plus: Native Features, Real Limits & When It Replaces Your ERP-Era Stack

The Mental Model: B2B on Shopify Is Customer-Graph Commerce

The single most useful frame for B2B on Shopify — on Basic, Grow, Advanced or Shopify Plus — is that it is not a separate store, a separate login portal, or a separate codebase. It is the same storefront, the same admin and the same checkout — re-interpreted through a customer graph. Every B2B object hangs off a company: companies have locations, locations have buyers, and prices, catalogs, payment terms and tax rules are bound to that triple rather than to individual customer emails.

The three-level customer graph (Company → Location → Buyer) is the schema every B2B feature on Shopify binds to. Pricing, catalogs, terms, tax and shipping all attach at the company-and-location pair — never at the individual buyer.

Once that model clicks, the rest of the feature set stops looking arbitrary. Catalogs and price lists scope what a company sees and pays — our Shopify wholesale pricing guide covers the models and the math for setting those price lists without eating the margin. Net terms and PO-on-checkout are how a company-level attribute changes the checkout. Draft orders are how a sales rep operates against the same graph.

If the question you keep asking is "where do I create the B2B store?", you are still in the old mental model — there is no separate B2B store to create. There is one storefront that behaves differently depending on which company is logged in.

This article assumes that frame and focuses on what it means in practice: what B2B on Shopify covers natively in 2026, which parts of it actually require Plus since the April 2026 plan change, where the feature set stops, what Shopify Functions unlock, when you should still pick a separate expansion store, and where it lands on cost against Adobe Commerce and BigCommerce B2B Edition. If you are still deciding whether B2B is even the right question for your business, the B2B vs B2C explainer covers that step.

Do You Need Plus for B2B? The 2026 Plan Boundary

Start with the one screen that used to be the whole article: do you actually need Plus, or does the native B2B already on your plan cover it? Shopify's own wording is unambiguous — "B2B features are included at no extra cost on the Basic, Grow, Advanced, and Shopify Plus plans" — so the table below is the real decision, and everything after it is implementation detail.

Two caveats the two-column split hides. Starter is not on Shopify's list of B2B plans — the enumeration is Basic, Grow, Advanced and Plus. And not every B2B gate is a Plus gate — Shopify's B2B plan-features documentation puts contextual checkout and contextual storefront with Shopify Markets on the Advanced and Plus plans, so the middle tier matters too.

With that settled, two screens remain for anyone weighing the upgrade: does your vertical match the pattern, and does your workflow hit the Plus line above? If both come back yes, the rest of the article tells you what to build.

Industry fit: where B2B on Shopify is a clear yes, and where it isn't

The pattern is straightforward: B2B on Shopify is the right answer when the buyer-rep workflow is the bottleneck, and a harder sell when the bottleneck is contract complexity or procurement-platform plumbing. Use the table as a fit screen before the platform demo, not after.

Four buyer profiles: match your situation to the right setup

Match your situation to one of the four profiles below. Note that the axis is catalog and pricing complexity, not revenue — a $20M distributor selling from one shared price list needs less platform than a $3M brand running per-customer contracts.

If native B2B on Basic, Grow or Advanced does not stretch far enough — per-company prices on the same checkout as retail, for instance — the B2B on Shopify wholesale guide covers the app and draft-order patterns that fill that gap below Plus (Wholesale Gorilla, B2B/Wholesale Solution, SparkLayer).

Business Outcomes: What KPIs Move After Migration

For any P&L owner, the platform debate is downstream of one question: what changes in revenue and team-hours after migration? The pattern across mid-market Plus B2B implementations is consistent enough to put numbers around — with the caveat that the magnitude depends on your starting point.

These ranges come from partner-published case studies and the consistent pattern in Plus B2B implementations the editorial team has reviewed. Treat them as planning anchors, not commitments — a paper-order shop sees larger lifts than a team already digitised on Magento.

3-Year TCO: Plus B2B vs Adobe Commerce vs BigCommerce B2B Edition

The honest 3-year TCO comparison below uses a stylised mid-market scenario: $5M B2B GMV, 200–500 active companies, native quoting, one approvals app, no EDI, no NetSuite middleware. Real merchants vary; the structure of the comparison does not. Three platforms are compared: Plus B2B, Adobe Commerce and BigCommerce B2B Edition.

Estimates assume a mid-complexity B2B implementation at $5M GMV with no EDI and no ERP middleware. Shopify Plus is $2,500/month on a 1-year term and $2,300/month on a 3-year term, moving to a variable revenue-linked fee at higher GMV — the 36-month column above spans both terms, from $2,300 × 36 (~$83K) on a 3-year commitment to $2,500 × 36 ($90K) on a 1-year one. Adobe Commerce license fees are indicative and negotiated per merchant. BigCommerce B2B Edition pricing varies by tier and is quoted per merchant; the figures above are partner-published mid-market ranges. Card processing is excluded from all columns since it is workload-dependent and similar across platforms.

Two takeaways. First, Plus B2B and BigCommerce B2B Edition land in a similar TCO band; the choice between them is feature fit and ecosystem, not headline cost. Second, Adobe Commerce sits materially higher across all six line items at this scale — most of the gap is implementation, ongoing maintenance and hosting rather than license fee. For deeper Plus-specific economics, the Shopify pricing breakdown walks through the platform-fee structure across all plans.

Already on BigCommerce and leaning toward the switch? The BigCommerce to Shopify migration guide covers the move itself — data mapping, 301 redirects and real costs.

What Every Plan Gets vs What Plus Adds

The nine capabilities below are what B2B on Shopify actually ships. Since April 2, 2026 six of them are included in full on Basic, Grow, Advanced and Plus alike; the Plus line cuts through only three — catalogs, the deposit-and-partial-payment side of payments, and checkout extensions. The plan line noted on each card shows exactly where, and it is narrower than most re-platforming budgets assume.

Two things to read between the lines. First, the baseline in this list is included at no extra cost on Basic, Grow, Advanced and Plus — no separate B2B subscription, no per-buyer fee, no add-on module; only the Plus lines noted on the cards above cost more. Note that Starter is not on that list, and that B2B requires the new customer accounts.

Second, the set is intentionally horizontal: it covers the workflow that 80% of B2B merchants need 100% of the time, and leaves the vertical-specific 20% (complex contract pricing, EDI, multi-level approvals) to Functions, apps or integrators. The next two sections cover exactly where that boundary sits.

The Legacy-Stack Replacement Map

The honest replacement map below maps ten common B2B capabilities against native B2B on Shopify, Adobe Commerce and mid-market NetSuite commerce. The aim is to give a re-platforming team a starting checklist, not to declare a winner — each row is a real decision that surfaces during requirements workshops. For how Plus, Hydrogen, B2B and Markets bundle at this scale, see our Shopify Enterprise overview.

"Yes" means available natively without third-party modules. "App or custom" means the platform itself does not ship the capability and the team builds it on extensibility primitives.

The pattern is clear. Native B2B on Shopify covers the catalog, pricing, terms and quoting workflow at the same depth as Adobe Commerce or NetSuite for the mid-market — and trails them specifically on enterprise procurement workflows (approvals, EDI, contract pricing with effective dates, hard credit limits). Three of those gaps close with Shopify Functions; two close with apps or middleware. The next section is the honest list of what does not close at all without help.

The Five Things Plus B2B Still Can't Do Without Help

The cleanest way to evaluate Plus B2B is to take the gaps seriously rather than around them. The five below are the ones merchants most often discover after the contract is signed, not before. For each, a typical fix exists — but the fix is usually an additional app, a Function, or a middleware integration with its own implementation cost.

Which shape that middleware takes — a certified connector app, an iPaaS platform, or a custom Admin API build — is a separate decision with its own year-one price tag, and our guide to connecting an ERP to Shopify works through it; this page stays with the B2B feature set the integration plugs into.

Shopify Functions: The Unlock Most Teams Underestimate

Most evaluations of B2B on Shopify underweight Shopify Functions because they sound like a developer feature. They aren't — they are how any merchant changes pricing, delivery, payment and discount behaviour at runtime without owning a checkout codebase. On Basic, Grow and Advanced that means installing a public App Store app that ships a Function; on Plus it also means writing your own. For B2B specifically, four Function types do most of the work.

Functions matter for the build-vs-buy decision because they execute server-side on Shopify's infrastructure. The logic stays consistent across storefront, headless and POS, and never adds page-load latency.

A merchant that would have needed a custom checkout to enforce buyer-specific rules on Adobe Commerce typically needs a single Function on Shopify — installed from the App Store on any plan, or written as a custom app if you are on Plus. That is the distance between "B2B on Shopify can't do X" and "it can do X with one Function" — small in code, large in TCO.

B2B + D2C: One Store or a Separate Expansion Store

You can run B2B and D2C on a single store with conditional rendering, or split them across two stores — the second typically using Plus expansion store capability. Neither store model is tied to a plan tier; what Plus changes is the price of the second store, because Plus includes 9 expansion stores while on Basic, Grow or Advanced a dedicated B2B store is a net-new paid subscription. The decision is operational rather than technical, and the six dimensions below are the ones that matter in practice.

Two practical defaults:

• Stay on a single store if your B2B catalog is mostly a subset of D2C SKUs and one team manages content — the operational saving compounds.
• Pay the expansion-store cost if your B2B UX needs to look like a procurement portal (no marketing imagery, dense PDP, fast reorder), if B2B and D2C teams are organisationally distinct, or if your D2C site cannot afford to leak B2B-only pages into Google's index.

Hybrid setups exist but tend to drift into either pure pattern within 18 months. Pick the destination, not the compromise.

The B2B Checkout Customizations That Actually Matter

Shopify's checkout takes customizations from Basic up — standard customizations on all pages, and app extensions on the Thank you and Order status pages. Advanced checkout customization is the Plus line: UI extensions on the information, shipping and payment steps, plus the Checkout Branding API. The four customizations below are the ones almost every B2B merchant ends up shipping, and the reason a "we'll just use the standard checkout" plan usually slips by a few weeks. For the full timeline of what changed and when, see the checkout extensibility deadlines guide.

• PO number capture as a required field. A simple text input, conditionally required for net-terms buyers, with the value piped to the order and into invoicing. Most ERP integrations need the PO surfaced before payment.
• B2B-only delivery instructions per location. Loading dock hours, gate codes, receiving contacts — captured at checkout and stored against the company location, then auto-filled on subsequent orders.
• Payment method gating for net-terms buyers. A payment customization Function hides card and Shop Pay for buyers with active net terms, leaving only "Invoice (Net 30)". Single source of truth at checkout, no support tickets about double-paid orders.
• Shipping rate calculation against company addresses. Freight quotes based on the company's registered shipping addresses, with carrier accounts that may differ between B2B and D2C. Native carrier-calculated shipping covers most cases; complex rates use a Function or a dedicated shipping app.

None of these are exotic, and none requires a custom checkout build. They are all built on the same checkout-extension primitives D2C merchants use — scoped to B2B with a single configuration flag. They do carry a plan cost, though: PO capture and per-location delivery instructions are UI extensions on the information and shipping steps, which means Plus, while payment-method gating rides a payment customization Function — a public App Store app on any plan, or your own custom app on Plus. Budget the plan, not just the build.

Migration Patterns That Actually Work

Re-platforming to B2B on Shopify has a well-documented happy path. The five phases below are what Plus Partners ship; the order matters and skipping any one of them is where projects drift past timeline.

The single phase teams most often under-invest in is the second — mapping the legacy customer graph. Shopify's two-level company → location model is simpler than the three-or-four-level hierarchies common in NetSuite, SAP or legacy CRMs. The collapse has to be a deliberate design decision before import, not a discovery during user acceptance testing.

Operational Reality: Sales Reps, Buyer Onboarding, Reporting & Enterprise Security

Most evaluations of B2B on Shopify stop at the feature checklist and the TCO table. The four operational dimensions below are what determines whether the platform delivers the savings the spreadsheet predicts — and where teams most often surprise themselves in month four.

Sales reps: draft orders, POS, and mobile order entry

For merchants where 30–80% of orders still come through a sales rep — typical for distribution, food service, beauty wholesale and industrial supply — the rep experience matters more than the buyer portal. Reps work across three surfaces:

• Admin draft-order builder. Full quotes with custom price overrides and PO numbers, sent as a checkout link the buyer pays through.
• Shopify POS on iPad (B2B mode). Pull up a company, see its catalog and prices, write the order in person at a trade show or on a route call.
• Shopify mobile app. Duplicate any company's prior order from the road — the cleanest fix for the single biggest source of order-entry errors.

Practical implication for the project plan: budget a real rep-onboarding workstream — typically 1–2 weeks of training plus a "shadow first 10 orders" period — not just a buyer-portal launch. Rep adoption is the variable that decides whether your reorder rate goes up or down in the first quarter post-launch.

Buyer onboarding: getting your companies to actually use the portal

The native B2B portal works, but adoption is not automatic — especially for buyers who have spent five years emailing orders to a rep. A working onboarding pattern has four moves:

1. Pre-load the company graph from your ERP before launch. Don't ask buyers to self-register.
2. Seed each company with 6–12 months of order history so first-time reorder is a one-click action.
3. Send a personalised email from the rep (not a generic blast) with a magic-link login.
4. Run a two-week "place orders for buyers while showing them the portal" period so reps demo the workflow on real orders.

Merchants who skip this play typically see 20–30% portal adoption at 90 days; those who run it cleanly land at 60–80%. Same platform, same buyers — different outcome driven entirely by onboarding discipline.

B2B reporting: what's native, what needs an export

Native in the admin: sales by company, sales by location, net-terms exposure, reorder rate by company. ShopifyQL queries split D2C and B2B by customer type — the underpinning for any "B2B revenue mix" board view.

Not native, almost always a finance-team workstream: AR aging by company (Shopify is not your accounting system), commission attribution by rep, and any forecast that crosses Shopify with your ERP-side pipeline. The standard fix is a daily export to your BI tool (Looker, Metabase, or a spreadsheet) — not heroic, but it has to be planned, not improvised in the first month-end close.

Enterprise security: SSO, audit, and compliance

For any merchant selling into enterprise accounts, IT will ask three questions before signing: SSO for buyers, audit logging, and compliance posture. Plus answers all three:

• Federated sign-in, for staff and for buyers. Organization-level SAML authentication covers your own users; buyers reach the B2B portal either with the default one-time email code or through your own OpenID Connect identity provider connected to customer accounts — both are Plus capabilities, and both remove the separate password enterprise IT asks about.
• Admin audit logs (org level). Capture staff actions across all stores — the artefact SOC 2 auditors and enterprise procurement reviews ask for.
• PCI compliance. Inherited from Shopify's hosted checkout, so the merchant's scope stays at PCI SAQ-A — materially smaller than a self-hosted Adobe Commerce footprint.

None of this is automatic at signup; each is a configuration line item in the implementation plan. But all three come from the platform rather than third-party add-ons — which is what shortens enterprise procurement cycles by weeks. Note the plan split: PCI SAQ-A scope is inherited on every plan, while staff SAML authentication, buyer OpenID Connect sign-in and org-level audit logs are all Plus capabilities.

The Bottom Line

The platform decision is the smaller half of the cost. The bigger half is the gap list — the workflows your team runs today that Plus does not cover natively, and how you intend to close them with Functions, apps, middleware or process change. Decide that list before signing, not after.

Frequently Asked Questions