> 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.md). # Products and product records ## Products and product records This chapter describes how to work with product records in the Aquila Flex backend. A product record is one of the core elements of the system: a product can be used in sales, orders, price lists, promotions, warehouse documents, reports and POS processes. The chapter covers: * `Administration -> Dictionaries -> Products` - the product list and product record details, * `Administration -> Dictionaries -> Product groups` - the product group structure, * product tabs, for example `Availability`, `PLU codes`, `Bound products`, `Prices`, `Configuration on cash register`, `Orders parameters` and `Attributes`. ### What you will find in this chapter | Page | Purpose | | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | [Product records overview](/aquila-store-user-manual/products-and-product-records/product-records-overview.md) | What product data is maintained in the backend. | | [Searching for a product](/aquila-store-user-manual/products-and-product-records/searching-for-a-product.md) | How to find a product on the list. | | [Adding a product](/aquila-store-user-manual/products-and-product-records/adding-a-product.md) | How to create a new product record. | | [Editing a product](/aquila-store-user-manual/products-and-product-records/editing-a-product.md) | How to change the data of an existing product. | | [Product types](/aquila-store-user-manual/products-and-product-records/product-types.md) | How the product types available in the product record differ. | | [Product card navigation](/aquila-store-user-manual/products-and-product-records/product-card-navigation.md) | In what order to read the product card and where to find the tab descriptions. | | [Source data - basic product data](/aquila-store-user-manual/products-and-product-records/source-data.md) | How to read the top section of the product card. | | [Life Cycle](/aquila-store-user-manual/products-and-product-records/life-cycle.md) | Which processes the product can participate in. | | [Product groups](/aquila-store-user-manual/products-and-product-records/product-groups.md) | How the product group structure works. | | [Availability - product activity on a location](/aquila-store-user-manual/products-and-product-records/availability.md) | How to understand product availability for a location. | | [PLU codes - PLU, EAN and product identifiers](/aquila-store-user-manual/products-and-product-records/plu-codes.md) | How to describe codes used to identify a product. | | [Bound products - linked products, sets and deposits](/aquila-store-user-manual/products-and-product-records/bound-products.md) | How to understand relationships between products, sets, packaging and deposits. | | [Warehouse stocks](/aquila-store-user-manual/products-and-product-records/warehouse-stocks.md) | How to check product stock levels. | | [VAT changes](/aquila-store-user-manual/products-and-product-records/vat-changes.md) | How to read the VAT change history. | | [Prices](/aquila-store-user-manual/products-and-product-records/prices.md) | How to read product price data. | | [Attributes - product attributes](/aquila-store-user-manual/products-and-product-records/attributes.md) | How to use additional product characteristics. | {% hint style="warning" %} Changes in a product record can affect sales, documents, orders, reports and data visible on POS. Before changing data, make sure you understand which processes use the product. {% endhint %} --- # 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.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.