Skip to main content

Localization overview

The Localization app controls which languages your storefront supports and lets you manage the custom translation keys that those languages use.

N
Written by Niyaz

The Localization app manages the languages supported by a storefront and the custom translation keys used by those languages. The application governs presentation resources and locale configuration rather than tax, exchange rates, financial amounts, legal compliance, or commercial policy.

Localization areas

The Localization application is organized around the Client Languages and Client constant keys areas. The Client Languages area determines which languages the storefront supports and which language is the default. The Client constant keys area manages the storefront's custom translation keys.

Client Languages

The Client Languages screen includes Supported Languages and Default language groups. The supported-language options are English, עברית, and العربية. Set the supported languages before assigning custom translations or Content Ready Components. Removing a supported language permanently deletes the custom translations associated with that language. Adding a language automatically assigns corresponding translations to existing custom constants.

Client constant keys

The Client constant keys area narrows the platform's full catalogue of shop translation keys to the subset a tenant activates. Activation uses a platform-wide catalogue rather than free text. The catalogue is large relative to the activated set, so activation is a selection task rather than an authoring task.

Why the language set comes first

The two areas are ordered by dependency rather than preference. Adding a language populates translations for every custom constant that already exists. Set the language set first to avoid the repeated work that a later language addition creates. The reverse order is not prevented, but it requires more work.

Synchronization

Both localization areas provide a Sync control to push the current build to the storefront.

Localization boundaries

Localization owns locale and resource workspaces, translation drafts, presentation policies, coverage validation, localized preview, and release candidates. Localization does not own tax calculation, exchange-rate authority, accounting currency, price, legal interpretation, business rules, or runtime source facts.

Related

Did this answer your question?