Languages per storefront
Choose the languages each store supports, then translate categories, products and content without creating separate catalogs.
Languages and currencies belong in the store model, not in a translation layer bolted on at the end.
Choose the languages each store supports, then translate categories, products and content without creating separate catalogs.
Present prices in the currency and number format the audience expects, with prices managed in the catalog rather than hard coded in templates.
Taxes, shipping zones and address formats can differ by market while the product record stays shared.
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.
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.
Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.
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.