> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/assets/understanding-the-inventory/manage-inventory.md).
# Manage Inventory
Inventory in equipme is not managed by editing fields or maintaining records manually.\
It is managed through actions that reflect real operational events.
Each action available in the Inventory view represents a meaningful step in the lifecycle of an asset. When you confirm receipt, store a service, assign an add-on, or request a successor service, you are not changing data for the sake of documentation. You are describing what actually happened, and equipme updates the inventory state accordingly.
This action-based approach ensures that inventory remains consistent and reliable. Assets move forward because something happened in the real world, not because someone adjusted a value in the system. Inventory follows reality instead of trying to predict or model it.
Managing inventory therefore means choosing the right action at the right moment. You confirm deliveries, transition assets between usage and availability, or continue a lifecycle when a replacement is required. The system takes care of keeping the inventory state in sync.
#### Working with inventory on the service level
Inventory management in equipme does not end in the inventory overview.
Each inventory item is linked to a concrete service instance. By opening an inventory entry, you move directly into the service details of that asset. This is where inventory, service configuration, assignment, and lifecycle come together.
On the service level, you see the full context of the asset. This includes its current status, selected options, billing information, and assignment to an employee, location, or group. Inventory is not separated from the service. It is embedded within it.
Most inventory related decisions are made in this view. Actions such as storing a service, requesting a successor, or extending the lifecycle are performed in the context of the service, not in isolation. This keeps asset management close to how services are actually used and maintained.
By managing inventory through service details, equipme avoids fragmented workflows. You do not need to switch between different areas to understand an asset. Everything relevant lives in one place and stays consistent across inventory, fulfillment, and service management.
---
# 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:
```
GET https://hub.equipme.io/equipme/assets/understanding-the-inventory/manage-inventory.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.