Sales Layer lets you manage content in more than one language by storing different language versions inside the same field. This is useful when you want to keep product information organized while working with several markets or regions.
The languages in your account are set when the account is created, but you can update them later if your catalog needs to support additional languages.
Add or remove languages in your account
To manage the languages available in your catalog, go to the Translations tab and click Actions > Modify languages. From there, you can add or remove languages as needed.
Sales Layer also lets you add local variants of a language, such as US English or Argentinian Spanish, from the Local Variants tab. In the same area, you can choose the main language of the catalog, which will be used as the default language when entering or editing content.

Turn a field into a multi-language field
If you want a field to store content in multiple languages, go to Redesign Forms, open the Modify option for that field, and enable the multi-language option if the field type supports it.
Once enabled, the languages configured in your account will appear in that field so you can enter content for each one. This setup is useful for fields such as product names or descriptions when the same product needs localized content for different audiences.

Edit field labels by language
In addition to translating field content, you can also make the field names themselves multi-language. To do this, go to Redesign Forms > Modify for the field and click the grey icon next to the field name. This lets you define a different label for each language.
This can be especially useful when several teams in different countries use the same account, because each user can see the field labels in the language that fits their work better.
[Screenshot placeholder: Field configuration screen showing the grey icon next to the field name and the translated field labels for multiple languages.]
Use multi-language content in exports
Multi-language setup also affects how content is exported through Channels. When exporting, you can choose not only which languages to include in the output, but also the language used for the column titles.
This helps when the exported file needs to be shared with teams, partners, or systems that work in a specific language.

Common Use Cases
Manage one catalog for several countries or regions.
Store translated versions of product names and descriptions in the same field.
Show translated field labels to users working in different languages.
Export content in selected languages for external channels or teams.
Best practices
Before adding more languages, decide which fields really need translation and which can stay in one language. Keep the main language of the catalog clearly defined, and use consistent naming for local variants so your team always knows which version they are editing or exporting.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article