> 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/access/public-health-product-suite/health-campaign-management-hcm/specifications/functional-specifications/inventory.md).

# Inventory

## Overview

The **Inventory** feature in the Health Campaign Management (HCM) system facilitates the tracking of health commodities (e.g., tablets, syringes) across multiple locations. It ensures transparency, accuracy, and accountability in stock usage during health campaigns.

## Specifications

<table><thead><tr><th width="190">Name of the field</th><th width="336">Description</th><th width="121">Mandatory</th><th>Input</th><th width="118">Data type</th><th>Minimum length</th><th>Maximum length</th><th width="146">Validation</th><th width="193">Comments</th><th>Need data from program/state</th></tr></thead><tbody><tr><td></td><td><strong>Stock details</strong></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Product variant ID</td><td>The product variant that is being transferred.</td><td>Mandatory</td><td>User</td><td>String</td><td>2</td><td>64</td><td></td><td></td><td>No</td></tr><tr><td>Quantity</td><td>The number, or quantity, or the count of units of the product variant that are being transacted.</td><td>Mandatory</td><td>User</td><td>Integer</td><td></td><td></td><td></td><td>Outputs from the micro-plan.</td><td>Yes</td></tr><tr><td>Reference ID</td><td>The reference entity for which the stock transfer is taking place.</td><td>Mandatory</td><td>User</td><td>String</td><td></td><td></td><td></td><td></td><td>No</td></tr><tr><td>Reference ID type</td><td>The entity type that the reference ID refers to. For example, 'Project'.</td><td>Mandatory</td><td>User </td><td>String</td><td>2</td><td>64</td><td>String</td><td></td><td>No</td></tr><tr><td>Transaction type</td><td>The kind of transaction that is taking place:  Received, dispatched.</td><td>Mandatory</td><td>User</td><td>String</td><td></td><td></td><td></td><td></td><td>No</td></tr><tr><td>Transaction reason</td><td>The status of the transaction: Received, returned, loss.</td><td>Mandatory</td><td>User</td><td>String</td><td></td><td></td><td></td><td></td><td>No</td></tr><tr><td>Transacting party ID</td><td>The ID of the party from/to which the product variant stock is being transferred.</td><td>Mandatory</td><td>User</td><td>String</td><td>2</td><td>64</td><td></td><td></td><td>No</td></tr><tr><td>Transacting party type</td><td>The type of entity that the transacting party ID refers to. For example, 'Warehouse'.</td><td>Mandatory</td><td>User</td><td>String</td><td>2</td><td>64</td><td></td><td>The list of warehouses/facilities and their type to be provided by the program/state during impel.</td><td>No</td></tr><tr><td></td><td><strong>Stock reconciliation</strong></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Physical count</td><td>The count of units of the product variant as a result of a physical count.</td><td>Mandatory</td><td>User</td><td>Integer</td><td></td><td></td><td></td><td></td><td>No</td></tr><tr><td>Calculated count</td><td>The count of units of the product variant that is calculated from the stock movements.</td><td>Mandatory</td><td>User</td><td>Integer</td><td></td><td></td><td></td><td></td><td>No</td></tr><tr><td></td><td><strong>Facility details</strong></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Facility ID</td><td>The ID of the facility where the stock of the product variant is being transferred.</td><td>Mandatory</td><td>System</td><td>String</td><td>2</td><td>64</td><td></td><td>List of warehouses/facilities and their type to be provided by the programme/state during impel.</td><td>No</td></tr><tr><td>Facility name</td><td>The administration name of the facility.</td><td>Mandatory</td><td>User</td><td>String</td><td>2</td><td>2000</td><td></td><td></td><td>Yes</td></tr><tr><td>Is it permanent?</td><td>Whether the facility is permanent or not.</td><td>Mandatory</td><td>User</td><td>Boolean</td><td></td><td></td><td></td><td></td><td>Yes</td></tr><tr><td>Usage</td><td>The purpose of the facility: Storage warehouse, medical facility, sewage treatment plant.</td><td>Mandatory</td><td>User</td><td>Dropdown</td><td></td><td></td><td></td><td></td><td>Yes</td></tr><tr><td>Storage capacity</td><td>Physical storage capacity of the facility in cubic metres.</td><td>Optional</td><td>User</td><td>Numeric</td><td></td><td></td><td></td><td></td><td>Yes</td></tr><tr><td>Address</td><td></td><td>Mandatory</td><td>User</td><td>String</td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>


---

# 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.digit.org/health/access/public-health-product-suite/health-campaign-management-hcm/specifications/functional-specifications/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.