> 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/searching-for-a-product.md).
# Searching for a product
## Searching for a product
**Menu path:** `Administration -> Dictionaries -> Products`
The product list consists of the `Filter` section and the `Data` section. Filters allow you to narrow down the product list before editing, viewing, exporting or analyzing a reported issue.
### When to use
Use this procedure when you want to find a product before editing it, checking details, verifying activity or analyzing a problem reported by a user.
### Steps
1. Open `Administration -> Dictionaries -> Products`.
2. In the `Filter` section, enter the product name, symbol, group or another available criterion.
3. If you want to search for part of a name, use the available field operator, for example a search that contains a text fragment.
4. If needed, set the location in the `Activity on` field.
5. Click `FILTER`.
6. Check the results in the `Data` section.
7. Select the correct product if you want to perform another operation.
8. If the product does not appear on the list, check whether you are working in a location where the product should be visible.
### Available criteria
| Field | Description |
| ----------- | --------------------------------------------------------------------------- |
| Prod.name | Product name or part of the name. |
| Symbol | Product symbol or its beginning. |
| Activity on | Location for which product activity is checked. |
| Group | Product group or part of the assortment structure. |
| Attributes | Additional product characteristics, if they are used in the implementation. |
### What to watch out for
* You do not always need to enter the full product name. In many fields, a text fragment is enough.
* If the product does not appear on the list, check the activity filter, group and selected attributes.
* A local product may not be visible in a parent or parallel location. Local products are visible in the location where they were created and in subordinate locations.
* If a product is inactive for a given location, it may not be visible in that location's operational processes.
* For service desk reports, note the search criteria, location and exact product name or code.
### Related pages
* [Product records overview](/aquila-store-user-manual/products-and-product-records/product-records-overview.md)
* [Editing a product](/aquila-store-user-manual/products-and-product-records/editing-a-product.md)
* [Availability - product activity on a location](/aquila-store-user-manual/products-and-product-records/availability.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/searching-for-a-product.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.
