> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/core-concepts/dashboards/report-library/ecommerce-performance/inventory.md).

# Inventory

## Overview

The **Inventory** dashboard gives you insight into which SKUs you have a lot of (known as "running long") and which SKUs you are running low on, as well as recent sales velocity.  The visualizations contained in this dashboard can help you answer the following questions:

* Do I need to buy more of a specific SKU?
* Which SKUs am I running long on? 
* How do I optimize my business based on inventory quantity and sales velocity?

<div align="left" data-full-width="true"><figure><img src="/files/coDFBLtO6EK2z1zn8BxM" alt=""><figcaption></figcaption></figure></div>

## Data sources

All of the visualizations in this dashboard are powered by the **Inventory Levels** explore, which will contain data from any commerce platform you have integrated to Daasity

## Setup

The **Inventory** dashboard will be available in your dashboard list by default.


---

# 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://help.daasity.com/core-concepts/dashboards/report-library/ecommerce-performance/inventory.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.