> 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/market-profiles.md).

# Market Locales

**Market Locales** let you sell globally without friction by auto-detecting each visitor's **currency, language, and profile** from their locale — so shoppers see a familiar, localized experience the moment they arrive, while still being free to change currency at checkout.

## Why it matters

* **For shoppers** — prices in their local currency and content in their language from the first screen, which builds trust and reduces cart abandonment.
* **For businesses** — define locale rules once and reuse them across regions, sites, and surfaces; align currency, language, and which profile applies per market.
* **For international growth** — smoother checkouts and stronger conversion across markets, with no per-site custom code.

## How it works

Configure ordered **locale rules** in **Commerce → Market Locales**. Each rule matches a locale pattern and applies a currency, language, and (optionally) a profile. When a customer arrives on a public page or journey, PeakCommerce detects their locale, applies the best-matching rule, and formats prices accordingly. If no rule matches, your **default** locale applies. Shoppers can override the detected currency at checkout, and their choice is remembered.

See [Auto-detecting currency, language & profile](/product/using-peakcommerce/market-profiles/automatic-detection-of-user-location-currency.md) to set up rules, and [Products & bundles](/product/using-peakcommerce/products-and-bundles/products-overview.md) for how localized prices reach your [payment pages](/product/using-peakcommerce/ecommerce-and-payment-pages.md).


---

# 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/market-profiles.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.