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

International from the first screen

Languages and currencies belong in the store model, not in a translation layer bolted on at the end.

01

Languages per storefront

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

02

Currencies and formatting

Present prices in the currency and number format the audience expects, with prices managed in the catalog rather than hard coded in templates.

03

Regional rules

Taxes, shipping zones and address formats can differ by market while the product record stays shared.

Translation is a workflow

A multilingual site fails when translation is treated as a final copy exercise. Build the language list into the store definition, assign responsibility for each language and translate category and product content as it is created.

Not every field needs a translation. Codes, dimensions and other factual attributes can remain shared while marketing copy changes.

Respect local expectations

Currency symbols, decimal separators, date formats and address order all affect trust. Use locale data rather than a single global format. Then test a complete order in each market, not only the product page.

In practice
  • Define the language and currency pair for each storefront before launch.
  • Translate category names and navigation labels, not only product descriptions.
  • Test checkout with local address and tax examples.
  • Assign one owner per language for tone and terminology.

Related capabilities

Primary sources

Reference shelf

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

  • Unicode Character encoding and script support.
  • Unicode CLDR Locale data for dates, numbers and currencies.
  • EU VAT information exchange VAT number validation for cross border trade.
  • W3C Web standards for markup, accessibility and internationalization.
  • .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.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
  • NuGet Package distribution used by the .NET client and samples.
  • Schema.org Structured data vocabulary for product and organization markup.
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.