> 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/view-available-stock-balance.md).

# View Available Stock Balance

## Overview

Your available stock balance is visible directly at the top of the stock screen. You no longer need to run a separate reconciliation flow to check it.

## Details

{% hint style="info" %}

#### What you will see per commodity

**Commodity Name:** Example - SPAQ, Nets, Drugs.

\
**Available Balance:** current stock, updated immediately after every transaction (receipt, issue, return, adjustment).

\
**Progress Indicator:** a visual bar showing stock level.

<img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FHj79dfOO4neIzDXqag0q%2Funknown.png?alt=media&amp;token=b3ff91cc-8183-418b-8ed6-03b3596af52a" alt="" data-size="original">

\
**Threshold Indicator:** colour-coded. Red if below the configured minimum, blue if between minimum and maximum, green if above the configured maximum.
{% endhint %}

You will only ever see stock for your own assigned facility or jurisdiction. A Distributor sees their assigned stock, an HFOIC sees facility stock, and a Warehouse Manager sees warehouse stock for their level. A distributor cannot deliver until they have sufficient stock required for an intervention.


---

# 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/view-available-stock-balance.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.
