> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/core-commerce/data-localization.md).

# Data Localization

Data localization allows you to reach the international customers.

## Purpose

The localization concept in the Emporix e-commerce system helps you adapt your business's content to international audiences.

## Localizable data

Resources that can be localized are described in their respective sections.

### Countries

Countries where your business operates are stored in country configurations.

{% hint style="info" %}
For more information on managing country configurations, check out the [Country Service guide](/api-documentation/api-guides/configuration/country-service/country.md).
{% endhint %}

### Currencies

Currencies accepted by your business are stored in currency configurations. You can specify the default currencies for particular sites as well as the whole tenant.

{% hint style="info" %}
For more information on managing currency configurations, check out the [Currency Service guide](/api-documentation/api-guides/configuration/currency-service/currency.md).
{% endhint %}

You can also define static exchange rates for currencies and calculate product prices based on these rates.

{% hint style="info" %}
For more information on currencies and exchange rates, check out the [Pricing guide](/api-documentation/api-guides/prices-and-taxes/price-service/price.md).
{% endhint %}

### Dates and times

Dates and times are stored as instantaneous moments in the UTC timezone.

{% hint style="warning" %}
To localize dates and times for your customers, you need to configure the UTC offset on your storefront.
{% endhint %}

### Languages

While the Emporix e-commerce system is designed in English, you can specify languages in which your business communicates with suppliers and customers through language configurations. You can specify the default languages for particular sites as well as the whole tenant.

{% hint style="info" %}
For more information on managing language configurations, check out the [Language Configuration guide](/api-documentation/api-guides/configuration/configuration-service/language.md).
{% endhint %}

### Measurement units

The Emporix e-commerce system supports all types of measurement units and measurement systems.

{% hint style="info" %}
For more information on measurement units, check out the [Measurement units guide](/api-documentation/api-guides/configuration/unit-handling-service/unit-handling.md).
{% endhint %}

You can further localize measurement units by translating their names to different languages.

### Names and descriptions

You can localize information-rich text fields — such as names or descriptions — by translating them into languages of your choice.

{% hint style="info" %}
For information on localizing object names and descriptions, check out the *Translations* section in the [Standard practices guide](/api-documentation/standard-practices/general-info.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/user-guides/core-commerce/data-localization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.