> 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/material-management/material-management-module/mm-analysis/non-moving-stock.md).
# Non Moving Stock
The **Non Moving Stock** report provides information about inventory items that have not recorded any consumption, issue, transfer, sale, or stock movement during a specified period. These items remain inactive in inventory and may indicate excess stock, slow-moving stock, or obsolete inventory.
## Steps to View the Non Moving Stock Report
Step 1: Navigate to the **Analysis** menu in the **Inventory** module.
1. Select **Non Moving Stock**.
* The **Non Moving Stock** screen will be displayed.
Step 2: After opening the report page, apply the necessary filters to generate the report.
* The report supports multiple filters, allowing users to customise the output according to their analysis requirements.
1. Use the Funnel Filter
* The **Funnel Filter** allows users to narrow down the report results by applying specific search criteria.
2. Use the Group By Option
* The **Group By** drop-down enables users to organise report data into meaningful categories for easier analysis.
Step 3: After selecting the required filters and grouping options, click **Display** button.
* The system will display the Non Moving Stock report based on the selected criteria.
---
# 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/material-management/material-management-module/mm-analysis/non-moving-stock.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.
