> 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/prices-history.md).
# Prices history
## Prices history
**Menu path:** `Administration -> Dictionaries -> Products`
The `Prices history` tab shows the history of product price changes.
It is useful when you need to check how the regular price or promotional price changed over time and whether the price change was applied in the expected period.
### How to use the tab
1. Open the product card.
2. Go to the `Prices history` tab.
3. In the `Date range` field, select how to define the date range.
4. Complete the `from` and `to` dates.
5. Click `FILTER`.
6. Check the price change chart for the selected period.
### What the chart shows
| Element | Meaning |
| ------------------------- | ------------------------------------------------------------------- |
| `Selling price` | Regular selling price of the product in the selected period. |
| `Promotion selling price` | Promotional product price in periods when the promotion was active. |
| `Price` | Price value presented on the vertical axis. |
| `Date` | Date or point in time for which the price value is presented. |
### When to check
Check the `Prices history` tab when:
* a user reports that the product price changed at an unexpected moment,
* you need to confirm whether a promotional price was valid in a given period,
* you are analyzing differences between regular and promotional price,
* you are checking the change history before analyzing sales data.
### What to watch out for
* Price history shows changes over time, but does not replace analysis of the full price hierarchy.
* If the price on POS was different than expected, also check Prices, Prices on shops and price list configuration.
* The scope of visible data can depend on user permissions and implementation configuration.
### Related pages
* [Prices](/aquila-store-user-manual/products-and-product-records/prices.md)
* [Prices on shops](/aquila-store-user-manual/products-and-product-records/prices-on-shops.md)
* [Product card navigation](/aquila-store-user-manual/products-and-product-records/product-card-navigation.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/prices-history.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.
