> 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/adding-a-product.md).
# Adding a product
## Adding a product
**Menu path:** `Administration -> Dictionaries -> Products`
Adding a product creates a new product record that can later be used in sales, document, order, price, promotion and reporting processes. Depending on the implementation, some fields may be required by the business process, integration or local regulations.
### Central or local product
Before adding a product, determine whether the product record should be created centrally or locally.
| Product type | When to use | What to check |
| --------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Central product | When the product should be visible across the whole location network. | Visibility in all locations does not automatically mean activity or sale availability. After creation, check `Availability`, prices, codes and POS configuration. |
| Local product | When the product should be created for a specific location and its subordinate locations. | A local product is not visible in parent or parallel locations. `Product symbol` is generated by the system. |
For central products, `Product symbol` can be defined. For local products, `Product symbol` is assigned by the system.
{% hint style="info" %}
Central products can be managed through `OpenAPI` if this model has been included in the implementation. Technical details of the integration should be confirmed with the Aquila Flex technical team.
{% endhint %}
### When to use
Use this procedure when a new product needs to be entered into the system or when a product record needs to be prepared before further configuration of prices, activity, codes and attributes.
### Steps
1. Open `Administration -> Dictionaries -> Products`.
2. Click `ADD`.
3. Complete the basic product data.
4. Select the product group.
5. Complete classification data if required.
6. Click `SAVE`.
7. After saving, complete the tabs required for the process, for example `Availability`, `PLU codes`, `Configuration on cash register`, `Orders parameters` or `Attributes`.
8. Check whether the product is visible on the list and whether it has the correct activity for the relevant locations.
### Key fields
| Field | Meaning |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Product index | Product index in the system. |
| Product source | Product source, for example central or local product, depending on configuration and where the product record was created. |
| Product name | Full product name visible in the product record and used in processes. |
| Name on cash register | Product name used on POS. |
| Product symbol | Product symbol. For a central product, it can be defined during creation; for a local product, it is generated by the system. |
| PKWiU | Product classification used where required by the process or regulations. |
| Product group | Product group selected from the product group structure. |
| VAT rate | VAT rate assigned to the product. |
### What to watch out for
* Before adding a product, make sure the correct product group exists.
* Product names should be readable and consistent with the organization's rules.
* If the product is to be sold on POS, check sales settings and activity on the location.
* Price data may need to be completed in the price or price list module.
* If the product is created for integration purposes, make sure the symbol, code and required attributes follow the agreed standard.
* Do not treat product visibility as confirmation that the product is active and ready for sale.
### Related pages
* [Product groups](/aquila-store-user-manual/products-and-product-records/product-groups.md)
* [Availability - product activity on a location](/aquila-store-user-manual/products-and-product-records/availability.md)
* [PLU codes - PLU, EAN and product identifiers](/aquila-store-user-manual/products-and-product-records/plu-codes.md)
* [Bound products - linked products, sets and deposits](/aquila-store-user-manual/products-and-product-records/bound-products.md)
* [Attributes - product attributes](/aquila-store-user-manual/products-and-product-records/attributes.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/adding-a-product.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.
