> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/planning/price-change.md).

# Price Change

### Price Change

This report will show you the percentage of increase of the buying cost by item for every item affected by a price change for a period of time. This will help to find out the reason for an operating cost increase by spotting the variation of the buying price.

This report may also be useful when you are buying stock at a guaranteed price from a supplier and you want to verify no price changes were maid.

**Supplier Code**

Select a supplier code from the list

**Product Code**

Select a product code from the list.

**Inventory Category**

If you have selected all the products, you can specify an inventory category.

**Inventory Group**

If you have selected all the categories, you can specify an inventory group.

**Date**

Select a date range by entering the beginning and ending date.

**Sort Order**

Select the field you want the information to be sorted on. There are six different sorts available: The Description The Category

Time period The Group The Supplier

The %

[![Report Link](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/ReportLink.png)](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/Chap11_InventoryManagement/Help/RPriceChange.htm)


---

# 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.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/planning/price-change.md?ask=<question>&goal=<user_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.