In the Xperience E-commerce Solution, you can translate various e-commerce objects when running a multilingual store. Learn how to enter different content for different languages. There are three different approaches when maintaining multilingual stores:
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.
This section describes translation of products created in the default way (i.e. an SKU linked with a page). Products stored as stand-alone SKUs need to be translated as multilingual texts with resource strings.
To translate the names and descriptions of product options or product variants, you need to use resource strings and the approach described in the Maintaining other multilingual e-commerce data section.
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.
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.
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.
Get more information about language versions in Language status overview.
If you edit a non-translated product, the system offers several options:
After you click Create page, you are ready to edit the page.
Learn more information about comparing two language versions in Comparing language versions.
Workflow 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.
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:
The name of the discount is now displayed differently according to user's current language.
Similarly you can localize other e-commerce data.
See more information about multilingual display names and descriptions in Localizing text fields.
For editing content of longer texts, typically invoices or emails, you can use resource strings. The following example edits an email notification.
To create a resource string, open the Localization application.
On the Resource string tab, click New string.
Type a key in the Key field. For example, custom.Hello.
Type variants to desired languages, for example Hello in the English field and Hola in the Spanish field.
Click Save to save the resource string.
Open the Email templates application.
Click Edit () to modify a specific notification.
In the HTML version or Plain text version field, type the resource string in the following format:
{$custom.Hello$}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.
Learn more information about resource strings in Working with resource strings.