> 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-on-shops.md).
# Prices on shops
## Prices on shops
**Menu path:** `Administration -> Dictionaries -> Products`
The `Prices on shops` tab shows product prices by location. This view is useful when checking what price or promotional price applies to a specific shop or location in the structure.
### Columns
| Column | Meaning |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| `Name` | Name of the location for which the price is presented. |
| `Number` | Location number. |
| `Activity` | Information whether the product is active for the given location. |
| `Selling price` | Regular selling price for the location. |
| `Promotion sell. price` | Promotional selling price for the location. |
| `Omnibus price` | The lowest price from 30 days before the promotion. Visibility of this price depends on configuration and implementation. |
| `Price by cashier` | Information whether the price can be assigned by the cashier on POS. |
### When to check
Check this tab when:
* you want to compare product prices between locations,
* a user reports a difference between the backend price and the shop price,
* you need to check whether a given location has its own price,
* you need to check a promotional price or omnibus price for a location.
### What to watch out for
* Missing price in a location row does not always mean an error. The price can be inherited from a parent location or come from another price source.
* When analyzing a price, also check the Prices tab, price lists and promotion configuration.
### Related pages
* [Prices](/aquila-store-user-manual/products-and-product-records/prices.md)
* [Availability - product activity on a location](/aquila-store-user-manual/products-and-product-records/availability.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-on-shops.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.
