> 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-complete-online-documentation/chap-4-point-of-sale-control/introduction-to-the-point-of-sale-control/navigating-the-point-of-sale-control-module.md).

# Navigating the Point of Sale Control module

All Maitre'D modules share the same general layout allowing users to quickly navigate through the modules. A menu bar in the top part of the window displays all the tasks and functions that can be performed using the POS Control module. The center pane is divided into two parts. The right hand side contains the same icons as the Maitre'D Back-Office main screen and allows users to open another module directly from the Point of Sale Control module. The left hand side contains a series of links to the most common tasks performed using the Point of Sale Control.

![Point of Sale Control Module Navigation](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/POSControl/POSControlNavigation.png)


---

# 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-complete-online-documentation/chap-4-point-of-sale-control/introduction-to-the-point-of-sale-control/navigating-the-point-of-sale-control-module.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.