> 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/ph-v1.7/access/public-health-product-suite/health-campaign-management-hcm/inventory-management/user-manual/manage-stocks.md).
# Manage Stocks
This enables a user to manage stocks, besides facilitating stock reconciliation.
## Steps
On this page, the following actions can be performed:
* After a successful login as a warehouse manager, a user lands on the home screen, which consists of **Manage Stock** and **Stock Reconciliation**.
### Manage Stocks
This screen consists of the following types of transactions that take place for the inventory:
* Stock receipt
* Stock issued
* Stock returned
* Stock damaged
* Stock loss
#### Stock Receipt
* When a user clicks on record stock receipt, the warehouse details screen will appear.
* The latitude/longitude captures the geo-location of the warehouse, which can be fetched with the help of the location icon within the field.
* Clicking on the next button will navigate the user to the **Received Stock Details** screen.
* The "Receipt Stock Details" form has some mandatory fields: product, received from the warehouse, and quantity received.
* The optional fields include waybill number, quantity indicated on the waybill, transport type, vehicle number, and comments.
* Clicking on the submit button will take the user to the success page.
#### Record Stock Issued
* This screen captures the mandatory fields: Product, Issued to warehouse, and the quantity.
* The optional fields include waybill number, quantity indicated on waybill, transport type, vehicle number and comments.
* Clicking on the submit button will go to the success page.
#### Returned Stock Details
This screen captures the mandatory fields: Product, returned to warehouse, and quantity returned.
The optional fields are waybill number, quantity indicated on the waybill, transport type, vehicle number, and comments.
Clicking on the submit button will take the user to the success page.
#### Damaged Stock Details
* This screen captures the mandatory fields: Product, damaged during, received from, and quantity damaged.
* The optional fields include waybill number, quantity indicated on the waybill, transport type, vehicle number, and comments.
* Clicking on the submit button will take he user to the success page.
#### Lost Stock Details
This screen captures the mandatory fields: Product, lost during, received from, and quantity lost.
The optional fields are Waybill Number, quantity indicated on the waybill, transport type, vehicle number, and comments.
Clicking on the submit button will take the user to the success page.
### Stock Reconciliation
Click [here](/health/ph-v1.7/access/public-health-product-suite/health-campaign-management-hcm/inventory-management/user-manual/reconcile-stock.md) to learn more about stock reconciliation.
---
# 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/ph-v1.7/access/public-health-product-suite/health-campaign-management-hcm/inventory-management/user-manual/manage-stocks.md?ask=&goal=
```
`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.