Inventory splitting

Understand and initiate 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.

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.

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:

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

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

Last updated