Before a build starts, the parts have to be gathered from storage. Doing that from a BOM line by line — find the part, move the stock, repeat — is slow and easy to get wrong. Kitting does it in one operation: you choose a project, a build quantity, and a staging location, and PartsBox computes everything the build needs and moves the stock there in a single batch.
The computation is the same one that builds use. Quantities include attrition, substitutes and meta-parts resolve to the concrete parts you have in stock, and stock is taken from sources in FIFO order by default. You can review every BOM entry before anything moves: pick different sources for a specific entry, exclude an entry, or override its quantity. Stock already in the staging location counts as available and stays where it is.
The pick list has one row for each part, location, and lot, sorted by storage location, so you visit each location once, even when one lot covers several BOM lines. Every row shows the designators it covers (for example C3 C7 R12), the quantity to pick, and the lot. The build worksheet shows the same kit per BOM entry, for use during assembly. Both can be checked off on screen, and both export to PDF with a check-off box on every printed row.
When stock is missing, PartsBox shows which entries are short and by how much. You can kit what is available and order the rest; the missing entries are reported and marked in the pick list.
Kitting only moves stock — it does not consume anything and it does not create a build record. Every move is recorded in stock history. When the parts are staged, start the build with a source filter restricted to the staging location, or ship the kit to wherever assembly happens.
Kitting starts on the Production plan.