> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/data-integrations/retail-data/inventory-and-availability.md).

# Inventory & availability

What's on hand, on order, and in transit at each retailer, plus how many stores are stocked.

Inventory & availability shows what stock is sitting where across your retail partners, and how many of their stores actually have your product on the shelf. It's how you catch out-of-stocks and overstock before they show up in your sales.

**Use it to:**

* Find stores and retailers that are out of stock or running low.
* Track how much inventory is on hand, on order, and on its way.
* Estimate weeks of supply so you can flag reorder or overstock risk.
* Monitor how widely your product is stocked across a retailer's stores.

## Inventory position

| Metric                     | What it tells you                                       | Notes                                        |
| -------------------------- | ------------------------------------------------------- | -------------------------------------------- |
| **On hand (units & $)**    | Stock physically in stores and DCs at the snapshot      | Retail value; cost value also where reported |
| **On order (units & $)**   | Ordered by the retailer, not yet received               | Where the retailer reports it                |
| **In transit (units & $)** | On its way to the destination                           | Where the retailer reports it                |
| **Presentation minimum**   | The floor/shelf minimum before a store reads as low     | Where the retailer reports it                |
| **Weeks of supply**        | How long on-hand stock will last at recent sell-through | Derived from on-hand and recent units sold   |

## Store availability

| Metric                  | What it tells you                          | Notes                                            |
| ----------------------- | ------------------------------------------ | ------------------------------------------------ |
| **Stores carrying**     | Stores authorized to carry the item        | Where the retailer reports store counts          |
| **Stores in stock**     | Stores that currently have it on the shelf | Where the retailer reports store counts          |
| **Stores out of stock** | Stores that should carry it but are out    | Where the retailer reports store counts          |
| **In-stock rate**       | Share of carrying stores that are in stock | Derived from stores in stock and stores carrying |

{% hint style="info" %}
**Snapshots.** Inventory is a point-in-time snapshot for each period, so numbers show the stock position as of that week or month end, not a running total.
{% endhint %}

Inventory & availability is available for every connected retailer at the banner level. Store-by-store inventory is available where the retailer reports individual stores.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.drivepoint.io/data-integrations/retail-data/inventory-and-availability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.