# Inventory splitting

### How does it work?

When splitting an inventory, the original inventory has its quantity decreased. A new inventory is then created for the quantity difference. This new inventory copies over nearly all of the properties from the original inventory. It also maintains a link to original inventory that is called `originPartInventoryId` in the API.

<figure><img src="/files/PjUV43pzKHqjPG9knuZq" alt=""><figcaption></figcaption></figure>

### Initiating an inventory split

You can manually split an inventory via the inventory or receipts views.

When splitting, you have 2 options:

1. **Split** - Splits a single item into 2 items by specifying a quantity. Example: Inventory is quantity 10 and you want to split off one for qty 3.
2. **Split Many** - Splits a single item into multiple items by specifying the number of items desired. Example: Inventory is quantity 10 and you want to create 10 inventories of quantity 1.

<figure><img src="/files/p4KaeLaCle0p2NRwf48X" alt=""><figcaption></figcaption></figure>

### Automated splitting

ION will automatically split inventory when partially installing, kitting, or scrapping a quantity. This occurs to keep the location/status of inventory items correct. For instance, if you have an inventory for quantity 2 and you kit 1 item, the inventory will split. Now the item that has been kitted will properly show a "Kitted" status and its location can be updated from the original.

For the purpose of barcodes, it is good to know how the new inventory is created. This table below shows how the inventory is created:

| Action                 | How should the inventory split take place |
| ---------------------- | ----------------------------------------- |
| partial kit            | New inventory for the kitted item         |
| partial unkit          | New inventory for the unkitted item       |
| partial install        | New inventory for the installed item      |
| partial uninstall      | New inventory for the uninstalled item    |
| partial scrap          | New inventory for the scrapped item       |
| partial unscrap        | New inventory for the un-scrapped item    |
| direct inventory split | Qty to split becomes new inventory item   |
| partial receive        | New inventory for received item           |
| partial unreceive      | New inventory for unreceived item         |

### Carrying information across split inventories

Inventory relates to a lot of different objects in ION: runs, kits, issues, purchase lines, etc. Runs and issues only allow 1 inventory item to be related to them. When an inventory that is tied to a run (or issue) is split, it will use the **origin part inventory** information to maintain a reference to the run/issue.

For the inventory items shown below, the inventory was added to a run and then there was an issue tied to it. When that inventory was split, the new inventory created maintains a reference to both the run and the issue (see "Appears on" and "Issues" columns).

<figure><img src="/files/o4vtkOKzcCnAXe5mx0Ma" alt=""><figcaption></figcaption></figure>

This is also reflected on the aBOM within the trace view:

<figure><img src="/files/tzfOv5wwXkcNLtaojIe8" alt=""><figcaption></figcaption></figure>

### What happens to installed inventory and build requirements?

Please review [Split Inventory on a Run](/features/runs/split-inventory-on-a-run.md) for more information on splitting an inventory item with installed inventory on the aBOM.


---

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