One Adobe Commerce Instance.
Unlimited Storefronts.

A website is the top-level entity — it holds its own pricing and customer scope. A store is a subset of a website with its own catalog and category tree. A store view is a specific locale or language within a store — it controls translations, currency display, and theme overrides. Redefine uses this hierarchy to isolate exactly what needs to be different per brand or region while maximizing what is shared.

Yes. Adobe Commerce supports per-store-view theme assignment. Redefine builds a base theme with shared components, then applies brand-specific overrides per store view. Updates to the base theme propagate to all stores. Visual overrides remain isolated to each brand. You do not need separate codebases to run separate visual identities.

Adobe Commerce's Multi-Source Inventory (MSI) allows you to assign stock sources per storefront or share a central pool. Redefine configures MSI to match your fulfillment model — whether that is a single warehouse serving all stores or regional warehouses routing orders by store view. Stock visibility and reservation logic are scoped per your operational requirements.

Each store view adds indexing surface and cache segments, so infrastructure must be sized correctly. Redefine benchmarks your target storefront count against your catalog volume before launch. Full-page cache, Varnish configuration, and Elasticsearch tuning are designed for multi-store load, not single-store defaults.

A two-to-four storefront build typically takes 6 to 10 weeks from architecture sign-off to the first live storefront. Five to ten storefronts run 12 to 20 weeks with a phased rollout strategy. Enterprise builds over 10 storefronts are sequenced across 24 or more weeks with parallel sprint tracks. All timelines begin after discovery and scoping, which Redefine delivers in 3 business days from your brief.