> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/core-commerce/product-user-guide/availabilities.md).

# Availability and Stock Levels

Availability service allows you to manage product availability, location, popularity, and stock levels.

Here you can find an overview of the Emporix API Availability Service, along with its features and benefits.

{% hint style="info" %}

* Looking for code tutorials? Check out the [Availability Service guide](/api-documentation/api-guides/orders/availability/availability.md).
* Looking for API reference? Check out the [Availability Service](/api-documentation/api-guides/orders/availability.md) in the Emporix API Reference.
  {% endhint %}

### Purpose

The Availability Service helps you manage information about the availability of products sold by your business. To make picking and packing easier, you can also manage physical location of products on particular sites.

### Features

The Emporix API Availability Service introduces a set of features that make product management easier:

| Feature                   | Description                                                                                                                                                |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Availability**          | Manage information about availability of products sold by your business.                                                                                   |
| **Product bundles**       | Automatically calculate a product bundle's stock level based on the lowest stock level of the bundled products.                                            |
| **Location** (deprecated) | Manage the exact location of products inside a warehouse or a store — zones, racks, shelves, and bins.                                                     |
| **Mixins**                | Extend availability records with custom structured attributes. View and maintain the extra fields in the Management Dashboard **Availability Schema** tab. |
| **Popularity**            | Store information about a product's popularity to recommend best-selling products to your customers.                                                       |
| **Stock levels**          | Manage stock levels of products at different sites.                                                                                                        |
| **Search functionality**  | Quickly retrieve information about location and availability of desired products.                                                                          |

{% hint style="info" %}
To create mixin schemas, see [Mixin Schemas](/user-guides/management-dashboard/settings/mixin-schemas.md). To fill in availability mixin fields, see [Products](/user-guides/management-dashboard/products-module/products.md).
{% endhint %}


---

# 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://developer.emporix.io/user-guides/core-commerce/product-user-guide/availabilities.md?ask=<question>&goal=<user_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.