Product Localizations Configuration
Localizations allow you to manage multilingual and multi-region product information, maintaining translated attributes and descriptions.
To configure languages you must be an Administrator or have the Can manage platform languages permission.
View active localizations
In the main table you can monitor the languages already configured in the system:
Localization Code: Standard identifier (e.g. en_US, fr_FR).
Description: Extended name of the reference market/language.
Activate a new language
Enabling a new localization immediately makes the translation fields available in the catalog.
Click on Enable new language (top right).
Select the desired localization from the drop-down menu.
Click on Enable.
The table will update instantly showing the new operational language.
Localizations cannot be disabled.
Once activated, a localization remains persistent in the system. Carefully plan which markets to enable to avoid overloading the interface with unnecessary fields.
Recommended Configuration
If you are configuring THRON for the first time, only activate the Locales corresponding to the markets in which you operate today. You can add more at any time, but not remove them.
A typical starting point for an Italian company selling also in the UK market:
| Market | Localization Code | Description |
|---|---|---|
| International | en_GB | English (United Kingdom) |
| Italy | it_IT | Italiano (Italia) |
We recommend adding a new Locale only when you have teams or processes ready to compile the information in that language. An active but unfilled Locale generates incomplete product sheets in completeness analyses.
Limits and System Logics
This section collects the technical details necessary for advanced management.
Synchronization: Activating a localization has a global impact on the PIM. Every "localizable" type attribute will show a new input field for the inserted language.
API Integrations: For external automation or synchronization of translated content, consult the dedicated technical documentation: Product Data Model - Locale API.
Exceptions: If a specific localization is not present in the selection menu, send a request to technical support for integration into the global database.
Best Practice
Plan before activating. Define with the team which markets are actually active in the next 12 months before enabling new Locales. Adding too many from the beginning creates unnecessary complexity in filling out product sheets.
Link Locales to localized attributes. A Locale alone is not enough: so that product information can be compiled for that market, make sure that the attributes that contain variable data by language (e.g. name, description) have the Localizable Value flag active. See the guide Create Product Attributes for details.
Monitor completeness. After adding a new Locale, set up a completeness Marker to track products not yet translated into that language.