> 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/warehouse-stocks.md).
# Warehouse stocks
## Warehouse stocks
**Menu path:** `Administration -> Dictionaries -> Products`
The `Warehouse stocks` tab shows the product stock level in warehouses.
It is an informational and analytical view. It allows you to check what quantity of the product is recorded for a given location and warehouse.
Stock level does not decide whether the product can be sold on POS. Lack of stock in the warehouse does not block sales. In the system, products can be sold with stock level `0` or with negative stock.
### What you will find on the tab
| Element | Meaning |
| ----------- | ---------------------------------------------- |
| `Shop` | Location for which the stock level is checked. |
| `Warehouse` | Warehouse assigned to the location. |
| `Stock` | Product quantity in the warehouse. |
### When to check
Check `Warehouse stocks` when you want to:
* verify the product quantity in the warehouse,
* compare product stock between locations or warehouses,
* analyze a report related to stock level,
* check whether the product stock is positive, zero or negative.
If the problem concerns product visibility on POS, do not diagnose it based on the value in `Warehouse stocks`.
Stock level shows product quantity, but does not define product visibility on the cash register.
In this situation, check primarily `Availability`, product codes, prices and POS configuration.
### What to watch out for
* Stock level is not the same as product activity.
* Stock level `0` or negative stock does not have to block product sale.
* A product can be active and available for sale despite zero or negative stock.
* A product can have stock in a warehouse, but still not be visible on POS if activity, price, code or POS configuration is missing.
* The `Warehouse stocks` tab does not replace the analysis of warehouse movements. If you need to check where the stock level comes from, go to `Income and expenditures`, if this tab is used in the implementation.
### Related pages
* [Availability](/aquila-store-user-manual/products-and-product-records/availability.md)
* [Product records overview](/aquila-store-user-manual/products-and-product-records/product-records-overview.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/warehouse-stocks.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.
