> 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/editing-a-product.md).

# Editing a product

## Editing a product

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

Editing a product allows you to change product record data such as name, symbol, group, sales settings, codes, activity and attributes. Changes can affect sales processes, reports, documents, orders and integrations.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FlByn7zh7hVm9fUsTvtuR%2F046.png?alt=media&amp;token=82341c70-d451-4c6e-84d1-bad1e00691c5" alt=""><figcaption></figcaption></figure>

### When to use

Use this procedure when product data needs to be corrected, missing information needs to be completed, the product group needs to be changed, POS configuration needs to be checked or a problem reported by a user needs to be analyzed.

### Steps

1. Open `Administration -> Dictionaries -> Products`.
2. Search for the product.
3. Select the correct record on the list.
4. Click `EDIT`.
5. Change the data in the relevant section or tab.
6. Click `SAVE` if the change requires saving.
7. Check the result on the product list or in the relevant details tab.

### Product tabs

| Tab                            | Purpose                                                                                                            |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| Source data                    | Product identification and descriptive data visible above the tabs, including product source and `Product symbol`. |
| Life Cycle                     | Processes in which the product can participate, for example sale, return, order and acceptance of delivery.        |
| Availability                   | Product activity on locations.                                                                                     |
| PLU codes                      | PLU codes or codes used to identify the product.                                                                   |
| Bound products                 | Product relationships with other records, for example packaging, deposit or set component.                         |
| Warehouse stocks               | Product stock levels in warehouses.                                                                                |
| VAT changes                    | Product VAT change history.                                                                                        |
| Prices                         | Product price information. The edit scope depends on configuration and the pricing process.                        |
| Configuration on cash register | Settings related to sales on POS.                                                                                  |
| Orders parameters              | Parameters used when ordering the product.                                                                         |
| Attributes                     | Additional product characteristics used in configuration or reporting.                                             |

The description of where to find specific information on the product card is available on [Product card navigation](/aquila-store-user-manual/products-and-product-records/product-card-navigation.md).

### What to watch out for

* Changing the name or symbol can affect how users search for the product.
* Changing the product group can affect reporting, filters and processes based on groups.
* If the product is used in integrations, consult the impact with an administrator or implementation team before changing identifiers.
* Local prices visible on the product card can be informational. Change prices according to the process described in the pricing chapter.
* A central product can be visible in all locations, while a local product is visible only in the location where it was created and in subordinate locations.

### Related pages

* [Searching for a product](/aquila-store-user-manual/products-and-product-records/searching-for-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)
* [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/editing-a-product.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.