The translations page allows you to translate your quote model. Translations can be done directly in the Quote Designer interface or they can be managed with an Excel file that is exported, translated, then imported.

The left pane contains all categories available for translation. The translated text is entered in the window on the right.

Translations can be managed outside of the application using the import/export function. This allows you so export all terms that need to be translated to an Excel file. The file can then be translated outside of the application, then imported.

The Excel file contains one tab per locale (defined in Settings, display locale) and 4 columns:

• Type - type of element to translate
• Name - name of the element to translate
• Source Locale - locale used in the application as Quote Display Locale
• Destination Locale - the translated text to be stored

In order to be able to import translations, the same format must used.

The left pane allows you to navigate between categories. Select the destination locale and enter the translation for this locale.

The elements to translate might be simple text fields. In that case, you can modify text boxes directly:

Or it can be properties of elements like columns or fields. In that case, you have to expand the panel below the element to access the translations of its properties:

For all translations related to the software aka System Translations including user interface system actions labels and application error messages, Smart CPQ comes standard Out-of-the-box translations in the following languages:

English (EN), French (FR), Spanish (ES), German (DE), Italian (IT), Portuguese (PT), Chinese (ZH) and Polish (PL).

Translations are applied based on the Display Locale configured in your quote model within the

Quote Designer.

All locales that begin with the language codes EN, FR, ES, DE, IT, PT, ZH or PL are supported out of the box (OOB). If the selected locale does not match any supported language, the system will use the fallback language defined in your quote model.

If you encounter issues with OOB translations, raise a Support Ticket. If a required locale is missing, submit a UserVoice request to have it added.

TRANSITIONING FROM CUSTOM TO OOB TRANSLATIONS

To enable out-of-the-box translations, you must submit a Support Ticket. Important: Only one translation method can be active at a time. When switching to OOB translations, any existing custom translations will no longer be available.

Customers currently using custom translations will continue to have them honored.