> 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/availability.md).
# Availability
## Availability - product activity on a location
**Menu path:** `Administration -> Dictionaries -> Products`
The `Availability` tab defines whether the product is active in a given location. Activity in a location means whether the product can be visible and used in the context of that location, especially on POS.
This is one of the first things to check when a user reports that a product is not visible on POS or cannot be used in sale, return or order for a specific shop.
### How to read the Availability tab
A product can be visible on the product list, but this does not yet mean that it will be active in every location. The `Availability` tab allows you to check for which locations the product is active and in which processes it can be used.
| Column / element | Meaning |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `Name` | Name of the location or location group visible in the structure. |
| `Number` | Number of the location or location group. |
| `Country` | Country assigned to the location. |
| `Activity` | Information whether the product is active in the given location. Lack of activity can cause the product not to be visible on POS. |
| `Sale` | Information whether the product can be sold in the given location. |
| `Return` | Information whether the product can be returned in the given location. |
| `Order to supp.` | Information whether the product can be ordered to supplier for the given location. |
| `Filter` | Section for filtering the location list. Filters by `Country`, `Name` and `Number` are available. |
| `ACTIVATE ALL` | Button that activates the product for all items according to screen rules and user permissions. |
| `DEACTIVATE ALL` | Button that disables product activity for all items according to screen rules and user permissions. |
Product activity is not the same as product visibility in the product records. A central product can be visible in all locations, but active only in some of them. A local product is visible only in the location where it was created and in subordinate locations, and its activity also needs to be checked separately.
Product activity does not confirm stock level. If you need to check the product quantity in stock, go to [Warehouse stocks](/aquila-store-user-manual/products-and-product-records/warehouse-stocks.md).
### When to use
Use this procedure when you need to check whether the product should be visible on POS or available in sale, return or order for a specific location.
### Steps
1. Open `Administration -> Dictionaries -> Products`.
2. Search for the product.
3. Open product details.
4. Go to the `Availability` tab.
5. In the `Name` column, find the correct location or location group. If needed, use the filter by `Country`, `Name` or `Number`.
6. Check the value in the `Activity` column.
7. If the product should be available in this location, set the correct values in the `Activity`, `Sale`, `Return` or `Order to supp.` columns, according to the organization's process.
8. Save the change if the screen requires it.
### What to watch out for
* A product can exist in central product records, but not be active for a given location.
* A local product may not be visible in a parent or parallel location, even if it exists in the system.
* Lack of activity can cause the product not to be visible on POS for the selected location.
* Product activity for a location can affect POS, sales, returns, orders and reports.
* Check stock levels in the `Warehouse stocks` tab, because `Availability` does not confirm the quantity available in stock.
* Product visibility can also depend on price, POS configuration, synchronization and user permissions.
* For a service desk report, note the product, location and process in which the product is not visible or does not work.
### Related pages
* [Searching for a product](/aquila-store-user-manual/products-and-product-records/searching-for-a-product.md)
* [Editing a product](/aquila-store-user-manual/products-and-product-records/editing-a-product.md)
* [Warehouse stocks](/aquila-store-user-manual/products-and-product-records/warehouse-stocks.md)
* [Product groups](/aquila-store-user-manual/products-and-product-records/product-groups.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/availability.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.
