> 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/record-loss-and-excess.md).

# Record Loss & Excess

## Overview

This applies to campaigns where products are packed in a bunch. Sometimes a box has fewer (Loss) or more (Excess) pieces once opened.

## Steps

{% stepper %}
{% step %}

### Count the stock

Open and count the stock. This is done after stock has already been received and accepted, at the point of physically opening and counting a box of stock.
{% endstep %}

{% step %}

### Record loss/excess

Go to Manage Stock and select Record Less/Excess.
{% endstep %}

{% step %}

### Fill the form

Choose whether you are reporting a Loss or an Excess, select the product, enter the quantity, and give a reason.
{% endstep %}

{% step %}

### Save and close

A recorded Loss is immediately deducted from your available balance; a recorded Excess is immediately added. Both appear in the Stock Summary screen.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Tip**

Keep the quantity to single digits when recording a Loss or Excess. This limit reduces data-entry errors.
{% 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://docs.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/stock-management/record-loss-and-excess.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.
