In-app multi-language translations in PIM
Optimizely Product Information Management (PIM) can display translated content for customers. Selecting a non-default language on properties, categories, assets, and products exposes the translatable fields.
Edit properties for multiple languages
When you flag properties as multi-language, the PIM shows any translated display names or list of values you provide.
Translate display names
When editing a property record, you can enter the Display Name for properties in each language.
- Go to Data Setup > Properties and click the multi-language property for which you want to add display names.
- Use the language dropdown menu to select the desired enabled language.
- Enter the display name for the selected language.
Selecting a non-default language hides all fields other than the Display Name. The default language Display Name is displayed on the left, and the selected language Display Name is displayed on the right.
Translate property values
With a non-default language selected on the Values tab, you can enter translations directly in the list.
- Go to Data Setup > Properties.
- Click the property name for which you want to add a translation.
- Click the Values tab.
- Select a non-default language from the dropdown menu.
- Enter translations for the values that are displayed on the list.
- Click Save.
Note
When you translate property values, any published products with the translated value are updated to approved. The translation updates in Commerce the next time products are published.
Edit categories for multiple languages
Almost all category data is customer-facing and can be translated. Optimizely hides the image selections, activation and deactivation dates, and a toggle option for dynamic recommendations to focus on the translatable fields when editing a category with a non-default language.
- Go to Categories and click the category name you want to edit.
- Select a non-default language from the drop-down menu.
- Enter translations for any of the multi-language fields.
- Click Save.
Edit assets for multiple languages
Only alt text of images can be translated for assets because no other data is customer-facing. Selecting a non-default language on the asset list automatically filters out other asset types to only show images.
- Go to Assets and click the product number you want to edit.
- Select a non-default language from the dropdown menu.
- Enter translations for the alt text field.
- Click Save.
Edit products for multiple languages
Selecting a non-default language on the product record hides properties not marked as multi-language and displays both an input for the selected language and the default language value. Property values are hidden because they are translated on the property record. The translated value is automatically used based on the value for the default language.
- Go to Products and click the product number you want to edit.
- Select a non-default language from the dropdown menu.
- Enter translations for any of the multi-language properties.
- Click Save.
A message warns about missing translations if any text field, text area, or HTML property is flagged as multi-language but does not have data for a secondary language. A warning icon also appears in the language dropdown if at least one property is missing a translation.
Complete multi-language properties and products
Product completeness depends on how properties are marked in Settings > Multi-language Options.
For example, English (EN) is the default language, and French (FR) is an enabled secondary language.
If FR is set to:
- None – Products can be published to Commerce without FR translations.
- Required Properties – Products cannot be published without FR translations for required properties.
- Required & Recommended – Products cannot be published unless they have FR translations for required properties and recommended properties with data in EN.
- All Properties – Products cannot be published unless they have data in FR for all properties with data in EN.
The following flows provide details about multi-language property evaluation for completeness, followed by examples of complete and incomplete products.
Evaluation of required multi-language properties for completeness
- Does the property have default language data?
- No – Property is incomplete.
- Yes – Are there languages with a setting other than None?
- No – Property is complete.
- Yes – Are there languages missing data for this property?
- No – Property is complete.
- Yes – Property is incomplete.
Evaluation of recommended multi-language properties for completeness
- Does the property have default language data?
- No – Property is not factored into completeness.
- Yes – Are there languages with All Properties or Req + Rec settings?
- No – Property is not factored into completeness.
- Yes – Are there languages missing data for this property?
- No – Property is not factored into completeness.
- Yes – Property is complete.
Evaluation of optional multi-language properties for completeness
- Does the property have default language data?
- No – Property is not factored into completeness.
- Yes – Are there languages with All Properties setting?
- No – Property is not factored into completeness.
- Yes – Are there languages missing data for this property?
- No – Property is incomplete.
- Yes – Property is complete.
Complete product example
Incomplete product example
