> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/1.7-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/1.7-documentation/french/guide-utilisateur/optimiser-boutique/internationalisation.md).

# Gérer la localisation et l'internationalisation

Aussi évident que cela puisse paraître, vous vendez sur Internet, et vos clients qui viennent du monde entier peuvent se rendre sur votre boutique et acheter vos produits. En tant que vendeur, vous devez pouvoir servir autant de clients que possible. Cela signifie disposer d'une site totalement traduit dans autant de langues que nécessaires, avec les taxes locales, les unités de poids et de prix, les zones locales géographiques, etc.

Ce chapitre contient les sections suivantes :

* [Localisation](/1.7-documentation/french/guide-utilisateur/optimiser-boutique/internationalisation/localisation.md)
* [Zones géographiques](/1.7-documentation/french/guide-utilisateur/optimiser-boutique/internationalisation/zones-geographiques.md)
* [Gérer les taxes](/1.7-documentation/french/guide-utilisateur/optimiser-boutique/internationalisation/gerer-taxes.md)
* [Traductions](/1.7-documentation/french/guide-utilisateur/optimiser-boutique/internationalisation/traductions.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 by asking a question.

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

```
GET https://docs.prestashop-project.org/1.7-documentation/french/guide-utilisateur/optimiser-boutique/internationalisation.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.