Checking must use the kit composition version and record approved substitutions for each component.
Index
A complete kit depends on its component combination, not simply the total number of pieces picked; similar items can produce an incompatible assembly.
The rule that changes the scope
Checking must use the kit composition version and record approved substitutions for each component.
A standard scanner may cover SKU picking; an extension handles equivalents and variable kits when configuration cannot express those rules.
Composition varies by product version, so another order's kit must not become an implicit reference. Staff need to see what is missing from that specific set and confirm similar parts by identifier rather than appearance. If a part is removed after checking, define whether the kit becomes incomplete again. That event differs from returning a surplus item that never belonged to the assembly in the first place.
Specify operational deliverables
- Associate the assembly order with the composition valid when it was released.
- Show shortages and excess by component, keeping picked and returned quantities separate.
- Link a component substitution to its approver and recorded technical reason.
Test the exception before acceptance
In a hypothetical scenario, a component is substituted during picking; the kit must show the approved equivalent and keep its original composition available.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring two similar kits, their component lists and a substitution used in operations.