Do multi-brand companies need a separate blended-vs-dedicated decision for each brand, or can one architecture serve all brands?

Two different questions hiding inside one

The decision genuinely is per brand, because every input to it is per brand: assortment, buyer type, staffing, inventory pooling, contract structure. A house-of-brands portfolio can correctly land on blended for one brand and dedicated for another.

The constraint is not per brand. It sits on the contract, and it is the thing that turns a set of independent decisions into a single architecture question.

The contract-level facts

• "Shopify Plus plan organizations can have a maximum of ten stores on their contract with no additional cost: One main store. Nine expansion stores" (per Shopify Help Center, September 2026).
• "For additional stores, it costs an extra $300 USD per month per store" (per shopify.com/plus/pricing, September 2026).
• Pre-approved store types include "B2B wholesale stores... Limit of one free B2B store per contract" and "D2C stores for wholesale merchants... Limit of 1 free B2C store per contract" (per Shopify Help Center, September 2026).
• "Apps are billed on a per-store basis rather than for the entire organization," and "Theme licenses are required for each individual store" (per Shopify Help Center, September 2026).

Put those together for a four-brand group that wants a dedicated B2B store per brand. The first is pre-approved and free. The other three are not on the pre-approved list as described, and each store consumes a slot from the same nine. Beyond ten stores, each is $300 USD per month plus its own apps and its own theme license.

That is the arithmetic that forces one architecture on most portfolios, and it is a contract fact rather than a design preference.

How the decision actually decomposes

The last row is the one that decides most real portfolios. A distributor who buys from three of your brands is three unrelated company records in three admins, with three credit relationships, three terms configurations and three sets of order history. Nothing in Shopify reconciles them. If your wholesale buyers overlap across brands, the case for consolidating wholesale into one store is much stronger than the case for splitting it by brand, and it is the opposite of how the DTC side of the portfolio is usually organised.

The three patterns we see, and when each is right

One blended store per brand. Correct when each brand has its own wholesale buyers, its own assortment and its own team, and none of them has hit a catalog or experience wall. Cheapest to run, no cross-store reconciliation, and every brand keeps full agentic-channel exposure on its DTC assortment because B2B-only products are excluded from Shopify Catalog per product rather than per store (per Shopify Help Center, September 2026).

One shared wholesale store across brands, DTC stores stay separate. Correct when buyers overlap, when a single sales team sells the whole portfolio, and when one credit relationship per customer is the finance requirement. Uses the single free B2B store slot as intended. The cost is that the wholesale store carries multiple brands' products in one catalog structure, which is a merchandising problem rather than a platform one.

Dedicated B2B per brand. Correct when brands are operationally independent to the point of separate legal entities, separate inventory and separate buyers, and when the portfolio can carry the store count. Most expensive by a wide margin, and the store count has to be checked against the nine before anyone designs anything.

The question that sorts a portfolio in one meeting

Do your wholesale buyers buy from more than one of your brands?

If yes, wholesale wants to be consolidated and the brand boundary is the wrong seam to cut on, whatever the DTC side does. If no, the per-brand decision really is independent and you are only constrained by slot count and budget.

When NOT to design this per brand

• When one brand is materially larger than the others. Design for that brand and let the rest inherit, or you will build three architectures to serve a rounding error.
• When the portfolio is still acquiring. Every acquisition arrives on somebody else's platform with its own wholesale process. An architecture that assumes a fixed brand count is obsolete at the next deal.
• When the brands share a warehouse. Shared physical inventory across separate stores means an integration nobody has budgeted, because stores do not share inventory by default.
• When the driver is org chart rather than customer. Brand managers wanting their own admin is a real organizational force and a bad architectural input.