> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2022/2022-09-19-ce-price-service-improvements.md).

# 2022-09-19: CE - Price Service Documentation

The following changes have been made to the [Price Service guide](/api-references/api-guides/prices-and-taxes/price-service/price.md) in the *Developer Guides*:

* All class diagrams including the `Price` and `PriceListPrice` now reflect the `tierValues.id` fields.
* Information on retrieving and assigning pricing tiers to prices has been added to the following tutorials:
  * "How to set up your first price"
  * "How to implement different pricing strategies"
  * "How to use the price matching functionality"
* A **Run in Postman** button has been added to the "How to configure a price list" tutorial.
* Response examples in the "How to use the price matching functionality" tutorial have been updated with tax values calculated for the matched prices.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.emporix.io/release-notes/archive/2022/2022-09-19-ce-price-service-improvements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.