> 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/bulk-shipment-template.md).

# Bulk Shipment Template

## Overview

Use the bulk shipment template to create several stock shipments in one upload.

Each row defines a shipment to a receiving facility. Add valid facility and commodity codes, then specify the quantity to dispatch. You can optionally associate a shipment with an existing campaign.

Ensure the issuing facility has enough available stock before submitting the template.

## Details

<table><thead><tr><th width="178.12109375">Field</th><th>Description</th></tr></thead><tbody><tr><td>Facility code</td><td>The receiving facility's code. Must already exist in master data.</td></tr><tr><td>Commodity code</td><td>The commodity being dispatched. Must already exist in master data.</td></tr><tr><td>Quantity</td><td>Must be numeric and greater than zero. Cannot exceed the issuing facility's available stock at time of submission.</td></tr><tr><td>Campaign identifier</td><td>Optional, but if provided, must be a valid, existing campaign.</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 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/bulk-shipment-template.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.
