Shopify B2B on one store: how to run wholesale and DTC without separate systems

What this guide is really about

Shopify B2B is finally a one-store conversation for normal merchants, not just enterprise teams. That changes the question.

The question is no longer, "Can Shopify do wholesale at all?" It can. The real question is whether one blended store gives you operational leverage, or whether it quietly turns into a compromise that makes pricing, merchandising, checkout, and staff workflows harder every quarter.

A lot of merchants overcorrect here. They assume wholesale automatically needs its own store because that feels more serious. In practice, that often creates duplicate theme work, duplicate apps, split reporting, extra integration work, and unnecessary inventory separation before the business has earned that complexity.

The opposite mistake is just as common. A team keeps everything in one store long after the B2B side has clearly outgrown shared merchandising, shared checkout behavior, or shared catalog logic.

“For the first time, merchants on every Shopify plan can manage wholesale and DTC from a single platform.”

This guide is the practical middle ground. Use one store by default when the operating model is still genuinely shared. Split only when the requirements stop being shared in a meaningful way.

When one Shopify store is the right B2B model

Shopify calls the one-store model a blended store. It means one admin, one storefront, the same overall branding, and shared inventory for both DTC and B2B buyers.

That model is strongest when wholesale is a different buying context, not a different business. The buyer might need net terms, company permissions, price breaks, or B2B-only products, but the underlying catalog and operations still belong to the same core store.

A blended store is usually the right call when all of the following are true:

• You sell many of the same products to both retail and wholesale buyers.
• You want inventory to stay shared instead of split across separate stores.
• The same team handles merchandising, pricing governance, and support.
• B2B needs different rules, not a fully separate brand.
• You want one analytics and operations surface instead of two.

The part people get wrong is assuming blended means “everything is shared and nothing is contextual.” That is not how Shopify B2B works now. B2B buyers can be separated through companies, company locations, catalogs, payment terms, permissions, and logged-in customer account behavior. You can also use Markets to tailor pricing, tax handling, theme context, and product availability for B2B groups.

If you need the broader merchant-facing operating model behind those choices, read

. This article is narrower. It is about when one store stays sane, and when it stops.

Where blended stores break down

One store stops being elegant when the wholesale side no longer behaves like a contextual variant of the retail business.

The first breaking point is pricing complexity. If you only need a few wholesale segments, a blended setup is clean. If every major account needs its own negotiated catalog logic, regional exceptions, and account-specific edge cases, the architecture starts to lean either toward Shopify Plus or toward a dedicated store.

The second breaking point is storefront divergence. If B2B buyers need a completely different navigation model, gated pages, a different merchandising rhythm, different landing pages, and different content strategy, then one theme becomes political. Every change turns into a DTC versus B2B compromise discussion.

The third breaking point is checkout and payment behavior. A healthy blended model can still support different payment methods, net terms, draft-order review flows, PO numbers, and one-time shipping address rules. But once your B2B checkout becomes a heavily negotiated process with deposits, partial captures, and account-level exceptions, the simpler one-store pattern loses some of its charm.

The fourth breaking point is organizational. If wholesale has different staff ownership, different support processes, different sales reps, and different commercial rules, forcing everything through one storefront and one shared governance model can create more friction than it removes.

In other words, the limit is not “B2B is more advanced now.” The limit is “Are these still the same business in practice?”

A dedicated B2B store is usually the better move when you need separate inventory, separate staff ownership, a fully gated storefront, or a genuinely distinct wholesale brand experience.

The setup pattern that works

The best blended implementations follow a boring pattern. That is a compliment.

1. Decide on the store model before you touch theme work

Start by deciding whether you are building a blended store or a dedicated one. Do not start by designing wholesale landing pages or installing apps. The structural choice changes everything that follows, including login, catalogs, analytics, and staff permissions.

2. Turn on customer accounts and create a clear wholesale entry point

Customer accounts are not optional for B2B. They are how logged-in buyers access B2B pricing, B2B-only products, and company account information.

In a blended store, the cleanest move is usually to add a visible wholesale entry point rather than forcing the main DTC navigation to carry all the context. A footer link, header utility link, or dedicated wholesale landing page that routes buyers into customer accounts is usually enough.

3. Model wholesale buyers as companies and company locations

Do not fake wholesale by stuffing tags onto ordinary customers and hoping discount logic holds. Shopify gives you a proper B2B model for a reason.

Use companies and company locations as the main operating unit. That lets you control location-level permissions, payment terms, catalogs, tax settings, addresses, and checkout behavior in a way that scales beyond one or two friendly wholesale customers.

4. Use catalogs and Markets for segmentation

Catalogs are the core of a blended B2B setup. They decide which products and prices a B2B buyer can access.

If your non-Plus setup only has a few wholesale segments, keep it simple. Create a small number of B2B markets such as “All Wholesale”, “EU Wholesale”, or “Distributors”, then attach catalogs to those groups. Do not create a fake custom architecture in apps and discount hacks when native catalogs are already the correct system boundary.

5. Set checkout rules at the company-location level

This is where one-store B2B becomes useful instead of cosmetic.

Company locations can carry payment terms, PO number behavior, draft-order review flows, saved cards, shipping rules, and tax settings. That means the buyer context lives with the account, not in fragile front-end logic.

If a buyer should submit every order for review instead of paying immediately, use the company-location setting for draft submission. If B2B and DTC need different payment methods, use Shopify’s checkout customization tools to contextualize them instead of trying to explain the difference in help text.

6. Keep theme changes deliberate

In a blended store, the job is not to make the whole storefront look wholesale. The job is to reveal wholesale-specific behavior only where it matters.

That usually means:

• showing B2B-only pricing and product access after login
• adding a wholesale-focused account entry point
• showing quantity rules, price breaks, or quick ordering patterns where appropriate
• hiding or de-emphasizing retail-oriented messaging inside the logged-in wholesale context

The trap is turning the entire theme into a giant if-statement.

7. Build intake and approval like an operating workflow, not a contact form

If you want new wholesale buyers to request access, use company account requests and route approvals through a real review process.

That means deciding:

• who reviews new wholesale applications
• what fields you need on intake
• which catalog a new account should land in
• whether ordering is auto-approved or manually approved
• what onboarding email or sales follow-up happens next

Wholesale is usually won or lost here. Not in the theme. In the approval and onboarding workflow.

How plan limits change the architecture

This is the part that determines whether your “simple one-store setup” is actually simple.

Shopify now gives foundational B2B features to stores beyond Plus, which is a big deal. But non-Plus does not mean unconstrained. Your article, proposal, or architecture doc should say that out loud.

There is one especially important non-Plus caveat. On Basic, Grow, and Advanced, B2B catalog features depend on new Shopify Markets. That means your segmentation model should be market-aware from the start.

Another real-world caveat is theme support. Quantity rules are supported on free Shopify themes version 8.0.0 and later, while volume pricing is supported on version 11.0.0 and later. On custom themes, a developer might need to wire the storefront display deliberately instead of assuming it just appears.

The honest recommendation is this:

• Use non-Plus for straightforward wholesale tiers and shared operations.
• Use Advanced when contextual storefront or checkout actually matters.
• Use Plus when wholesale pricing and payment behavior become account-specific enough that three market catalogs stop being realistic.

The operating model agencies should implement

Agencies should stop pitching one-store B2B as a theme project. It is an operating model project with a theme layer attached.

A solid implementation usually has six workstreams.

1. Commercial model

Define who buys, how they are grouped, who gets what price logic, which buyers need terms, and which buyers must submit orders for review.

2. Data model

Define companies, company locations, permissions, addresses, tax handling, and who internally owns account setup.

3. Catalog model

Decide whether you are segmenting by region, buyer type, or named accounts. If you are on a non-Plus plan, be ruthless here. Three catalogs means three catalogs. Do not pretend twenty customer-specific price books are going to fit inside that.

4. Storefront model

Decide what changes for logged-in wholesale buyers. That might include contextual content, quick ordering, pricing visibility, restricted pages, or wholesale-specific navigation. Keep this tight. The more you fork the theme, the more expensive future changes become.

5. Checkout and payment model

Decide which buyers pay now, which buyers use net terms, which buyers submit drafts for approval, and whether B2B payment methods must differ from DTC. This is where agencies should scope checkout customization honestly instead of hand-waving it.

6. Intake and workflow model

Decide how new wholesale customers apply, who approves them, which Flow automations run, how reps are assigned, and what the onboarding handoff looks like.

If an agency cannot explain those six layers, it has not scoped a B2B project. It has scoped a redesign with wholesale adjectives.

The best agency deliverable here is not a Figma file. It is a simple decision document that answers:

• Why are we blended instead of dedicated?
• How many catalog segments do we actually need?
• Which plan is sufficient today, and why?
• What exact events force a later split into a dedicated B2B store?

That document saves a lot more money than a pretty wholesale landing page.

Common mistakes when mixing wholesale and DTC

• Treating B2B like a discount-code problem instead of a companies and catalogs problem.

• Launching a dedicated B2B store before there is any meaningful need for separate inventory, branding, or operations.

• Ignoring the non-Plus catalog limit and discovering too late that the whole model depends on more segmentation than the plan can support.

• Assuming logged-in wholesale buyers will automatically get a good storefront experience on a custom theme without deliberate work.

• Forgetting that B2B needs customer accounts, then wondering why the storefront behaves like retail.

• Gating the entire storefront and then realizing that prospective buyers can no longer use company account requests.

• Letting the theme absorb account logic that should live in company locations, catalogs, and checkout settings.

• Pitching “one store for both” as if it means less strategy. It often means more strategy, just with less duplicated infrastructure.

The right mental model is simple: keep the store unified, but keep the buyer context explicit.

That means native account structures, native catalogs, native checkout rules, and tightly scoped storefront differences. Not a pile of hidden conditions spread across apps, theme code, and support notes.

Best internal links

• Shopify B2B guide for merchants

  for the broader B2B operating model beyond the one-store question.

• How to optimize Shopify product pages for conversion

  for the PDP messaging and trust layer once wholesale and retail shoppers share the same storefront.

• Shopify collections strategy guide

  for the catalog and navigation structure that keeps shared-store merchandising from getting muddy.

• Shopify app stack audit

  for checking whether wholesale complexity is being handled natively or papered over with overlapping apps.

Sources and further reading

• Shopify brings native B2B features to millions more merchants

• Choosing a store type for your B2B business on Shopify

• Shopify B2B features by plan

• Catalogs and pricing in B2B

• B2B and Markets

• Sign-in and customer accounts in B2B

• Allowing new B2B customers to request access to your store

• Checkout, orders, and draft orders in B2B

• Managing checkout settings in B2B

• Displaying quantity rules and volume pricing on your store