> 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/masters/main-master-module/master/product-sub-group.md).
# Product Sub Group
The **Product Sub Group Master** is used to define sub-classifications within a **Product Group**. It helps in organising products in a more detailed and structured manner. This enables better **product management, reporting, pricing control, inventory tracking, and accounting accuracy** within the system.
### Steps to Create Product Sub Group
Step 1: Go to the **Settings** section
1. Open the **Master** module. From there, select **Product Sub Group Master**.
Step 2: Click on the **Add** button to create a new product sub group.
Step 3: A form will appear after clicking the Add button. Enter the required details based on user needs, such as:
* **Product Sub Group Name**
* **Product Group**
* **Product Sub Group Id**
* **Default Account Name**
Ensure that the correct Product Group is selected to maintain proper hierarchy and classification.
Step 4: After entering all required details and selecting the appropriate Product Group, click the **Save** button to create the product sub group in the system.
---
# 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/masters/main-master-module/master/product-sub-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.
.png?alt=media)
.png?alt=media)