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

Products with real depth

Describe product types, variants, bundles and services without bending the order model out of shape.

01

Types and attributes

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

02

Variants in one place

Manage colours, sizes or capacities from a centralized screen so every variant keeps a consistent identity and price relationship.

03

Bundles and services

Sell grouped items or intangible services alongside physical products, using the same catalog and order flow.

Model for the customer, not the warehouse

A product page should answer the shopper's question before it exposes internal structure. Choose attributes that help comparison, then use categories and filters to make those attributes useful. Not every warehouse field belongs on a storefront.

Variants work best when the distinguishing choice is obvious. If shoppers need a table to understand the difference, the model or the presentation is probably too complicated.

Translation and maintenance

Product descriptions, attributes and media can be maintained per language. Keep a single source for factual attributes and translate the persuasive content around them.

Bulk editing is safer than repetitive manual entry for price and inventory changes. See the dedicated update tools for that workflow.

In practice
  • Define product types around customer decisions, not internal departments.
  • Use variant attributes only when the shopper must choose between them.
  • Keep a media naming convention so translations do not fragment the library.
  • Document which fields are shared and which are language specific.

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.
  • Unicode Character encoding and script support.
  • Unicode CLDR Locale data for dates, numbers and currencies.
  • NuGet Package distribution used by the .NET client and samples.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
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.