> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-1/menu-item.md).
# Menu Item
A **Menu Item** is used to define and manage items that will be displayed in a menu structure. It helps in linking existing items to a menu so they can be used for ordering, billing, or display purposes in the system.
### Steps to Create a Menu Item
1. Navigate to the **Point of Sale** module and select **Masters1**.
* Click on **Menu Item.**
* The Menu Item screen will appear.
2\. Click on the **New** button to create a new Menu Item.
3\. Click on the **Search Icon.**
* Select the required **Item Name** from the list.
* This links the menu item with an existing item in the system.
4\. After selecting the item, click on the **Save** button.
* The Menu Item will be created successfully.
5\. Click on **Bulk Update.**
* A new screen will appear.
6\. Choose the required **Product Group.**
* Click on the **Display** button.
* The system will show all items under the selected group.
7\. Make the required changes in bulk for menu items.
* After updating, click on the **Save** button.
* All changes will be saved successfully.
---
# 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://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-1/menu-item.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.
