2. Set Up Language & Locale
Once the initial ACC deployments are completed, the next essential step before proceeding with other configurations is setting the project locales and defining the default language.
What Are Locales?
Locales determine how language-specific content is managed and presented throughout the project. They control:
How product attribute values and other localizable data are stored and displayed,
Which languages are available for input and output in Omnitron and Commerce,
The localization of content across multiple channels and regions.
The locales you define will appear at the top of the Omnitron interface and serve as the basis for content management. For example, you can set tr-tr for Turkish and en-us for English, enabling you to manage product names, descriptions, or other translatable fields in both languages.
Locales must be defined before entering any data into Omnitron. If content is entered before locales are properly configured, re-entry may be required.
What Is the Default Language?
The default language determines which locale is used in requests and API responses when no specific language is provided by the client. For example, if no Accept-Language header is specified in a request, the system will respond using the default language.
This ensures consistency in responses and provides a fallback option for multilingual setups. It also affects system messages, validation errors, and user interface language when a specific language is not explicitly selected.
By default, English is set as the default locale.
If you plan to use a locale other than English or change the default language, this must be configured through environment variables in both the Commerce and Omnitron services.
The language settings defined via environment variables must be identical in both Commerce and Omnitron services. These settings must be applied immediately after the services are deployed and before any other configuration begins. Otherwise, language-related issues may arise later during your project setup or runtime.
Supported Languages in the System
Below is the list of ISO language codes currently supported by the system:
ar ➡ Arabic 🇸🇦
el ➡ Greek 🇬🇷
kk ➡ Kazakh 🇰🇿
nl ➡ Dutch 🇳🇱
pl ➡ Polish 🇵🇱
ro ➡ Romanian 🇷🇴
ru ➡ Russian 🇷🇺
sr ➡ Serbian 🇷🇸
tr-tr ➡ Turkish 🇹🇷
uk ➡ Ukrainian 🇺🇦If you require support for a language not listed above, please contact the Akinon team to discuss availability and integration options.
Setting Language Environment Variables
To set a default language and supported locales (e.g., Turkish as default along with English), follow the steps below:
Configure Language for Omnitron Service
Navigate to the Project Details page.
Click on the Omnitron service.
Click the VIEW ENVIRONMENT VARIABLES button.
Add the following two variables using the + NEW ENVIRONMENT VARIABLE button: For locales:
Name:LANGUAGESValue:tr-tr=Turkish,en-us=English
For default language:
Name:LANGUAGE_CODEValue:tr-tr
Configure Language for Commerce Service
Return to the Project Details page.
Click on the Commerce service.
Click the VIEW ENVIRONMENT VARIABLES button.
Again, add the same two variables as configured for Omnitron: For locales:
Name:LANGUAGESValue:tr-tr=Turkish,en-us=English
For default language:
Name:LANGUAGE_CODEValue:tr-tr
Final Step: Redeploy to Apply Language Settings
After adding the language environment variables, the new language settings will only take effect after a new version is deployed for both Commerce and Omnitron services.
📩 Please contact the Akinon team to request a new deployment version for each service.
Once deployment is complete, the newly added locales will become available and selectable within the Locales section in Omnitron Frontend.
Last updated
Was this helpful?