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

The commerce model, capability by capability

Catalog, store, price, promotion, tax, delivery, content and order. Each capability has a page because each one carries a decision.

Capability index

Filter by the work in front of you

The groups are a reading aid, not a product boundary. Most stores use several groups at once.

01 / 18

Multi store environment

Each storefront gets its own domain, languages, currencies, presentation and assortment while the commerce engine stays shared.

Read the capability
02 / 18

Catalogs and price lists

The same product can carry different prices in different catalogs, so retail, wholesale and partner audiences stay separate without duplicate records.

Read the capability
03 / 18

Categories

Create category levels that mirror how customers browse, then assign any product to any category without moving the product record.

Read the capability
04 / 18

Products and services

Define product types for clothes, devices, media or services, then attach the attributes each type needs.

Read the capability
05 / 18

Ecommerce marketing and SEO

The storefront layer is yours. Build the markup and interaction you need instead of accepting a fixed template.

Read the capability
06 / 18

Customers and orders

Manage status changes, order versions and comments in the administration console so the current state is never a guess.

Read the capability
07 / 18

International support

Choose the languages each store supports, then translate categories, products and content without creating separate catalogs.

Read the capability
08 / 18

Taxes

Build tax zones for geographic areas, assign tax categories to products and define the rates that apply.

Read the capability
09 / 18

Sales promotion

Define when an offer applies and what it does, from percentage reductions to shipping or order level benefits.

Read the capability
10 / 18

Warehouse and inventory

Create warehouses that match physical locations and keep stock positions separate without separating the catalog.

Read the capability
11 / 18

Prices and inventory updates

Work with purpose built screens for tier pricing, prices and inventory instead of editing products one by one.

Read the capability
12 / 18

Shipping

Group destinations into shipping zones that reflect carrier coverage, then expose the methods each zone supports.

Read the capability
13 / 18

Scalability and performance

The services are designed to answer useful questions in fewer requests, which reduces chatter between the storefront and the engine.

Read the capability
14 / 18

Third party integration

The commerce engine is reached through a services layer, so the storefront technology is a choice rather than a constraint.

Read the capability
15 / 18

Scheduler and data integration

Create recurring jobs for order confirmation emails, data imports and exports, or routine catalog maintenance.

Read the capability
16 / 18

Flexible and extensible

The .NET client, the ASP.NET MVC sample store and the administration console shorten the distance from install to a working storefront.

Read the capability
17 / 18

Multitenancy

A single WebStore server can host several sellers and their stores while the administration console stays central.

Read the capability
18 / 18

Product direction

The long term direction has been to let teams add or replace behaviour in modules rather than editing the core.

Read the capability

Filter note The filter changes which capabilities are visible. It does not change the edition you need.

How it fits

A short path through the model

Most implementations follow the same route from catalog definition to a live order.

From product truth to a delivered order

Start with the product and category model. Put the products into a catalog, attach a price list and decide which storefront receives that catalog. Taxes and shipping turn the basket into a price the customer understands. Promotions adjust that price under explicit rules.

When the order arrives, the order record and the inventory position become the operational truth. The scheduler and import export tools keep that truth aligned with the rest of the estate.

DefineCatalog, category, product type, variants and content.
PublishStorefront, language, currency, assortment and price list.
PriceTax zones, shipping rules, promotions and currency rounding.
OperateOrder status, inventory, customer history and scheduled handoffs.
Primary sources

Platform 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.
  • Microsoft Learn Reference material for the Microsoft development stack.
  • GitHub Source hosting and issue tracking for .NET projects.
  • OWASP Application security guidance and cheat sheets.
  • Semantic Versioning Version numbering conventions used in release notes.
  • W3C Web standards for markup, accessibility and internationalization.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
Next step

Choose the capability that is blocking the next release

The whole platform does not need to be implemented at once. Start with the part that changes the customer's experience or the team's workload.