> 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-sub-group-2.md).
# Item Sub Group 2
**Item Sub Group 2** is a further level of item classification used to divide items under an **Item Group** and **Item Sub Group 1**. It helps in creating a more detailed hierarchy for better organization, reporting, and item selection in the system.
### Steps to Create Item Sub Group 2
1\. Navigate to the **Point of Sale** module and select **Masters1**.
* Click on **Item Sub Group 2.**
* The Item Sub Group 2 screen will appear.
2.Click on the **New** button to start creating a new Item Sub Group 2.
3.Choose the **Item Group Name** from the available list.
* This links the entry to the main item category.
4\. Select the relevant **Item Sub Group 1** under which Item Sub Group 2 will be created
* This ensures proper hierarchy and classification.
5\. After selecting all required details, click on the **Save** button.
* The system will successfully create and store the Item Sub Group 2.
---
# 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-sub-group-2.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.
