> 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/product-card-navigation.md).

# Product card navigation

## Product card navigation

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

The product card is divided into two parts. The top part contains the `Source data` section, which is the basic product data. Below it are tabs that describe product availability, codes, relationships, warehouses, VAT, prices, POS, units of measure, attributes, translations, pictures and order parameters.

Read the product card documentation in the same order in which the user moves through the screen: first `Source data`, then the following tabs from left to right.

{% hint style="info" %}
Tabs visible on the product card can differ between users, roles and implementations. If you do not see a tab described in the documentation, it may be caused by missing permissions, environment configuration or the fact that the function is not used in your implementation.
{% endhint %}

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FAQmjCBskA0PKBCrWE8l8%2F045.png?alt=media&amp;token=74fdb043-3fa3-4119-8103-1d48dd110674" alt=""><figcaption></figcaption></figure>

### Product card description order

| Order | Product card part                | Where to go                                                                                                                |
| ----- | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| 1     | `Source data`                    | [Source data - basic product data](/aquila-store-user-manual/products-and-product-records/source-data.md)                  |
| 2     | `Life Cycle`                     | [Life Cycle](/aquila-store-user-manual/products-and-product-records/life-cycle.md)                                         |
| 3     | `Availability`                   | [Availability - product activity on a location](/aquila-store-user-manual/products-and-product-records/availability.md)    |
| 4     | `PLU codes`                      | [PLU codes](/aquila-store-user-manual/products-and-product-records/plu-codes.md)                                           |
| 5     | `Bound products`                 | [Bound products](/aquila-store-user-manual/products-and-product-records/bound-products.md)                                 |
| 6     | `Warehouse stocks`               | [Warehouse stocks](/aquila-store-user-manual/products-and-product-records/warehouse-stocks.md)                             |
| 7     | `VAT changes`                    | [VAT changes](/aquila-store-user-manual/products-and-product-records/vat-changes.md)                                       |
| 8     | `Prices`                         | [Prices](/aquila-store-user-manual/products-and-product-records/prices.md)                                                 |
| 9     | `Prices on shops`                | [Prices on shops](/aquila-store-user-manual/products-and-product-records/prices-on-shops.md)                               |
| 10    | `Shop purchase prices`           | [Shop purchase prices](/aquila-store-user-manual/products-and-product-records/shop-purchase-prices.md)                     |
| 11    | `Margins on shops`               | [Margins on shops](/aquila-store-user-manual/products-and-product-records/margins-on-shops.md)                             |
| 12    | `Prices history`                 | [Prices history](/aquila-store-user-manual/products-and-product-records/prices-history.md)                                 |
| 13    | `Configuration on cash register` | [Configuration on cash register](/aquila-store-user-manual/products-and-product-records/configuration-on-cash-register.md) |
| 14    | `Units of measure`               | [Units of measure](/aquila-store-user-manual/products-and-product-records/units-of-measure.md)                             |
| 15    | `Attributes`                     | [Attributes - product attributes](/aquila-store-user-manual/products-and-product-records/attributes.md)                    |
| 16    | `Translations`                   | [Translations](/aquila-store-user-manual/products-and-product-records/translations.md)                                     |
| 17    | `Picture`                        | [Picture](/aquila-store-user-manual/products-and-product-records/picture.md)                                               |

### How to navigate

1. Open the product from the product list.
2. Check the data in the `Source data` section.
3. Go to the relevant tab according to the table above.
4. If a given tab is not visible, check user permissions, role and implementation configuration scope.
5. After changing data, click `SAVE` if the screen requires saving.

### What to watch out for

* Not every tab is used to edit data; some tabs are for viewing only.
* Missing data in a tab does not always mean an error. It may result from product, location or process configuration.
* Changes in tabs related to prices, POS, VAT, activity and relationships can affect sales, documents and reports.


---

# 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/product-card-navigation.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.
