> 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/dispatch-bulk-stock.md).

# Dispatch Bulk Stock

Bulk stock dispatch via Console (Excel upload)

## Overview

Use the bulk stock dispatch option when you need to dispatch stock to many facilities at once. For example, a national-level dispatch to 30 or more State warehouses, instead of recording each transaction one at a time.

The Bulk Shipment Template is a standard file for recording each stock dispatch. Complete one row for each facility and commodity, then upload the file to create all dispatches together.

{% hint style="info" %}
**Before you begin:**

Bulk upload only works with the standard Bulk Shipment Template. It is a system-controlled file and must not be restructured. Bulk upload is not supported offline.
{% endhint %}

## Steps

{% stepper %}
{% step %}

### Log in and open the upload screen

Log in to HCM Admin Console (or the Commodity Management web module) with your Campaign Manager, Logistics Manager, or State Warehouse Manager credentials.
{% endstep %}

{% step %}

### Download the Bulk Shipment Template

Click Download Template. This gives you the standard Excel or CSV file with columns for receiving facility code, commodity code, and quantity.

<div align="left"><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FCO6sF8eEePKO3NulNAQD%2Funknown.png?alt=media&amp;token=5f3ca5bb-6f35-4355-a46c-3a0262dbd8c6" alt="" height="289" width="549"></div>
{% endstep %}

{% step %}

### Fill in the template

One row equals one stock issuance transaction to one facility. Fill in the receiving facility code, commodity type, and quantity for every dispatch. Every row needs valid facility and commodity codes, a quantity greater than zero, and a receiving facility within your permitted hierarchy.

<div align="left"><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2Fbt27PxKnkbwqih3xwUWQ%2Funknown.png?alt=media&amp;token=78c224fa-7f6e-47ea-8562-f4e8b9dd7ded" alt="" height="265" width="554"></div>
{% endstep %}

{% step %}

### Upload the file

Return to the console and upload your completed file.

<img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FoBEbzwbWZNBrs7smmVgW%2Funknown.png?alt=media&amp;token=37ba7631-03e8-4755-beea-7b099ca2ae89" alt="" data-size="original">
{% endstep %}

{% step %}

### Review the preview screen

The system shows every parsed row marked Valid, Warning, or Error. Correct invalid rows directly where possible, remove rows you do not want to submit, or download the error report to fix offline and re-upload.
{% endstep %}

{% step %}

### Submit

Submission is only enabled once all blocking errors are resolved. On submission, the system creates one transaction per receiving facility, each with its own unique transaction reference, all linked under a single Bulk Upload Reference ID.
{% endstep %}
{% endstepper %}

{% hint style="info" %}

#### Common errors

* Missing mandatory columns, wrong column order, or an altered template structure will cause the whole file to be rejected.
* A facility or commodity code that does not exist in master data will flag that row as an error.
* Duplicate rows (same facility and same commodity) are flagged for review.
* Insufficient stock is re-validated at the moment of submission. A row that looked valid in preview can still fail if the available balance changed in the meantime.
  {% endhint %}

If you sent the wrong stock: issued quantities cannot be edited directly. Use the stock return flow to correct it.


---

# 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/dispatch-bulk-stock.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.
