Shopify B2B: blended or dedicated store?

1. Identify the requirement that can rule a structure out

Start with six inputs: shared SKUs, stock ownership and allocation, staff responsibilities, current plan and market design, connected systems, and public discovery needs. For each requirement, write mandatory or preferred. A preference can be traded against cost. A mandatory requirement needs a demonstrated solution before approval.

Replace broad statements with observable behavior. “Wholesale is different” does not tell a developer what to separate. “Retail orders must never consume the 200 units reserved for trade customers” does. Name the system that owns that reservation and the person allowed to release it.

Choose the hardest row first. A beautiful B2B homepage cannot compensate for a mandatory stock rule that the proposed architecture has not solved.

2. Draw the stock and system boundary

Shopify documents a blended store as one admin with shared stock, without inventory allocation by customer type. A dedicated store has a separate admin and inventory, and its integrations need reconfiguration. Read the store-type comparison.

Draw a line from the inventory authority to each storefront and order destination. Label every connection with its owner, sync direction, identifier, and failure response. “ERP connected” is insufficient: identify whether it controls available stock, prices, fulfillment, company records, or several of these.

If a warehouse serves two stores, separate store inventory does not itself design the warehouse allocation process. Require a written answer for simultaneous orders, transfers, oversells, cancellations, and sync delays. If an outside system is proposed to allocate shared stock, treat that as a separate dependency to demonstrate, with its own support owner.

I would keep a stock reservation requirement open until the person responsible for inventory can explain what happens during a failed sync. Entering an assumed app capability as “solved” only moves the decision into launch week.

3. Separate price segmentation from a second store

Catalogs can define B2B product access and prices inside the same store. In a blended store, merely adding an item to a B2B catalog does not make it trade-only. First verify that every D2C market where you sell has an active region market catalog, assigned directly or inherited from a parent market. Without an applicable region market catalog, that market falls back to products published to Online Store and can expose the trade-only item. Then include the item in the appropriate B2B catalogs, exclude it from all region market catalogs, and keep it published to Online Store so approved B2B buyers can browse it after login. Hold approval of the trade-only setup until this coverage and the exclusions are verified in every D2C selling market. Check the current catalog and availability rules.

List the products that are shared, wholesale-only, retail-only, or packaged differently. A case pack sold as a separate product needs a deliberate stock and fulfillment mapping. Do not assume that two product records automatically consume a common underlying stock component correctly.

Record what a logged-out visitor, D2C customer, and approved company buyer should see for the same product URL. If prices are private, add a separate data-access review. Hiding a price label is not proof that the information is protected across every data surface.

Check plan fit independently of store type. As checked on October 31, 2026, native B2B is available on Basic, Grow, Advanced, and Plus, excluding Starter and Retail. Contextual storefront and checkout customization through Markets requires Advanced or Plus. Read the plan-specific feature list. Choosing dedicated does not remove the need to verify the exact capability.

For B2B/D2C content changes through the native theme editor, Shopify’s store-type guidance also scopes the free-theme route to version 11.0 or later. Older or custom themes need their own implementation review. Check the theme-specific scope. Put the installed theme and version in the brief rather than approving the design from plan eligibility alone.

4. Map entry, sign-in, and approval before gating

B2B uses customer accounts. A blended store can keep legacy accounts for D2C; if both audiences use customer accounts, they share the login page. Check account behavior by store type. Decide whether the business needs different account presentation, different access, or both.

A fully gated dedicated storefront cannot expose the public Shopify Forms company-request journey to applicants who cannot enter. Plan the public application route before selecting the gate. The request feature creates a new company, location, and customer; it does not add a colleague to an existing company. Read company-request scope and the gated-store limitation.

Write four acceptance scenarios: a new applicant finds the entry route; a pending applicant receives no unapproved buying access; an approved buyer reaches the intended company location; and an existing company can follow its separately defined add-user process. Define who approves access and how support handles a buyer assigned to the wrong location. Do not use a successful login as proof of correct commercial access.

5. Quote the work that a second store adds

For every app and integration, record installed store, data scope, subscription basis, credentials owner, configuration owner, support terms, and removal consequences. Ask each supplier whether a second installation, license, connector endpoint, or separate configuration is needed. Keep an unanswered quote line marked unknown rather than zero.

Compare actual setup charges, recurring licenses, implementation work, maintenance, operator time, and the cost of recovering a failed update over the same planning period. Store count alone does not produce a reliable project price. Require currency, taxes, contract term, exclusions, and who maintains custom work.

6. Approve the boundary with observable buyer and staff tasks

Before build approval, retain the operating map, chosen route, rejected alternative, unresolved exceptions, and an owner for each dependency. A useful decision sentence is: “Investigate blended because stock and operators are shared; hold approval until trade-only visibility and case-pack stock mapping are demonstrated.” It states both the direction and what can change it.

For acceptance, run the logged-out, D2C, approved-company, and pending-company scenarios with representative shared and exclusive products. Include order routing, inventory changes, cancellation, staff access, and a failed connector update. Record expected and observed behavior against the exact candidate configuration.

If a wholesale product leaks publicly, inspect catalog and D2C market exclusions. If a buyer cannot apply, inspect the gate and public entry path. If stock is consumed by the wrong audience, reopen the allocation design instead of adjusting the storefront label. If two stores create repeated manual updates, inspect the ownership and integration assumptions in the quote.

Changing structure later is significant: Shopify says most company, catalog, and storefront setup must be redone. Review the switching warning. Save the migration and recovery owner now, while the work can still be scoped. Your next step is to fill the stock row and the applicant-entry row. Those two answers usually make the remaining comparison much more concrete.