> 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-category.md).
# Product Category
The **Product Category** is used to classify products based on shared characteristics. It helps in organizing products efficiently and supports better management of inventory, reporting, pricing, and accounting within the system. Each product category is linked with a **GL (General Ledger) account**, which ensures accurate financial tracking.
## Steps to Create a Product Category
Step 1: Go to the **Settings** section
1. Open the **Master** module. From there, select **Product Category Master**.
Step 2: Click on the **Add** button to create a new product category.
Step 3: A form will appear after clicking the Add button. Enter the required details, such as:
* **Product Category ID**
* **Product Category Name**
Step 4: Choose the appropriate **GL (General Ledger) account** from the available list.
* This step is important because it ensures that all financial transactions related to the product category are correctly recorded in the accounting system.
Step 5: After entering all required details and selecting the GL Ledger, click the **Save** button to create the product category.
---
# 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-category.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)
