> For the complete documentation index, see [llms.txt](https://ynteq.gitbook.io/ynteq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ynteq.gitbook.io/ynteq-docs/ynteq-features/managing-spare-parts.md).
# Managing Spare Parts
Within the Ynteq CMMS you can manage your spare parts inventory and make sure that you always have the right spare parts in-place, and won’t become blocked in your maintenance activities due to missing parts.
Some features we would like to highlight:
1. You can filter spare parts based on the warehouse location, associated vendor as well as spare parts that have a restock needed (see 3)
2. When you select a spare part you inspect detailed part information where you can see in which assets they are used, where they are stored, where you’ve purchased them and where they are located.
3. When you use a spare part, you can add them to your work order and the inventory levels are automatically adjusted (see work order execution topic). If you don’t use the spare part for a work order, you can also adjust the inventory levels here manually. When you are below the minimum stock level, a red exclamation mark indicates that restocking is needed.
---
# 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://ynteq.gitbook.io/ynteq-docs/ynteq-features/managing-spare-parts.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.