> 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/offline-stock-issue-and-accept-using-qr-code.md).

# Offline Stock Issue & Accept Using QR Code

## Overview

This is for the last-level Warehouse Manager and the Distributor, who often work without connectivity.

## Steps

{% stepper %}
{% step %}

### Issue stock offline

Warehouse Manager issues stock offline. Issuing stock has never required internet. The app generates a QR code representing the transaction.
{% endstep %}

{% step %}

### Scan QR code

Distributor scans the QR code. Go to Scan Stock Receipt and scan the Warehouse Manager's QR code to accept the stock. This works fully offline; no network connection is needed for the Distributor to accept.
{% endstep %}

{% step %}

### Sync online&#x20;

Sync when back online. Up-sync your transactions before you clear app storage or uninstall the app, or the offline transactions will be lost. A push notification will auto-trigger a download of any incoming stock once you are back online. If you miss it, use the Downsync card (Section 9) to recover it manually.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Note:** The last-level Warehouse Manager's own acceptance step, receiving stock issued to them, still requires an internet connection. This is unchanged. Only the Distributor's acceptance step works via offline QR scan.
{% 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/offline-stock-issue-and-accept-using-qr-code.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.
