> 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/plu-codes.md).
# PLU codes
## PLU codes - PLU, EAN and product identifiers
**Menu path:** `Administration -> Dictionaries -> Products`
PLU, EAN and other identifiers help recognize the product in sales, labeling, weighing, integration and POS handling processes. The scope of use of this data depends on the implementation configuration and assortment type.
The `PLU codes` tab shows the list of codes assigned to the product. On the list, you can check the code, code type, multiplicity, assigning scope, information whether the code is default and whether it is active.
Codes assigned to a product are inherited by subordinate locations according to the location structure. This means that a code added at a parent level can be available lower in the structure if the product and location configuration allows it.
### When to use
Use this section when the product requires an additional identification code, a code for POS, a code for scales or an alternative barcode.
### Code list
| Column | Meaning |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `Code` | Code value assigned to the product, for example EAN or PLU. |
| `Multiplicity` | Code multiplicity. Defines what product quantity is linked to the code. |
| `Type` | Code type, for example `EAN 13`, `PLU`, `EAN 8` or `Local`. |
| `Assigning` | Code assigning scope, for example global or local, depending on configuration. |
| `Default` | Information whether the code is the default code for the product. A code marked as `Default` is used when printing price labels. |
| `Active` | Information whether the code is active and can be used. |
| `Image` | Barcode preview, if generated by the system. |
### Adding or editing a code
1. Open the product in edit mode.
2. Go to the `PLU codes` tab.
3. Click `ADD` if you need to add a new code, or select an existing code and click `EDIT` if you want to change it.
4. Complete the fields on the `Code details` screen.
5. Click `SAVE`.
6. Check whether the code is visible on the list and has the correct status.
### Fields on the Code details screen
| Field | Meaning |
| -------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `Code` | Code assigned to the product. The field is required. |
| `Type` | Code type. The field is required and selected from a list. |
| `Multiplicity` | Code multiplicity. By default, it can be set to `1`. The field is required. |
| `Default` | Marks the code as the default code for the product. A code with `Default` selected is used when printing price labels. |
| `Active` | Marks that the code is active. An inactive code should not be used in current processes. |
| `FIRST FREE` | Helper button for getting the first free code. |
### Code types
On the `Code details` screen, the `Type` list can include among others: `EAN 13`, `PLU`, `EAN 8` and `Local`.
| Type | When to use |
| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `EAN 13` | Standard EAN-13 code. The system should validate it according to the EAN standard, including the check digit. Use it for products with a correct EAN-13 code. |
| `EAN 8` | Shorter EAN code. The system should validate it according to the EAN standard, including the check digit. Use it for products with a correct EAN-8 code. |
| `PLU` | Code without EAN standard validation. It can be a short code used by the cashier, for example `12`, especially for products without an EAN code, such as bakery or fresh products. |
| `Local` | Code without EAN standard validation. Functionally, it works the same as `PLU`; the difference is the code type and naming rules adopted in the organization. |
`PLU` and `Local` do not differ in validation mechanics. Both types can accept codes without a check digit. Which type should be used should follow the standard adopted in the organization or implementation.
### What to watch out for
* A PLU code or barcode should be unique according to the organization's rules.
* An incorrect code can cause problems during sale, scanning or data import.
* If the code should work on POS or scales, synchronization may be required after a change.
* If a product has many codes, check which code is marked as `Default`, because this code will be used when printing price labels.
* Do not delete or deactivate a code without confirming whether it is used by POS, scales, labels or integrations.
* For `EAN 13` and `EAN 8` types, the code should comply with the EAN standard. If the product has no EAN code, use the type compliant with the organization's standard, for example `PLU` or `Local`.
* Before adding a code at a parent level, remember that the code can be inherited by subordinate locations.
### Related pages
* [Adding a product](/aquila-store-user-manual/products-and-product-records/adding-a-product.md)
* [Editing a product](/aquila-store-user-manual/products-and-product-records/editing-a-product.md)
* [Bound products](/aquila-store-user-manual/products-and-product-records/bound-products.md)
* [Availability](/aquila-store-user-manual/products-and-product-records/availability.md)
* [Product card navigation](/aquila-store-user-manual/products-and-product-records/product-card-navigation.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/plu-codes.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.
