> 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/picture.md).
# Picture
## Picture
**Menu path:** `Administration -> Dictionaries -> Products`
The `Picture` tab is used to upload a product picture.
The picture is used in places where the system presents visual product identification.
### Where the picture is visible
A picture uploaded in the `Picture` tab can be visible:
* on the product list, if the picture column is displayed in the column layout,
* on POS after scanning the product,
* on POS if the product is added to `QuickSelect`.
### File requirements
| Requirement | Value |
| ------------------------- | ----------------------------------------------- |
| Format | `JPG`, `PNG` |
| Maximum resolution | `640x480` |
| Behavior of larger images | Larger images are scaled to a lower resolution. |
| Maximum size | `200 KB` |
### How to upload a picture
1. Open the product card.
2. Go to the `Picture` tab.
3. Click `Choose file`.
4. Select the product picture file.
5. Click `IMPORT`.
6. Check whether the picture has been saved and is visible in places that use the product picture.
### What to watch out for
* The picture should be readable also in a smaller POS preview.
* If the picture should be visible on the product list, the user must have the appropriate column displayed.
* If the picture should be visible on POS, data synchronization may be required.
* Do not upload pictures containing customer data, personal data or elements unrelated to the product.
### Related pages
* [Product records overview](/aquila-store-user-manual/products-and-product-records/product-records-overview.md)
* [Sorting and column layout](/aquila-store-user-manual/system-basics/sorting-and-column-layout.md)
* [Configuration on cash register](/aquila-store-user-manual/products-and-product-records/configuration-on-cash-register.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/picture.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.
