> 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/margins-on-shops.md).

# Margins on shops

## Margins on shops

**Menu path:** `Administration -> Dictionaries -> Products`

The `Margins on shops` tab shows the product margin by location.

It is useful when analyzing the pricing model in which the selling price or product profitability depends on the margin set for a shop or location.

### Columns

| Column     | Meaning                                                           |
| ---------- | ----------------------------------------------------------------- |
| `Name`     | Name of the location for which the margin is presented.           |
| `Number`   | Location number.                                                  |
| `Activity` | Information whether the product is active for the given location. |
| `Margin`   | Margin assigned to the product for the location.                  |

### When to check

Check this tab when:

* you are analyzing product margin for a specific shop or location,
* the product price is calculated using margin,
* you are comparing margins between locations,
* a user reports a problem with a price resulting from margin.

### What to watch out for

* Margin is not the selling price. It can be one of the elements used in the price calculation or analysis process.
* Missing value in a location row does not always mean an error. Margin may not be maintained at this location level.
* When analyzing a price, also check Prices and Shop purchase prices.

### Related pages

* [Prices](/aquila-store-user-manual/products-and-product-records/prices.md)
* [Shop purchase prices](/aquila-store-user-manual/products-and-product-records/shop-purchase-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/margins-on-shops.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.