> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/stock-management/stock-kpi-dashboard.md).

# Stock KPI Dashboard

## Overview

Use this to get a real-time, hierarchy-wide view of stock position without waiting for manual reports.

{% hint style="info" %}

#### What is on the dashboard

**Summary indicators:** Total Stock Received, Issued, Returned, Available Balance, Facilities with Low Stock, Facilities with No Stock.

**Stock Position Table:** one row per facility or distribution point, with columns for State, LGA, Ward, Health Facility, DP, Qty Received, Qty Issued, Qty Returned, Available Balance.

**Risk and exception flags:** facilities are automatically highlighted where balance is below the configured minimum threshold, issued quantity is far higher than received (an anomaly), no transactions have been recorded for a configurable period, or returns exceed a configurable percentage of issued stock.
{% endhint %}

## Steps

{% stepper %}
{% step %}

### Apply filters

Filter by Campaign, Commodity, State, LGA, Ward, Health Facility, or Date Range. Filters recalculate the KPIs and persist for your session.

<div align="left"><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FY5gsD05FsiZA5Ts8HRxZ%2Funknown.png?alt=media&amp;token=5db49672-cab5-4c25-9d4d-2e44e41ced8d" alt="" height="298" width="623"></div>
{% endstep %}

{% step %}

### Drill down

Click through State, LGA, Ward, Facility, Transaction List. Clicking any row opens that facility's stock details and transaction history.
{% endstep %}
{% endstepper %}

The dashboard requires an internet connection. If you go offline, it displays the last refresh timestamp and disables filters and refresh until you reconnect.

<div align="left"><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FWmUvwAb6YGBKpxRBWMtR%2Funknown.png?alt=media&amp;token=6c36b39f-4819-410b-a402-a287e08e659b" alt="" height="297" width="617"></div>

<br>


---

# 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.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/stock-management/stock-kpi-dashboard.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.
