> For the complete documentation index, see [llms.txt](https://manual-v2.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual-v2.firstresonance.io/supply-chain/inventory.md).

# Inventory

In ION, an **inventory item** is a persistent digital twin representing a specific quantity of a part—typically a single serial-numbered unit or a lot-tracked batch.

* **Creation and Persistence:**\
  The inventory item record is created at the earliest opportunity (e.g., the moment a purchase line is entered) and persists throughout the lifecycle of the corresponding physical piece.
* **Rich Metadata:**\
  Each item carries detailed metadata, including:
  * Location
  * Supplier information
  * Cost
  * Lot or serial numbers
  * Quantity
  * Organizational defined attributes
* **Lifecycle Statuses:**\
  Rather than being deleted when consumed, each inventory item transitions through clearly defined statuses:

  * On Order
  * Available
  * Work In Progress (WIP)
  * Kitted
  * Installed
  * Scrapped
  * Unavailable

  This ensures that you can always determine the current location and state of an item, answering questions such as "Where is serial XYZ right now?" and facilitating accurate audits of each hand-off.

  The **Unavailable** status is also used by the issue disposition workflow. When inventory is associated with an issue, a disposition type configured as **Release on Resolve** or **Permanently Unavailable** can move that inventory to **Unavailable** while the issue is being processed or as part of the final disposition. For more detail, see [Disposition Types](/quality/disposition-types.md).
* **Traceability and Searchability:**\
  Multiple inventory items can exist simultaneously for the same part number across various locations or tracking schemes, providing granular traceability without sacrificing ease of search across the factory.


---

# 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://manual-v2.firstresonance.io/supply-chain/inventory.md?ask=<question>&goal=<endgoal>
```

`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.