Overview - ION Manual
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
A kit is a request for a defined set of parts pulled from inventory and delivered together to a location. It records what should be in it, the specific lots and serials that fulfill it, where it stages and delivers, and its status. A kit does not create or consume parts. It reserves existing inventory and moves it, so a kitted unit is unavailable to other demand until the kit completes. Most kits go to a run, where the kit reserves components against that run’s build. A kit can also serve engineering testing, line-side replenishment, or any workflow that needs a known set of parts in one place.
Requesting versus fulfilling
A kit has two sides that different people work. The requester defines what the kit needs and where it goes. The inventory team fulfills it by assigning specific lots and serials to each requested part, and can pull the oldest inventory first across the whole kit. Picking can be partial, but a kit can’t be delivered until every line is fully kitted. See Create and fulfill kits. A kit tracks two locations. The Staging location is where parts sit while the kit is picked. The Destination (the kit’s delivery location) is where they end up once the kit is delivered.
Statuses
A kit moves through the statuses below to coordinate the requester and the inventory team. Each status offers one forward action (Submit Request, Start Picking, then Deliver or Complete), and each status drives what happens to the kitted inventory. A kit tied to a run passes through Delivered on its way to Completed; a kit with no run goes straight to Completed.
| Status | What it’s for |
|---|---|
| Draft | The default for a new kit, and the only status where parts can be added, edited, or removed. The requester fills in the parts needed and sets the kit’s Destination. |
| Requested | The requester has finished defining the kit. Inventory teams filter for requested kits to action, and the kit can be assigned to a team member or a team. A destination is required before picking can start. |
| In Progress | The kit is being fulfilled. Kitted inventory takes the Kitted status. |
| Delivered | The kit has been delivered. Its Current Location updates to the Destination, so all inventory in it moves there automatically. |
| Completed | Returns a kit, or part of it, to the warehouse. Inventory that wasn’t installed is marked available. To move that inventory to one location in a single action, use Stage Inventory. |
| Canceled | The kit is no longer needed. |
To move a kit backward, use its More actions (⋯) menu on the Kitting page: Return to Draft for a requested or in-progress kit, Reopen as In Progress for a delivered kit, Reopen as Delivered for a completed kit tied to a run, and Reopen as Draft for a canceled kit. Cancel Kit is available until the kit is completed or canceled.
Kitting to a run
When a kit is tied to a run, the parts it reserves are subtracted from inventory and attached to that run as soon as they are kitted, so you can plan assemblies without double-counting inventory. You can auto-fill the request from the run’s aBOM, and a single request creates one kit per destination. See Kit parts to a run.
Kanban kitting
A kanban kit is a reusable container that cycles between inventory and the line for high-volume repeat builds. The same kit pattern is pre-assembled into the container, sent to the line, emptied, and returned to inventory to be refilled. This fits discrete BOM-controlled parts consumed in a repeatable pattern, not high-velocity consumables. See Kanban kitting.