> For the complete documentation index, see [llms.txt](https://manual.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.firstresonance.io/features/parts-and-trace/inventory/inventory-status.md).

# Inventory status

## Overview

ION shows all part instances on the inventory screen even if they been consumed (installed, kitted) or scrapped. This allows for maximum traceability of parts as they move through the factory. Additionally, ION creates "inventory" as early as possible in the process, which is why inventory is created for runs and purchases before they are completed.

In order to manage this and allow you to see what inventory is physically available, ION uses an inventory status. The inventory status is calculated based on relationships in ION. Below shows the different options and logic associated with each.

<table><thead><tr><th width="146.33333333333331">Status</th><th>Meaning</th><th>Logic</th></tr></thead><tbody><tr><td><strong>Scrapped</strong></td><td>Full quantity is scrapped.</td><td>Scrapped quantity on the inventory record is equal to the inventory quantity.</td></tr><tr><td><strong>Installed</strong></td><td>Installed onto an assembly.</td><td>Full quantity is installed onto a parent aBOM.</td></tr><tr><td><strong>Kitted</strong></td><td>Actively kitted.</td><td>Kitted to an open kit (kit status not complete) AND not installed.</td></tr><tr><td><strong>WIP</strong></td><td>Linked to an active or failed run.</td><td>Inventory is attached to a run that is in a status of <code>todo</code>, <code>in progress</code>, <code>redline</code>, <code>hold</code>, or <code>failed</code>.</td></tr><tr><td><strong>On Order</strong></td><td>Linked to an active purchase.</td><td>Inventory is attached to a purchase line that is in a status of <code>draft</code>, <code>requested</code>, <code>approved</code>, or <code>ordered</code>.</td></tr><tr><td><strong>Unavailable</strong></td><td>Physically in inventory, but not able to be consumed based on location restrictions.</td><td>Inventory is none of the above states and the location that it is located in has its inventory availability turned off. OR the inventory quantity is 0.</td></tr><tr><td><strong>Available</strong></td><td>Physically available to consume.</td><td>Inventory is none of the above states.</td></tr></tbody></table>

The above table is sorted in order of how it is executed in the logic. For instance, if an item is `installed` and `kitted`, the `installed` status will take precedence.


---

# 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://manual.firstresonance.io/features/parts-and-trace/inventory/inventory-status.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.