---
title: Maintaining multilingual stores
related:
  - https://docs.kentico.com/13/e-commerce-features/configuring-on-line-stores/configuring-multilingual-stores.md
  - https://docs.kentico.com/13/multilingual-websites.md
  - https://docs.kentico.com/13/multilingual-websites/editing-the-content-of-multilingual-websites.md
  - https://docs.kentico.com/13/multilingual-websites/editing-the-content-of-multilingual-websites/language-status-overview.md
  - https://docs.kentico.com/13/multilingual-websites/setting-up-a-multilingual-user-interface/working-with-resource-strings.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

In the Xperience E-commerce Solution, you can translate various e-commerce objects when running a [multilingual store](https://docs.kentico.com/13/e-commerce-features/configuring-on-line-stores/configuring-multilingual-stores.md). Learn how to enter different content for different languages. There are three different approaches when maintaining multilingual stores:

- [Maintaining multilingual products and their details](#maintaining-multilingual-products)
- [Maintaining other multilingual e-commerce data](#maintaining-other-multilingual-e-commerce-data)
- [Maintaining multilingual texts, such as e-commerce notifications or invoices](#maintaining-multilingual-texts)

> **Info:** You can see the interface for multilingual stores only when your store is configured to use multiple cultures (languages). See more in [Configuring multilingual stores](https://docs.kentico.com/13/e-commerce-features/configuring-on-line-stores/configuring-multilingual-stores.md).

## Maintaining multilingual products

> **Info:** This section describes translation of [products](https://docs.kentico.com/13/e-commerce-features/managing-on-line-stores/products.md) created in the default way (i.e. an SKU linked with a page). Products stored as [stand-alone SKUs](https://docs.kentico.com/13/e-commerce-features/managing-on-line-stores/products/managing-stand-alone-skus.md) need to be translated as [multilingual texts with resource strings](#maintaining-multilingual-texts).
>
> To translate the names and descriptions of [product options](https://docs.kentico.com/13/e-commerce-features/managing-on-line-stores/products/working-with-product-options.md) or [product variants](https://docs.kentico.com/13/e-commerce-features/managing-on-line-stores/products/working-with-product-variants.md), you need to use resource strings and the approach described in the [Maintaining other multilingual e-commerce data](#maintaining-other-multilingual-e-commerce-data) section.

### Getting familiar with the multilingual product interface

You can translate products either from the **Products** application or from the **Pages** application. In both applications, you can see a selector with which you can switch languages.

![Products language selector](https://docs.kentico.com/docsassets/13/maintaining-multilingual-stores/products_language_selector.png "Products language selector")

You can recognize translated and not translated products simply by looking at the product tree. The translated products are labeled with a green tick (), the not translated products are labeled with an _A_ character in a frame.

![Icons of translated and not translated products](https://docs.kentico.com/docsassets/13/maintaining-multilingual-stores/translated_products_icons.png "Icons of translated and not translated products")

You can also see the translation status of a specific item by looking at the **Languages** column in the product listing. If you hover your mouse over a specific culture icon, additional information appears.

![Language variants of products](https://docs.kentico.com/docsassets/13/maintaining-multilingual-stores/product_language_variants.png "Language variants of products")

> **Tip:** Get more information about language versions in [Language status overview](https://docs.kentico.com/13/multilingual-websites/editing-the-content-of-multilingual-websites/language-status-overview.md).

### Translating products

If you edit a non-translated product, the system offers several options:

- _Create an empty page_ – creates a new page of the same type, but without any content.
- _Copy content from another language_ – creates a copy of the page with content loaded from the selected language version. If you select the _Save the new page before editing_, the system adds the new page version and immediately saves the copied content.
- _Translate using translation service_ – the content of the page will be provided by an external translation service. The translation service needs to be [configured](https://docs.kentico.com/13/multilingual-websites/configuring-translation-services.md) first.

After you click **Create page**, you are ready to edit the page.

> **Tip:** Learn more information about comparing two language versions in [Comparing language versions](https://docs.kentico.com/13/multilingual-websites/editing-the-content-of-multilingual-websites/comparing-language-versions.md).

### Editing multilingual products under workflow

[Workflow](https://docs.kentico.com/13/configuring-xperience/configuring-the-environment-for-content-editors/configuring-workflows.md) is a sequence of steps that define the life cycle of pages and products. It allows you to set up a reviewing and approval process to ensure the quality of content.

Workflow covers product properties in the **General** section (with some exceptions) and overall page settings. If your multilingual products are under workflow, the product properties are **NOT shared between different language versions** of a single product. Any updates of the product **Price** (or other key properties) need to be made separately for each language version. Alternatively, your developers can set up some form of automatic synchronization mechanism.

## Maintaining other multilingual e-commerce data

The **Display name** and **Description** fields in the administration interface of all e-commerce data provide a user-friendly way to handle localization.

For example, if you want to localize the name of a specific [Buy X Get Y discount](https://docs.kentico.com/13/e-commerce-features/managing-on-line-stores/discounts/working-with-buy-x-get-y-discounts.md):

1. Open the **Buy X Get Y discounts** application.
2. **Edit** () a Buy X Get Y discount.
3. Click to the **Name** field.
4. Click **Localize** (**+**) in the grey square that just appeared.

   ![Localizing a discount name](https://docs.kentico.com/docsassets/13/maintaining-multilingual-stores/localizing_discount_name.png "Localizing a discount name")
   - The **Localize field** dialog opens.
5. Leave the default _Create new resource string_ option.
   - If you prepared a resource string beforehand, select _Use existing resource key_ and select the key.
6. Click **Save & Close**.
   - The **Localize string** dialog opens.
7. In the dialog, all activated languages are displayed and you can type the translation for every language.

   ![Localizing a string](https://docs.kentico.com/docsassets/13/maintaining-multilingual-stores/localizing_string.png "Localizing a string")
8. Click **Save & Close**.
   - The dialog closes and a planet icon appears in the field.

     ![The planet icon](https://docs.kentico.com/docsassets/13/maintaining-multilingual-stores/planet_icon.png "The planet icon")
9. Click **Save** to save the discount.

The name of the discount is now displayed differently according to user's current language.

Similarly you can localize other e-commerce data.

> **Tip:** See more information about multilingual display names and descriptions in [Localizing text fields](https://docs.kentico.com/13/multilingual-websites/setting-up-a-multilingual-user-interface/localizing-text-fields.md).

## Maintaining multilingual texts

For editing content of longer texts, typically [invoices](https://docs.kentico.com/13/e-commerce-features/configuring-on-line-stores/configuring-invoices.md) or [emails](https://docs.kentico.com/13/e-commerce-features/configuring-on-line-stores/configuring-e-commerce-email-notifications.md), you can use resource strings. The following example edits an email notification.

1. To create a resource string, open the **Localization** application.
2. On the **Resource string** tab, click **New string**.
3. Type a key in the **Key** field. For example, _custom.Hello_.
4. Type variants to desired languages, for example _Hello_ in the **English** field and _Hola_ in the **Spanish** field.

   ![Creating a resource string](https://docs.kentico.com/docsassets/13/maintaining-multilingual-stores/creating_resource_string.png "Creating a resource string")
5. Click **Save** to save the resource string.
6. Open the **Email templates** application.
7. Click **Edit** () to modify a specific notification.
8. In the **HTML version** or **Plain text version** field, type the resource string in the following format:

   ```csharp

   {$custom.Hello$}

   ```
9. Click **Save** to save the email template.

The notification now sends emails with _hello_ in English or Spanish, according to the current user's settings. You can set similarly also other texts.

> **Tip:** Learn more information about resource strings in [Working with resource strings](https://docs.kentico.com/13/multilingual-websites/setting-up-a-multilingual-user-interface/working-with-resource-strings.md).