> 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-3/item-sub-group-3.md).
# Item Sub Group 3
The **Item Sub Group 3** feature is used to create a third level of item categorization in the system. It helps in further classifying items under Item Group, Item Sub Group 1, and Item Sub Group 2 for better organization and easy management of items.
### Steps to Create and View Item Sub Group 3
Step 1: Navigate to the **Point of Sale** module.
1. Go to **Master3 > Item Sub Group 3**.
* The Item Sub Group 3 screen will appear.
Step 2: Click on the **Add** button to create a new entry.
Step 3: Select the required **Item Group** from the available list.
* This is the main category under which the sub group will be created.
Step 4: Select Sub Group Levels and Enter ID
1. Select the required **Item Sub Group 1** and **Item Sub Group 2.**
2. Then enter the **Item Sub Group 3 ID** in the provided field.
* Ensure the ID is unique and correctly entered.
Step 5: Save the Item Sub Group 3
* After entering all required details, click on the **Save** button to successfully create the Item Sub Group 3.
---
# 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-3/item-sub-group-3.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.
.png?alt=media)
