> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/advanced-reports/pos-inventory-issue-list.md).
# POS Inventory Issue List
The **POS Inventory Issue List Report** provides detailed information about inventory items issued through the POS system. This report helps users track issued inventory records, monitor stock movement, and review issue-related transactions.
## Steps to View the POS Inventory Issue List
Step 1: Navigate to the **Point of Sale** module and click the **Advanced Reports** menu.
1. Select **POS Inventory Issue List**
2. The **POS Inventory Issue List** screen will be displayed.
Step 2: On the report screen, click on the **Report Type** option.
1. Choose the required report type from the available options.
Step 3: After selecting the required report type, click on the **Display** button.
* The POS Inventory Issue List Report will appear on the screen.
---
# 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://help.rbsgo.com/point-of-sale/point-of-sale-module/advanced-reports/pos-inventory-issue-list.md?ask=&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.
