> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/product-data/add-a-property-category.md).
# Add a Property Category
Within this article, you will find how to organize your product data efficiently by creating and managing property categories.
Product categories can be used to group properties, providing a structured way to manage and organize your product data. By categorizing properties, you can streamline the process of identifying and highlighting specific product benefits, making it easier to manage diverse product lines.
For example, you might create distinct categories for Blenders and Coffee Machines, along with general properties applicable across multiple products.
This categorization not only aids in better data organization but also enhances the ability to target and segment products effectively, ensuring that product-specific attributes are clearly defined and easily accessible.
1. Go to **Crobox App**, navigate to **Product Data** and select **Properties**.
2. Click on the three-dot menu and select **Add Category above.**
3. **Name** the category and if applicable, create conditions to segment specific products from your feed into the category (this is an optional filter to apply business rules).
4. After additional product categories are created, move properties to product-specific categories by **selecting the checkbox**, then choose **"Move to Category"** from the menu.
5. Adjust properties existing in multiple categories by updating the property settings and **adding all applicable categories.**
---
# 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.crobox.com/how-to-guides/product-data/add-a-property-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.
