# Kitting

Kitting in ION allows you to request inventory to be delivered to a particular location. You will select which parts and quantities you need, and ION automatically selects inventory to be picked and delivered based on FIFO methodology. The kit also allows you to manually select specific lot number or serial numbers to be delivered. Once the kit is delivered, the inventory is moved to the delivery location.

#### Use cases for kitting include:

1. Delivering material for a particular build run.
2. Delivering material to a lineside rack to be used for multiple builds.
3. Moving parts from the incoming receiving rack to a warehouse bin.
4. Reserving parts for a R\&D test or run.

## Kit Statuses and Workflows

Below are the various stages of a kit and how to make the most of them. Remember, you can move from any status to any status in ION

**Draft:** This is the default status of a newly created kit. As a manufacturing engineer or technician, you should use this status when filling out parts that you need at the lineside or at any other location. At this stage, set the *deliver to location* of the kit.

**Requested:** Once the creator of the kit has finished, determine what parts are needed and where, then set the status of the kit to requested. Inventory teams can filter for kits that are requested to understand which are ready to be actioned on. At this stage, you can assign the kit to the appropriate team member to fulfill.

**In Progress:** Once you are kitting the relevant inventory for a kit, mark the kit as in progress to show both other inventory personnel and the kit requestor that the kit is already being worked on. Kitted inventory will be marked with the [kitted](broken://pages/wA8aTiYqIH0THP2eL5ra) status.

{% hint style="info" %}
The kit will automatically move to In Progress if you kit any material when the kit is in a Requested status.
{% endhint %}

**Delivered:** After delivering the kit, mark the kit as delivered. This will set all of the inventory in the kit to the location of the [kit's *deliver to location* automatically.](broken://pages/k3i98KMvXLx8tBZDxvar)

{% hint style="info" %}
See [Broken mention](broken://pages/k3i98KMvXLx8tBZDxvar) for more details.
{% endhint %}

**Completed:** If you need to return a kit ot part of a kit back to your warehouse, mark the kit as completed. This will mark the inventory that has not been installed as available. This however will not change the location of the inventory that is being returned. You can use the current location of the kit to change location of the kitted inventory all at once.

**Canceled:** When a kit is no longer needed, mark it as canceled.

### New vs Legacy

Based on the ability to split kits, auto-selected inventory, show total inventory counts, and more, we are predicting a 3 - 5x improvement on kits with larger improvements coming from larger kits. See this video for a comparison between the two interfaces.

{% embed url="<https://www.loom.com/share/7853483fc7ff485c9ab381189b3c6742?sid=3aacae3c-b24e-4dd6-a8fc-c205e5fda891>" %}


---

# Agent Instructions: 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://manual-v2.firstresonance.io/supply-chain/kitting.md?ask=<question>
```

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.