A store is a configuration, not a new installation
Each storefront gets its own domain, languages, currencies, presentation and assortment while the commerce engine stays shared.
Open a storefront for each brand, country or audience, then keep catalogs, orders and permissions under a single roof.
Each storefront gets its own domain, languages, currencies, presentation and assortment while the commerce engine stays shared.
A product can appear in more than one catalog with a different price list, description and category path per store.
The Community Edition supports one store, Professional supports five and Enterprise removes the store limit.
A second storefront should not create a second operations team. WebStore keeps the customer record, inventory position and order queue central, so support staff can answer a question once rather than searching across disconnected systems.
Brand teams still get room to differ. Each storefront can choose its own theme, navigation, language set and currency, and can expose only the catalogs that belong to that audience.
A regional launch, a wholesale portal beside a retail site or a seasonal campaign site can all be modelled as separate stores. The decision is usually about presentation and audience, not about duplicating the commerce engine.
If the requirement is instead to host unrelated sellers with their own administration, look at multitenancy. The two features solve different problems and can be combined.
Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.
The useful test is a real assortment, a real market and a real order. Bring those to a conversation rather than a generic feature list.