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

Price lists that behave like your business

Build an assortment once, then give each audience the products and prices that belong to it.

01

One product, many price lists

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

02

Assortments by audience

Assign a product to any number of catalogs and categories, then publish only the relevant catalog to each storefront.

03

Controlled change

Price and product updates can be staged, validated and applied in bulk rather than edited one item at a time.

Pricing is a business rule, not a field

A single list price rarely survives contact with real trading. Contract pricing, regional differences, currency rounding and promotional overlays all need somewhere to live. WebStore separates the product record from the price list so each commercial conversation can have its own terms.

Because the catalog is also the assortment boundary, it becomes a useful permission and publishing unit. A partner storefront can receive one catalog while the public site receives another.

Keep the model explainable

Name catalogs after the audience they serve, not after the person who created them. Document which catalog drives which storefront and who may change prices. A small amount of naming discipline prevents most pricing incidents.

In practice
  • Use one base catalog for shared product content and separate catalogs for commercial differences.
  • Record the effective dates and owner of every price list.
  • Test currency rounding before a market goes live.
  • Review stale catalogs at the same time as seasonal price changes.

Related capabilities

Primary sources

Reference shelf

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

  • Schema.org Structured data vocabulary for product and organization markup.
  • W3C Web standards for markup, accessibility and internationalization.
  • MDN Web Docs Reference for HTML, CSS and JavaScript behavior.
  • .NET platform Runtime, tooling and framework documentation from Microsoft.
  • SQL Server Database engine documentation and editions.
  • OData The open data protocol used by the WebStore services layer.
  • NuGet Package distribution used by the .NET client and samples.
  • 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.
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.