Kitting & Manufacturing
Kit and BOM returns policy
Choose whether returned kits come back as individual components or as a single re-assembled unit. Lot-controlled recalls handled automatically.
Two return modes
Every kit and BOM has a ReturnPolicy setting with two modes:
components or assembled_kit. The choice controls what happens when the return is marked received in your warehouse—specifically, how the inventory is restocked and which FIFO cost layer the unit goes back onto.Mode: components
In
components mode, the return receiving UI presents one row per component SKU. The receiver scans (or counts) each part as it goes back on the shelf. Each component's on-hand quantity is incremented individually, and a new FIFO layer is created for each part at its most recent layer cost—not the kit's original cost. Use this mode when components are easy to separate, individually sellable, or when not all parts may come back (e.g. customer returns the scooter but kept the spare hex keys).Mode: assembled_kit
In
assembled_kit mode, the return is treated as a single re-assembled kit unit. On receipt, the kit SKU's synthetic stock goes up by 1, but underneath ShipWave creates a special FIFO layer that holds the entire kit at the original sold cost. The next time the kit ships, ShipWave preferentially draws from this layer (cheaper than re-assembling from raw components). Use this mode when the kit can be inspected, re-sealed, and resold as-is—e.g. a gift box returned in original packaging.Choosing the right mode per kit
Default to
components for utility kits (hardware sets, accessory bundles) where parts are easy to separate. Default to assembled_kit for high-touch retail bundles (gift boxes, branded starter kits) where re-sealing is reasonable. You can change the mode at any time without affecting historical returns. The setting lives on the kit's ReturnPolicy panel.Recall flow for lot-controlled components
If a component is lot-controlled and you mark a lot as recalled, ShipWave finds every kit and BOM that consumed units from that lot and surfaces them in the Recall queue. For each affected order, you can: (a) push a customer notification email, (b) auto-issue a replacement order using the replacement-gated returns flow, or (c) mark the unit as quarantined if it came back through a return. This works the same whether the component was consumed at ship time (kit) or at MO completion (BOM).
FAQs
What if a customer returns only part of a kit?
Use components mode and just receive the parts they actually shipped back. The other components stay in your "loss" column for that order.
Can I switch a return's mode after it's created?
Yes, until the return is marked received. After receipt, the inventory is committed.
How does this interact with replacement-gated returns?
It composes cleanly. The replacement-gated flag is about reminding the customer to ship the unit back; the mode is about what happens once it arrives. See <a href="/help/replacement-gated-returns">Replacement-gated returns</a>.
Do BOMs support both modes too?
Yes. assembled_kit treats the finished good as resellable; components disassembles it back into raw parts. Disassembly creates a "reverse MO" record so you can audit it later.
More in Kitting & Manufacturing
- Kits vs. BOMs: which one should you use?
Understand the difference between virtual kits assembled at ship time and pre-manufactured finished goods built from a Bill of Materials.
- Creating a kit
Build a virtual bundle from existing components. Availability and component decrement happen automatically at ship time.
- BOMs and manufacturing orders
Define a Bill of Materials, issue a manufacturing order, and track labor + scrap as components are consumed and finished goods are produced.
- Substitution groups
Let any of several interchangeable SKUs satisfy a kit or BOM component slot. Track which one actually shipped for accurate cost and warranty data.