> 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/transaction-and-warehouse-tabs.md).

# Transaction & Warehouse Tabs

## Overview

Commodity Management is the web module for tracking every commodity transaction and warehouse stock position across the supply chain.

## Details

{% hint style="info" %}

#### Tab 1: Transaction Overview

Metric cards: Total Number of Warehouse Managers, Number Synced, and Sync Rate percentage.

\
Metric cards: Total Transactions, Total Completed, Total Cancelled, Total Pending.

\
Full transaction list: Transaction Reference Number, Creation Date, Sent From, Sent To, Created By, Status, and Transaction Type (Logistics or Reverse-Logistics).
{% endhint %}

{% hint style="info" %}

#### Tab 2: Warehouse Stock Overview

Lists every warehouse, health facility store, or distribution hub you have visibility into (your own boundary and everything below it): Warehouse Name, Warehouse Type, full Boundary, Commodity, and Current Stock.

\
Action buttons: Download Bulk Shipment Template, Upload Bulk Shipment Template, and Ship Commodity&#x20;

\
Filters let you drill down to LGA, Ward, and Health Facility level.
{% 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/transaction-and-warehouse-tabs.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.
