Foundation · 2 min
What you need to know
When does a business need multiple ecommerce stores?
Multiple stores are justified by distinct brands, entities, catalogs, customers, pricing, operations or data boundaries that overrides cannot manage safely.
Should multiple brands use separate stores?
Separate stores when brands require different customer experiences or governance; shared operations may still use common catalog and fulfillment services.
Should B2B and B2C use separate storefronts?
Separate storefronts may help when buyers, contracts, prices, checkout and service differ materially but avoid duplication when one experience can branch cleanly.
How should multiple stores share product data?
Use stable global product identities and governed shared facts with explicit store-specific offers, content and eligibility.
How should multiple stores share inventory?
Share a location-based inventory ledger and reservations when stores draw from the same stock; avoid periodic totals that allow simultaneous overselling.
How should orders from multiple stores be managed?
Aggregate orders into one operational view while retaining store, entity, currency, policy and fulfillment context.
How should permissions work across multiple stores?
Use scoped roles by store and function, with controlled cross-store access for shared teams and auditable high-impact actions.
How should reporting work across multiple stores?
Provide both store-level performance and consolidated results using common definitions, eliminations, and currency treatment.
A quick store check
Trace a shared product and order across two stores and verify inventory, permissions, entity and reporting boundaries.
Foundation · 2 min
Frequently asked questions
Can stores share inventory but use different SKUs?
They need a durable mapping to the same stock identity and location ledger.
Should consolidated reporting hide store results?
No. Preserve store detail alongside reconciled totals.