> 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-specifically-track-items-that-carry-high-unit-costs-for-tighter-financial-controls.md).

# How to specifically track items that carry high unit costs for tighter financial controls?

To view the High Value Stock Items report for tracking items with high unit costs or significant total monetary value, follow these steps:

1. Go to Analysis > High Value Stock Items.
2. Use the Funnel Filter or Group By drop-down options to narrow down your search or filter by specific items and categories.

This report allows you to closely monitor high-cost and critical items to ensure tighter risk management, effective inventory control, and financial oversight.


---

# 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-specifically-track-items-that-carry-high-unit-costs-for-tighter-financial-controls.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.
