> 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-records-overview.md).
# Product records overview
## Product records overview
**Menu path:** `Administration -> Dictionaries -> Products`
Product records are used to maintain data describing products used in the backend and on POS. They include basic data, product group, codes, sales settings, activity on locations, attributes and information used in documents, prices, orders and reports.
The columns visible on the product list can be adjusted by the user, if they have access to this option in the interface. The column layout and the number of visible records can be changed according to the general rules for working with tables. Details are described on the page [Sorting and column layout](/aquila-store-user-manual/system-basics/sorting-and-column-layout.md).
### When to use
Use this module when you need to:
* search for a product,
* add a new product record,
* change the name, symbol, group or classification data,
* check product activity on a location,
* complete PLU codes or barcodes,
* check or complete product attributes,
* analyze product data before reporting an issue to service desk or the product records administrator.
### Key dependencies
| Element | Meaning |
| ----------------- | -------------------------------------------------------------------------------------------------- |
| Product | A product record item used in sales, documents, price lists, promotions, orders and reports. |
| Product group | The product's place in the assortment structure. Groups help filter, report and organize products. |
| Product activity | Information whether the product is available for the selected location. |
| PLU code | A code used to identify a product, often for weighed or fresh products. |
| Product attribute | An additional product characteristic used for description, filtering or process configuration. |
| POS settings | Data that affects product behavior during sales, for example sale blockage or weighed product. |
### Central and local products
Products can be created centrally or locally. The place where the product is created affects which locations can see the product on the product list.
| Product type | Visibility | Product symbol |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| Central product | The product is visible in all locations. Product visibility does not mean that the product is active or that it can be sold in every location. | `Product symbol` can be defined when the product is created. |
| Local product | The product is created in a given location and is visible only in subordinate locations. In parent and parallel locations, the product is not visible on the product list. Product visibility does not mean that the product is active or that it can be sold. | `Product symbol` is generated by the system. |
Central products can also be managed through `OpenAPI` if this integration model has been included in the implementation. Technical details of product handling through `OpenAPI` should be confirmed with the Aquila Flex technical team.
### Product and location
A product can be visible in a given location, but its use in a shop, warehouse or on POS depends on the configuration for that location. Therefore, when analyzing a product, you need to check not only the basic data and product source, but also the tabs and fields related to the location.
| Area | How it affects the product |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| Location | Defines the shop, head office or other object for which product availability is checked. |
| Location group | Allows multiple locations to be handled together, for example for activity, promotions, reports or configuration. |
| Warehouse | Is assigned to a location and stores product stock. One location can have more than one warehouse. |
| `Availability` | Shows whether the product is active for the location and whether it can be used in sales, returns and orders. |
| `Warehouse stocks` | Shows the product quantity in warehouses for the selected location. |
| Local prices | Can differ from the global price if the implementation allows prices at location level. |
| POS | A product visible on POS should have the correct activity, price, codes and sales configuration for the given location. |
If a product is not visible in a shop or does not work in the expected process, first check whether it is a central or local product, which location you are working in, whether the product is active, and whether it has the correct warehouse, price and POS configuration.
If you already know what product information you are looking for, go to [Product card navigation](/aquila-store-user-manual/products-and-product-records/product-card-navigation.md). It contains a map of the tabs and indicates where to check specific data.
### What to watch out for
* Do not change product data if you do not know whether the product is used in active prices, promotions or documents.
* Some product data can be used by POS, so a backend change may become visible in the shop only after synchronization.
* Product prices are described separately in the chapter about prices and price lists. The product card can show price information, but not every screen is used to change it.
* If a product is not visible in the shop, check the product source, location, product activity, group, price and POS configuration.
### Related pages
* [Searching for a product](/aquila-store-user-manual/products-and-product-records/searching-for-a-product.md)
* [Adding a product](/aquila-store-user-manual/products-and-product-records/adding-a-product.md)
* [Product card navigation](/aquila-store-user-manual/products-and-product-records/product-card-navigation.md)
* [Availability - product activity on a location](/aquila-store-user-manual/products-and-product-records/availability.md)
* [Sorting and column layout](/aquila-store-user-manual/system-basics/sorting-and-column-layout.md)
* [Glossary](/aquila-store-user-manual/introduction/glossary.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/product-records-overview.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.
