Skip to content
Open source core .NET 4.5 and SQL Server Sannois, France
MAGELIAWebStore
Platform · 01 of 18

Several storefronts, one operations core

Open a storefront for each brand, country or audience, then keep catalogs, orders and permissions under a single roof.

01

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.

02

One product truth, several positions

A product can appear in more than one catalog with a different price list, description and category path per store.

03

Capacity follows the edition

The Community Edition supports one store, Professional supports five and Enterprise removes the store limit.

Where central control pays off

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.

When a second storefront is the right move

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.

In practice
  • Map each storefront to a clear audience and a single commercial purpose.
  • Agree which catalogs, price lists and warehouses are shared before launch.
  • Give each store a named owner for content, pricing and order escalation.
  • Review store level permissions whenever a new market goes live.

Related capabilities

Primary sources

Reference shelf

Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.

  • .NET platform Runtime, tooling and framework documentation from Microsoft.
  • OData The open data protocol used by the WebStore services layer.
  • SQL Server Database engine documentation and editions.
  • NuGet Package distribution used by the .NET client and samples.
  • W3C Web standards for markup, accessibility and internationalization.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
  • OWASP Application security guidance and cheat sheets.
  • Open Source Initiative License review and the open source definition.
  • Schema.org Structured data vocabulary for product and organization markup.
  • Microsoft Learn Reference material for the Microsoft development stack.
Next step

Put this capability against your own catalog

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.