> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/pim3/fundamental-concepts/catalogues-and-categories.md).
# Catalogues & categories
This article explains the concepts of catalogues and categories and how they are used to organize your products
### What are catalogues
Catalogues are root elements in category structures used for organizing products logically in categories.
### What are categories
Categories are used to create hierarchical structures within a catalogue. Categories serves as a means for structuring products in meaningful classifications.
Categories can be organized in a nested structure to form the desired hierarchical structure. There are no limitations to the number of categories and depth of category structure in the system.
### Standard category
Standard categories allows classifying products and variant groups manually.
### Dynamic category
Dynamic categories allows you to automatically classify products and variant groups, which meet certain criteria.
---
# 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.struct.com/pim3/fundamental-concepts/catalogues-and-categories.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.