> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/products-and-product-records/product-groups.md).
# Product groups
## Product groups
**Menu path:** `Administration -> Dictionaries -> Product groups`
Product groups organize product records and make it easier to work with a large number of products.
The group structure can be used for filtering, reporting, sales analysis, process configuration and assigning a product to the correct assortment area.
### When to use
Use this screen when you need to check the product group structure, add a new group or indicate the correct group while creating or editing a product.
### Steps
1. Open `Administration -> Dictionaries -> Product groups`.
2. Check the group structure in the `Data` section.
3. If you are adding a new group, click `ADD`.
4. Complete the name, number and place in the structure.
5. Save the group.
6. Return to the product and assign it to the correct group.
### What to watch out for
* Do not create new groups if a similar group already exists.
* Group names should be consistent with the adopted assortment structure.
* Changing a product group can affect reporting and filtering.
* If the group structure is fed from an external system, changes should be made according to the implementation process.
### Related pages
* [Adding a product](/aquila-store-user-manual/products-and-product-records/adding-a-product.md)
* [Editing a product](/aquila-store-user-manual/products-and-product-records/editing-a-product.md)
* [Searching for a product](/aquila-store-user-manual/products-and-product-records/searching-for-a-product.md)
---
# 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.aquiladynamics.com/aquila-store-user-manual/products-and-product-records/product-groups.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.
