> 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/units-of-measure.md).
# Units of measure
## Units of measure
**Menu path:** `Administration -> Dictionaries -> Products`
The `Units of measure` tab is used to maintain unit of measure conversions for the product.
It is used when the product can be handled in more than one unit and the system needs to know the relationship between the base unit and the target unit.
### When to use
It is worth checking or adding a unit conversion when:
* the product is received, ordered or recorded in a unit different from the base unit,
* documents operate on collective packaging and the product is sold in pieces by default,
* a document unit needs to be linked with the unit used on the product,
* a user reports a problem with quantity resulting from unit conversion.
### Adding a conversion
Clicking `ADD` opens the `Unit measure conversion` screen.
### Conversion fields
| Field | Meaning |
| ------------- | ---------------------------------------------------------------------------------------------------- |
| `Source unit` | Source unit from which the conversion starts. For example `Pcs`. |
| `Multiplier` | Multiplier defining the relationship between the source and target unit. |
| `Target unit` | Target unit into which the source unit is converted. For example `Kilogram`, `Litr`, `Pcs` or `Box`. |
### List columns
| Column | Meaning |
| --------------------- | ---------------------------- |
| `Source name of unit` | Name of the source unit. |
| `Document code` | Unit code used in documents. |
| `Multiplicity` | Conversion multiplier. |
| `Target name of unit` | Name of the target unit. |
| `Target unit code` | Target unit code. |
### What to watch out for
* An incorrect multiplier can affect quantities visible in documents and analyses.
* Conversion should be set according to the unit rules adopted in the implementation.
* If you are not sure what unit relationship to use, consult the change with the administrator or the team responsible for product records.
### Related pages
* [Source data](/aquila-store-user-manual/products-and-product-records/source-data.md)
* [Warehouse stocks](/aquila-store-user-manual/products-and-product-records/warehouse-stocks.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/units-of-measure.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.
