How to Build Multiple Branded Storefront Experiences Under One Shopify Admin?

Theme Store
1

Hi Devs,

I’m looking for insights on the best architecture to achieve a multi-brand storefront experience under one Shopify store / one Admin, similar to what MUST Société / Maison Corbeil / Jardin de Ville are doing https://mustsociete.com/ please visit this website and click the top left menu items on desktop to understand what I mean and go deep in browsing in each.

What I’m trying to build

I need to manage multiple storefront identities under the same Shopify store:

  • Different homepages per brand

  • Different headers, logos, menus, and color themes depending on the active brand

  • Brand-specific product pages (logo + header should remain tied to the brand the user entered from)

  • Separate collections, content, navigation, and banners

  • One Shopify admin, one inventory, one checkout

Basically:

One Shopify store → Multiple branded storefronts that switch dynamically and maintain state as the customer navigates.

What I’ve noticed on competitors doing this

Brands like Must Société / Maison Corbeil seem to achieve:

  • Storefront changes based on which sub-brand the customer enters

  • The header + logo persist even on product pages

  • URL structure remains inside ONE store (not headless, not Shopify Plus multi-store)

  • I suspect they use localStorage / session storage or a route-based switch to maintain the “active storefront” identity

  • Each brand appears as a visual layer on top of the same catalog, not a separate store

What I need clarity on

  1. What is the recommended approach for managing multiple storefront identities inside one Shopify theme?

    • Separate templates?

    • Theme app extensions?

    • Route-based detection?

    • Metaobjects powering brand configurations?

  2. How to persist the selected storefront (header + logo + theme) across the session so product pages don’t fall back to the “global default” theme?

  3. Is this achievable with Online Store 2.0 alone, or does it require:

    • Custom JS with browser storage

    • A proxy app

    • Multiple unpublished theme instances

    • Hydrogen + Oxygen (headless)?

  4. Best practices for managing navigations, mega-menus, and content for each sub-brand while keeping everything inside one Admin?

Goal

Create something like:

  • /brand-a → Brand A homepage, logo, header, collections, product pages branded as A

  • /brand-b → Brand B homepage, logo, header, collections, product pages branded as B

Without duplicating the entire store or going headless unless absolutely required.

If anyone has done this or understands the architecture behind these implementations, I would love insights on:

  • Theme structure

  • Data modeling (metaobjects or metafields)

  • How to persist brand selection during browsing

  • Limitations to be aware of

Thanks in advance — any architecture recommendation or example would help a lot.

3

I think a lot of this could be achieved natively by relying on metafields and metaobjects to store brand specific information, and then building logic that displays the particular header and storefront properties.