> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/product/product-category/creating-product-category.md).
# Creating Product Category
### Creating Product Category
* Navigate to the Product Category Module
* Enter the following details:
**Category** **Name**: Enter the desired name for the Product Category that you wish to assign. Category
**Description**: Provide a description for the Product Category.
**Category Logo URL:** Enter the URL of the image to be used as the logo for the Product Category. This helps visually identify the category in the system.
After entering the details, click on the Save button to store the information. The Product Category will be visible in the Product Category Centre, where you can make edits or modifications as needed.
### Header Options
**Delete**: This allows users to delete a particular Product Category from 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://docs.xorosoft.com/xoroerp-1/admin/product/product-category/creating-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.
