Online store translation management

Online store translations are maintained in several different views. The correct place depends on whether it is general user interface text, product information, status, payment method, or CMS content.

The default language texts are also translated texts. Therefore, this guide can also be used in a single-language store.

Note: You can browse texts in the Translations editing view in the control panel, but the writing endpoint is not enabled. Adding, changing, deleting text, and the Auto-translate function are not saved from this view. Use a functional object-specific editing view or export the missing writing feature for further development.

Choose the right place to edit your online store translations

The correct place to edit online store translations depends on the intended use of the text. General user interface texts are browsed centrally, but language versions of products, categories, modes, and content belong to their own registers. Use the following division:

• General store UI texts, email texts and PDF texts: Editing translations in the /cms/translations path. The view in the control panel is for browsing only.
• Categories: Categories in the path /categories .
• Products: Products on the path /products .
• Attributes and other shared product information: the specific Translations section of the registry in question.
• Request for quotation statuses: Request for quotation statuses in the path /quotes/statuses .
• Payment methods: Payments via the route /configuration/payment .
• Shipping methods: Shipping methods in the /configuration/shipment path.
• Order statuses: Order statuses at /orders/statuses .
• Reviews: Reviews on the route /reviews .
• FAQ content: FAQ categories and FAQ questions in FAQ views.
• Gallery: Gallery at /cms/gallery .
• Custom navigation and footer: /cms/custom-navigation and /cms/custom-footer .
• CMS pages: CMS → Content in the path /cms/content .

Edit content hosted in an external content management system in that system. Content created in WordPress or Builder.io will not be transferred to the general text register in the Control Panel for translation.

Browse common translation texts

General online store translation texts are browsed by page and language in the Edit Translations view:

1. Open Translation Editor .
2. Select Page .
3. Select Language .
4. Check the Key and Value in the table.
5. Use the page's own search to find the correct text. For a long list, you can use the browser's search function with the key combination Ctrl+F or Command+F .

The texts are grouped by purpose. Groups can include, for example, cash register, product information, product listing, and general texts for the entire store. The text of an email or PDF is most reliably found by searching for a short, precise snippet of the text.

Don't infer the usage based on the key name alone. Always check the change in the store view, email, or PDF file where the text appears.

Edit category and product texts

Categories

Open Categories , select a category, and edit its localized names, descriptions, URL parts, and SEO information in the category's own view. The category's UI tells you which fields are translations. Check each language used in your store separately and keep the structure of URL parts consistent. Category text should not be looked up in the general text register if it is stored directly in the category data.

Production

Open Products , select a product, and use the Translations section of the product's localized fields. Product-specific names, descriptions, SEO texts, and other language versions are part of the product data.

Common concepts across products are not modified by a single product. Open their own register, for example:

• Attributes in the path /catalog/attributes
• Product bubbles on the route /products/bubbles
• Tags in the path /products/tags
• Manufacturers on the route /manufacturers

If the same term appears on multiple products, first check whether it comes from such a shared registry.

Edit spaces and editorial texts

Translations of online store status, payment and delivery texts are maintained in their own registers:

1. Open the right view: Request for quotation statuses , Payments , Shipping methods , or Order statuses .
2. Open the record you want to edit.
3. Edit its language versions in the Translations section of the view.
4. Check the text in the store in the situation where the mode or method in question appears.

General user interface texts such as the order total may not be included in the payment or order status register. They can be found in the general translation texts section.

Edit contents

FAQ and gallery

The FAQ categories and FAQ questions in the online store have their own localized names, descriptions, answers, URL parts, and SEO information. Edit the question and answer in the same language and check that the question belongs to the correct FAQ category. The language versions of the gallery albums and galleries are edited in the Gallery view. Check the album and gallery name and the localized texts associated with the images. Existing gallery records are saved when changing or leaving the field.

Navigation, footer and CMS pages

Edit the store navigation in the Custom Navigation view and the footer in the Custom Footer view. CMS pages and their language versions belong to the CMS → Contents view.

The text displayed on the homepage can come from a banner ad, FAQ, custom navigation, footer, or CMS page. First, identify the content type that produces the text and edit it in the corresponding view.

In the navigation, also check the link target and language-specific URL. In the footer, ensure the language versions of the headings, link texts and content blocks. On the CMS page, in addition to the visible text, check the page name, URL part and SEO information when they are editable.

Enable automatic translation for the language

Language-specific settings for automatic translation are located in the Automatic Translation tab of the AI Automations view, at /ai-automations .

1. Open AI Automations .
2. Select Automatic translation .
3. Enable automatic translation for desired target languages.
4. Leave the store's default language as is. You cannot turn automatic translation of the default language on or off from this setting.

Automatic translation only handles empty target language values when the source text exists. If an existing translation needs to be rebuilt, clear the target language value only in an editing view where saving works, and make sure that the original text is saved before clearing.

The translation service is selected in the environment settings. The system can use OpenAI, DeepL, or Google Translate. The view also shows the usage of characters per month and a possible usage limit. Do not promise a specific completion time: the background run schedule depends on the environment's timing and the size of the queue being processed.

If the translation service fails, check the error before trying again. Failure does not guarantee that the original text will be saved in the target language.

Update store translation cache

The online store's translation cache needs to be updated if a translation made in a working edit view is not yet visible in the store:

1. Open the Control Panel maintenance functions.
2. Select Reload translations .
3. Wait for the success notification.
4. Refresh the store page in your browser.

This function reloads translations into the store's cache. It is only available in a multilingual store.

If you see a success message but the old text remains on the page, perform a normal browser refresh and reopen the same application. Also, make sure you are viewing the correct store and language. Reloading the cache will not fix text stored in the wrong content type or language.

Check the change

Always check at least the following:

• the right language and the right trade
• correct content type or register
• the appearance of the text in the actual use case of the store
• in emails and PDF files, also the final formed message or file
• that the change did not break placeholders, HTML structure, or links

First translate the paths that the store actually uses. This way, missing texts and incorrect language versions will be found more easily than trying to fill in all the registers at once.

If text is not found

If the online store translation text is not found in the expected view, first narrow down its actual use:

1. Copy a short and unique excerpt from the text.
2. Search for it in the Translation Editing view with multiple page selections.
3. Check if the text is native content for the product, category, status, payment method, shipping method, FAQ, gallery, or CMS.
4. Check if the text is generated by external WordPress or Builder.io content.
5. If the Control Panel does not have a working writing view, file the missing feature for further development and do not try to work around it via the browser.