> 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/item-group.md).
# Item Group
An **Item Group** is a master classification used to organize items into main categories. It helps in grouping similar items together for better management, reporting, and easy selection while creating items in the system.
### Steps to Create Item Group
1\. Navigate to the **Point of Sale** module and select **Masters1**.
* Click on **Item Group**
* The Item Group screen will appear
2.Click on the **New**button to create a new Item Group.
3\. Enter the **Item Group Name** in the provided field.
* The name should clearly represent the category of items it will include.
4\. Choose the appropriate **Tax Structure** from the available list.
* The tax structure defines the tax rules applicable to all items under this group.
5\. After entering all required details, click on the **Save** button.
* The system will create and store the new Item Group 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/item-group.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.
