> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-advanced-pos-user-interface-html-pos/enabling-the-advanced-pos-user-interface.md).
# Enabling the Advanced POS User Interface
Enabling the Advanced POS User Interface (UI) is pretty straightforward. This article describes the procedure in detail.
***
### Before you begin
Before enabling the Advanced POS UI, make sure that all your POS workstations already work in Legacy mode.
### Enable the Advanced POS UI
1. Logon to the Maitre’D Back-Office with appropriate credentials. (Distributor or System Owner)
2. Start the Point of Sale Control module.
3. Click on the View menu and select the Options... option.
4. The Point of Sale Control module's options window opens on the Configuration branch.
5. Click on the POS sub-branch and enable the Use advanced POS UI option.
6. Click OK. You will be asked to create the workstation data. Click OK to proceed. The entire process could take from a few seconds to a few minutes, depending on your system's performance and the number of workstations on your Maitre'D license.
7. The options window will close, and you will be back to the Point of Sale Control module.
At this point, the POS workstations should automatically restart with the Advanced POS User Interface.
**Legacy POS User Interface**
**Advanced POS User Interface**
---
# 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.maitredpos.com/maitred/maitred-advanced-pos-user-interface-html-pos/enabling-the-advanced-pos-user-interface.md?ask=&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.
