> 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/online-ordering/online-ordering/inventory/menu-display.md).

# Menu display

![](https://s3.amazonaws.com/helpjuice-static/helpjuice_production%2Fuploads%2Fupload%2Fimage%2F8237%2Fdirect%2F1611150783920-IMG_Catogire-AN.png)

The menu display is a tool for changing the order and visibility of categories and products constituting a menu.

{% embed url="<https://youtu.be/25kOmCSsZTQ>" %}

### Reach menu display

1. Click on the branch to which you want to apply changes.
2. In the inventory section of the navigation bar, go to ***Menu Display***.
3. Then click on the ***Online*** catalog. This catalog contains your online ordering menu.

### Change the menu display

{% embed url="<https://s3.amazonaws.com/helpjuice-static/helpjuice_production%2Fuploads%2Fupload%2Fimage%2F8237%2Fdirect%2F1611150819562-VDO_Affichage-AN.mp4>" %}

1. Click on the desired category and, while keeping the mouse button pressed, drag the category to the desired location.
2. Open a category by clicking on it.
3. To make a product invisible, uncheck this product. Note that categories with no visible product will not be displayed on your online menu.
4. To move a product, click on the desired product and, while keeping the mouse button pressed, drag the product to the desired location in its category.
5. Click on ***Save*** when you're done with your changes.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maitredpos.com/online-ordering/online-ordering/inventory/menu-display.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 `build a script that syncs our docs to a CMS` 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.