> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/ecommerce-and-payment-pages/translating-e-commerce-pages.md).

# Localizing Pages

Selling across markets means serving the right language *and* the right currency to each visitor. PeakCommerce localizes the buying experience by **language and currency** so you don't script translations by hand or maintain a separate storefront per region — one set of pages adapts to whoever lands on it.

## How it works

Localization is driven by [Market Studio](/product/using-peakcommerce/market-studio.md). A visitor's **currency selects their market** (each market sells in exactly one currency), and the market's [Who gets what](/product/using-peakcommerce/market-studio/who-gets-what.md) sentences decide the rest:

1. The visitor's currency — from their entry link (for example `?currency=CAD`) or detected from their locale — places them in a market.
2. The market's ordered sentences assign **language** and, optionally, a **profile** (theming and configuration), matching on locale patterns (`fr-*`) or [audiences](https://gitlab.com/peakcommerce/peak-help-docs/-/tree/main/product/rules-and-customizations/README.md).
3. The **Otherwise** line fills anything the sentences left blank, so every visitor resolves a complete experience.

The page then renders in that language and currency.

## Key concepts

* **Sentences, not per-page translation files.** You localize centrally in Market Studio; the page surfaces the matched language and currency at render time.
* **Page copy is component-driven.** Because pages are built from [components](/product/using-peakcommerce/templates.md), localized copy and per-market variants are managed in those components and shown according to the resolved market.
* **Otherwise is your safety net.** It catches visitors no sentence matches, so there's never a blank or untranslated experience.

## Gotchas

* Sentences read **top to bottom** — the first line with an opinion about a facet decides it, so order them most-specific-first.
* A currency a visitor explicitly arrived with is **authoritative**: sentences fill in the open facets but never switch the visitor's currency.
* A currency no market serves is a **reported gap** — the visitor is offered the currencies you do sell in, never silently charged in another one.

See [Market Studio](/product/using-peakcommerce/market-studio.md) to configure markets and sentences.


---

# 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://docs.peakcommerce.com/product/using-peakcommerce/ecommerce-and-payment-pages/translating-e-commerce-pages.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.