> 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 Locales**. Each market locale is a rule that auto-detects a visitor's locale and applies a matched language, currency, and [profile](/product/using-peakcommerce/market-profiles.md):

1. Define a **locale pattern** (for example `en-US`, `fr-*`) that the rule matches against the visitor.
2. Set the **currency** and **language** that pattern should resolve to.
3. Optionally bind a **profile** so matched visitors also get the right theming and configuration.
4. Order rules by **priority** and mark one as the **default** fallback for unmatched visitors.

When a visitor arrives, the highest-priority active rule whose pattern matches wins, and the page renders in that language and currency.

## Key concepts

* **Rules, not per-page translation files.** You localize by configuring Market Locales centrally; the page surfaces the matched locale 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 matched locale.
* **A default is your safety net.** The default rule catches visitors no specific pattern matches, so there's never a blank or untranslated experience.

## Gotchas

* A market locale only applies if it's **active** — an inactive rule is skipped even when its pattern would match.
* Priority breaks ties; if two patterns overlap (for example `fr-*` and `fr-CA`), the higher-priority rule wins, so order them most-specific-first.
* Always keep exactly one **default** rule so unmatched locales still resolve a currency and language.

See [Market Locales](/product/using-peakcommerce/market-profiles.md) to configure locale rules.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/using-peakcommerce/ecommerce-and-payment-pages/translating-e-commerce-pages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.