Shopify B2B on a Custom Storefront: 2026 Feature Benchmark

Yes, Shopify B2B works with a custom storefront. Almost all of the wholesale logic — customer-specific price lists, net payment terms, PO number capture, deposits — runs inside Shopify's checkout and customer accounts, so it carries over untouched when your frontend is Framer or any other Storefront API client. The one part that does not come for free is catalog gating: your storefront has to ask for prices in the buyer's context and then refuse to show anything when it cannot.

That distinction matters more in 2026 than it did a year ago, because there is far more B2B to carry over. Shopify's B2B GMV grew 76% year over year in Q2 2026 while total GMV rose about 32%, and since April the foundational B2B feature set ships on Basic, Grow and Advanced rather than Plus alone.

What Shopify B2B Actually Is in 2026

Shopify B2B is a native wholesale layer inside the same store as your retail business: companies and company locations instead of individual customers, catalogs that override retail prices per buyer, and a checkout that accepts payment terms rather than a card every time.

Nothing about it is a separate storefront. A company location is just a customer record with a catalog attached, which is exactly why a headless frontend can participate — it only has to identify the buyer and ask Shopify for that buyer's prices.

Does Shopify B2B Work With a Custom Storefront?

It does, through one mechanism: buyer context. You pass a buyer object — a customerAccessToken plus a companyLocationId — into the @inContext directive on your product queries, and Shopify returns that company's prices instead of retail ones. The companyLocationId comes from the Customer Account API, so B2B requires Shopify's new customer accounts rather than legacy auth.

Three things then follow automatically on a contextualized query: variant price reflects the company's catalog, quantityRule returns the minimum, maximum and increment, and quantityPriceBreaks returns the volume tiers. Carts are the exception. The buyer argument is ignored on cart queries, so you set buyer identity through cartCreate or cartBuyerIdentityUpdate instead.

2026 Shopify B2B Feature Benchmark: Liquid Theme vs Framer Frontend

Here is every B2B capability as of the Winter '26 Edition, mapped against where it actually executes and what plan it needs. "Checkout-side" means the feature works identically on a custom storefront because your frontend never touches it.

Two rows are the whole story. Everything marked checkout-side is free when you go headless, because Shopify still renders the checkout. The two bolded rows are the real cost of a custom storefront, and they are both frontend work rather than platform limits.

What Shopify B2B Pricing Looks Like Per Plan

Shopify B2B pricing is now a question about catalogs, not about access. Basic, Grow and Advanced can run up to three active catalogs across all B2B markets, with net terms, PO numbers, vaulted cards and ACH included. Plus removes the catalog cap, adds direct assignment to a specific company or location, and unlocks deposits and partial payments.

For a design-led brand with a handful of pricing tiers, three catalogs is often enough for the first year. The trigger for Plus is per-account pricing — once each stockist negotiates its own sheet, a cap of three stops the model rather than slowing it.

"Products not published for the current B2B customer will be removed from cart."

That line from Shopify's headless B2B documentation is the single most useful sentence for anyone building this. Switching buyer identity on a cart that already holds items can invalidate it, so resolve the company location before the first add-to-cart, not after.

Where a Custom Storefront Breaks B2B

Three failure modes account for nearly every broken headless B2B build, and all three are caching or sequencing problems rather than missing features.

The first is caching contextualized responses. A B2B price is specific to one company, so a CDN or static cache that holds it will eventually serve one stockist another's negotiated pricing. The second is the cart-identity ordering problem above. The third is a storefront that renders prices before the session resolves, which briefly exposes retail pricing on a gated catalog — the exact leak wholesale gating exists to prevent.

If you are wiring a Framer frontend to Shopify, the checkout customization boundaries and the buyer-context patterns behind Shopify Markets are the same mechanics applied to currency instead of company, and worth reading alongside this. The broader setup is covered in using Framer as a headless Shopify frontend.

Do You Still Need a Shopify B2B App?

Less often than in 2024, but the gaps are specific. Native B2B now covers accounts, catalogs, terms and PO capture, and the Winter '26 Edition brought eleven more third-party apps into B2B compatibility alongside EDI purchase-order sync through SPS Commerce and Crstl.

A Shopify B2B app still earns its keep for quoting and negotiated carts, approval chains above a value threshold, and ERP-driven credit limits. What it should no longer be doing is faking price lists with discount codes or hiding products with tag-based theme logic — that work is now native, and on a custom storefront it is one query parameter.

The payoff for getting the gating right is retention, not aesthetics: Shopify reports merchants adopting B2B see up to 4.1x higher reorder frequency than on DTC orders. A wholesale buyer who can log in, see their own prices and reorder in two clicks does it again. FramerLink exists to keep that buyer context intact between Shopify and a Framer frontend, which is the only part of this benchmark you have to build yourself.