---
title: "Localization"
slug: "localization-1"
updated: 2024-11-08T18:44:07Z
published: 2024-11-08T18:44:07Z
canonical: "docs.zilliant.com/localization-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zilliant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Localization

eCommerce allows localization for the following languages:

| Locale | Locale key |
| --- | --- |
| English | en |
| German | de |
| Chinese | zh |

The eCommerce application checks a user’s locale to display the corresponding language. If your eCommerce configuration doesn’t support the user’s locale, the eCommerce application will display English by default.

For elements of the eCommerce application that aren’t managed in eCommerce, maintain localization through [Zilliant CPQ](/v1/docs/about-cpq).

          Before you continue

          

There are differences when maintaining locale files for eCommerce and for Zilliant CPQ. This topic covers how to maintain localization only for eCommerce.

## Maintain custom locale files

The directory structure for locale files is mapped to how the Zilliant system retrieves files, then implements them in the eCommerce application. When managing locale files, maintain the directory structure. To update a locale, contact your Zilliant representative for a `translation.json` file and perform the following steps.

To maintain custom locale files in Zilliant CPQ:

1. From the left navigation area, select **Administration**.
2. From the top navigation bar, select **Content Management**.
          Tip

          

If you don't see this menu item, select Open dropdown menu at the right end of the navigation bar, or select the left and right arrows to move through the navigation bar.
3. Select **userdata** > **attachment** > **PortalSettings**.
4. Select locales. All locale files are maintained in this folder, with subfolders for each language.
          Note

          

If your system is new, create a locales directory with the following structure: `/locales/<localeKey>/translation.json` Replace `<localeKey>` with the relevant locale key.

Always validate if there are any markup errors.

![CPQ-icon_down](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/CPQ-icon_down.png?sv=2026-02-06&spr=https&st=2026-11-10T17%3A05%3A09Z&se=2026-11-10T18%3A05%3A09Z&sr=c&sp=r&sig=aDnJykXVHl4TM8rSUwAVwSHQnQvCIC0QlIEqZmmLDxk%3D) Open dropdown menu