> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/store-operations/orders/fulfillment/troubleshooting/change-language.md).

# Change Language

The language switching feature in the HotWax Commerce platform is designed to enhance user accessibility and comfort by allowing users to operate the interface in their native or preferred language. This feature is particularly significant for a global user base, ensuring that language barriers do not hinder the efficient use of the platform.

### Steps to Follow

**Step 1: Navigate to Launchpad**

* [Launchpad](https://launchpad.hotwax.io/)

**Step 2: Open Any App**

* Access any of the apps, such as the Fulfillment App.

**Step 3: Go to Settings Page**

* The settings page contains various customization options, Scroll Down to Find the Language Section.

**Step 4: Choose Your Language from the Dropdown Menu**

* Select your desired language to update the interface language.

By following these steps, users can ensure that their interaction with the HotWax Commerce platform is seamless and tailored to their linguistic preferences.


---

# 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.hotwax.co/documents/store-operations/orders/fulfillment/troubleshooting/change-language.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.
