> 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/configuration-on-cash-register.md).
# Configuration on cash register
## Configuration on cash register
**Menu path:** `Administration -> Dictionaries -> Products`
The `Configuration on cash register` tab contains product settings used during sale on POS. Settings can apply to all locations or only to the current location, so when analyzing a product you always need to check the location context in which the user is working.
### Setting scope
| Scope | Meaning |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| `All locations` | Setting that applies more broadly, for the product in locations covered by the configuration. |
| `Current location` | Setting for the location where the user is currently logged in. It can overwrite the general setting if configuration and permissions allow it. |
### Fields visible on the screen
| Field | Meaning |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Cashier set the price` | Defines whether the cashier can set the product price during sale on POS. |
| `Price changes blockage on the cashier` | Defines whether changing the product price on the cash register is blocked. |
| `Special sale procedure` | Indicates a special sale procedure if the product requires such handling on POS. An example can be selling a gift card, where the cashier enters the card top-up value. |
| `Product weighed` | Defines whether the product is handled as a weighed product. |
| `Age verification during sale` | Defines whether age verification is required during sale of the product. |
### How to interpret icons
| Icon | Meaning |
| ------------------- | --------------------------------------------------- |
| Red rollback symbol | Setting inherited or restored to the general value. |
| Green check mark | Setting enabled. |
| Orange cross | Setting disabled. |
### When to check
Check the `Configuration on cash register` tab when:
* the product behaves differently on POS than expected,
* the cashier cannot change the product price or the price can be changed despite an expected block,
* the product should be weighed,
* sale of the product requires age verification,
* the product requires a special sale procedure.
### What to watch out for
* Changing settings in this tab can affect how the product is sold on POS.
* Settings for `Current location` can differ from general settings.
* If the user cannot change the configuration, permissions or implementation configuration may be the cause.
* After changes that require POS synchronization, the effect may be visible only after data is updated on the cash register.
### Related pages
* [Availability - product activity on a location](/aquila-store-user-manual/products-and-product-records/availability.md)
* [Prices](/aquila-store-user-manual/products-and-product-records/prices.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/configuration-on-cash-register.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.
