> 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/attributes.md).
# Attributes
## Attributes - product attributes
**Menu path:** `Administration -> Dictionaries -> Products`
Product attributes are used to store additional characteristics of the product record. They can be used to describe the product, filter, report, handle labels, meet legal requirements or support customer-specific configuration.
### When to use
Use this tab when the product requires an additional marker, configuration value or information that is not present in basic product data.
### Steps
1. Open `Administration -> Dictionaries -> Products`.
2. Search for the product.
3. Open product details.
4. Go to the `Attributes` tab.
5. Click `ADD` if a new attribute needs to be added.
6. Select the attribute from the list.
7. Complete the value.
8. Save the change.
9. Check whether the attribute is visible on the list.
### Attribute examples
| Attribute | Example use |
| ----------------- | --------------------------------------------------------------------- |
| Concession | Marking a product that requires additional control or classification. |
| Label template | Selecting a label template for the product. |
| Origin country | Country of origin used in description or reporting. |
| Dynamic attribute | Characteristic defined according to customer or process needs. |
### What to watch out for
* Attributes can differ between implementations because they are defined according to customer needs.
* Do not add an attribute if you do not know which process uses it.
* An incorrect attribute value can affect filtering, reporting, labels or integrations.
* If the expected attribute is not visible, check product attribute configuration or report the topic to the administrator.
### Related pages
* [Editing a product](/aquila-store-user-manual/products-and-product-records/editing-a-product.md)
* [Product groups](/aquila-store-user-manual/products-and-product-records/product-groups.md)
* [PLU codes - PLU, EAN and product identifiers](/aquila-store-user-manual/products-and-product-records/plu-codes.md)
* [Bound products - linked products, sets and deposits](/aquila-store-user-manual/products-and-product-records/bound-products.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/attributes.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.
