> 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-transactions/faq-on-material/how-to-check-stock-levels.md).

# How to check stock levels?

To check stock levels in the system, you can choose from a few different methods depending on whether you need a quick store check, a specific item lookup, or an overall stock summary report:1. Check Stock (Transaction)Use this option to quickly review and verify the current item quantities available in a specific store:

1. Go to Transaction > Check Stock.
2. Click on CC Store Name and select the desired store.
3. Select the Date range and click the Check button to view current stock levels.

2\. Item Stock Query (Queries)Use this option to search stock details for a specific product:

1. Go to Queries > Item Stock Query.
2. Click the Item Search icon and choose the item name.
3. Click the Display button to view the stock status.

3\. Stock Summary (Reports)Use this report to view a full overview of current stock quantities, rates, and total values:

1. Go to Reports > Stock Summary.
2. Use the Funnel Filter to narrow down results by product or product group if necessary.
3. Click the Display button to view the report. You can also print or export it to Excel


---

# 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-transactions/faq-on-material/how-to-check-stock-levels.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.