Kitting Software for Manufacturers: Kitting vs. Multi-Step BOMs, Explained

The Word "Kitting" Gets Stretched to Cover Too Much

Ask five manufacturers what "kitting software" means and you'll get five different answers. For one, it's bundling three finished SKUs into a gift set at pack time. For another, it's building a sub-assembly on the shop floor that later gets consumed into a bigger product. For a third, it's the whole multi-stage production process — mix, bottle, label, box — that a competitor's marketing page called "kitting" because the phrase tests well in search.

That looseness isn't just a semantics problem. It leads manufacturers toward the wrong tool. A team that actually needs staged production with tracked work-in-progress ends up evaluating something that only bundles finished SKUs at ship time. A team that just needs a simple bundle ends up wrestling with a staged-production system that wants ten fields filled in for something that's really one step.

I've walked enough manufacturers through this exact confusion — usually while they're trying to explain their process to a new software vendor and watching the vendor nod along without really following — that it's worth drawing the line properly. This guide covers what kitting actually is, what multi-step manufacturing actually is, and how Nstock models real staged production: stocked sub-assemblies, pass-through work-in-progress, and the option to produce only partway through a recipe, all from one production order instead of a chain of disconnected ones.

What Kitting Actually Is

At its narrowest and most accurate, kitting is assembling a set of existing, already-stocked items into a single sellable unit at the point of packing or shipping — without a meaningful production process happening in between. A gift box with three finished skincare products and a card. A tool kit with a wrench, two bits, and a case, each already sitting in inventory as its own SKU.

Nothing gets transformed. Nothing has an intermediate identity worth tracking on its own. The kit SKU consumes three, or ten, or twenty component SKUs in fixed quantities, and the moment it's kitted, it exists as one line of finished stock. That's a single-level bill of materials doing exactly what it's built for: one product, one list of components, one deduction event.

If that's genuinely your process — and for a large share of what gets called "kitting," it is — you don't need staged production, work-in-progress tracking, or a multi-step anything. A standard BOM with the kit as the finished product and its contents as line items handles the whole thing in one production run.

What Multi-Step (Staged) Manufacturing Actually Is

Multi-step manufacturing is a different problem: your product genuinely passes through distinct production stages, and at least one of those stages produces something with its own identity — a base mix, a sub-assembly, a bottled-but-unlabeled unit — before the process reaches the item you actually sell.

The test that separates the two isn't how many boxes you'd draw on a whiteboard. It's whether an intermediate stage produces something that could plausibly exist as inventory on its own — something you might build ahead of demand, hold in stock, sell in bulk to a wholesale buyer, or consume into more than one finished product. If a stage produces something like that, it deserves to be modeled as a real stage with real inventory behind it, not flattened into a line item buried inside a bigger recipe. That's the same principle behind multi-level BOM costing: an intermediate product that only exists as an invisible ingredient line can't be quoted, stocked ahead of time, or costed honestly.

A base syrup that gets bottled into three different flavored finished products. A PCB assembly that's soldered once and then goes into two different enclosure variants. A bulk gummy batch that some customers want packaged into jars and others want to buy loose. All of these are staged production, and none of them are "just kitting."

How Nstock Models Staged Production

Nstock's multi-step BOM defines every production stage — first mix through final packaged item — in one bill of materials, instead of a separate BOM per stage stitched together by hand. A few mechanics do the actual work:

• Each step is either a stocked sub-assembly or pass-through WIP. A step can be set to stock its own output — completing it creates real inventory, a lot you can hold, consume into a later step, or sell on its own. Or a step can be pass-through work-in-progress: no lot is ever created for it, and it exists purely to track progress and consumption between stages that don't need to exist as separate stock.
• One production order for the whole run. Starting production from a multi-step BOM creates a single production order that walks through every step in sequence — not a separate order per stage that someone has to remember to kick off and reconcile by hand.
• Produce up to any stocked step, not just the end. You choose how far a run goes. Stop at an intermediate step if that's all you need right now — a base mix banked for later, a sub-assembly built ahead of a bigger order — or carry the run through to the finished product in one pass.
• Partial completions accumulate. A step doesn't have to finish in one batch. Log progress across several production sessions and Nstock tracks the running produced count, flagging the step complete once the target quantity is reached — useful for a stage that runs on a different shift schedule than the rest of the line.
• Each step can consume raw materials of its own, on top of a defined quantity of the previous step's output — so packaging added only at the final step, or a flavoring added only mid-process, is scoped to exactly the step where it's actually used, not smeared across the whole recipe.

One limitation worth being direct about: CSV import always creates standard, single-level BOMs. Multi-step products are built using the Add BOM builder in the app, not bulk-uploaded from a spreadsheet.

A Worked Example: Base Mix, Bottle, Box

Take a supplement brand producing a flavored electrolyte drink. Three real stages:

1. Mix the base. Raw ingredients — mineral blend, sweetener, flavor concentrate — are combined into a bulk base mix, measured by liter. This stage stocks its own output: a base-mix lot the team can hold, split across multiple bottling runs, or, if a wholesale buyer wants the unflavored base without packaging, sell directly.
2. Bottle it. A defined volume of base mix per bottle is consumed, plus the bottle and cap themselves as step-level raw materials. This step could also stock its own output — a filled-but-unlabeled bottle — if that intermediate state is ever held or shared across product lines. Or it can be pass-through WIP if bottling and labeling always happen back-to-back with nothing held in between.
3. Label and box. The final step consumes bottled units plus labels and shipping boxes, producing the finished, sellable product — the last step's output is automatically the BOM's finished good, with no separate output field to fill in.

One multi-step BOM. One production order for a full run. If the team only needs base mix banked ahead of a busy bottling week, they run the order and stop after step one — the base mix lands in inventory as real stock, ready for whenever bottling picks back up, without anyone half-finishing a production order and leaving it hanging. If a wholesale customer wants bulk base mix instead of the finished bottle, that intermediate product already has its own cost and its own stock to quote from — see how multi-level BOM cost rollup works for the mechanics of pricing that intermediate honestly instead of guessing.

Why the Distinction Matters for Costing and Reporting

Flattening a staged process into one line item doesn't just make a BOM harder to read — it distorts two numbers manufacturers rely on for real decisions: work-in-progress value and true unit cost. If a base-mix stage never gets its own tracked identity, the value tied up in that half-finished inventory has nowhere accurate to live — it's either invisible, understating what's actually on the shop floor, or double-counted, folded into the finished good's cost before the good is actually finished. See WIP Valuation Explained and How to Calculate WIP Inventory for what that number should represent — a multi-step BOM's stocked steps are what make it possible to calculate honestly, because each stage's output is a real, costed lot the moment it's produced, not an assumption buried in a spreadsheet formula.

The same logic applies to day-to-day visibility. A production tracking process that only knows "started" and "finished" on a multi-week staged run can't tell anyone where that run actually is today. One that tracks stage-by-stage completion — which is what a multi-step BOM's per-step progress does — can.

When You Don't Need Any of This

It's worth saying plainly: most bundling use cases don't need multi-step BOMs at all. If your "kit" is a fixed set of already-finished SKUs assembled at pack time with no intermediate production stage worth tracking — a variety pack, a gift bundle, a starter kit — a standard single-level BOM is not a compromise. It's the correct tool, and it's simpler to build and maintain than a multi-step BOM would be for the same job. Reach for a multi-step build only when a real intermediate stage exists that's worth its own tracked identity, not by default, and not because a competitor's marketing calls the whole category "kitting."

Common Mistakes

Modeling every bundle as staged production. The instinct to add stages "just in case" makes a BOM harder to build and harder to read, for no operational benefit, if nothing actually happens between assembling the kit and shipping it.

Making every step pass-through WIP out of habit. If an intermediate genuinely gets held, shared across products, or sold on its own, it should stock real inventory — a pass-through step that should have been a stocked one hides that inventory from reports, reorder logic, and quoting.

Forgetting that the last step's output is the finished product. The final step in a multi-step BOM doesn't need its own separate output product field — it's implicitly the BOM's finished good, the same product the BOM itself is defined for.

Trying to bulk-import a multi-step recipe. CSV import only creates standard BOMs. A multi-step recipe with real stages has to be built in the Add BOM builder.

Frequently Asked Questions

What is kitting in inventory management?

Kitting is assembling a set of already-stocked, existing items into one sellable unit — typically at pack or ship time — without a meaningful production process transforming them along the way. It's handled by a standard, single-level bill of materials where the kit is the finished product and its contents are the components.

What's the difference between kitting and multi-step manufacturing?

Kitting groups finished items together; multi-step manufacturing actually transforms raw materials through distinct production stages, at least one of which produces something — a base mix, a sub-assembly — worth tracking as its own inventory. If nothing meaningful happens between "components exist" and "kit is packed," it's kitting. If a stage produces something that could be held, shared, or sold on its own, it's staged production.

What is a multi-step BOM in Nstock?

A multi-step BOM defines every production stage for a finished good — mixing a base, bottling it, boxing it, for example — in one bill of materials instead of a separate BOM per stage. Starting production from it creates a single production order, and you can choose to produce up to any step that stocks its own output, not just the final product. Standard, single-level BOMs are unaffected — multi-step is opt-in per BOM.

Can I produce only partway through a multi-step BOM?

Yes. You choose how far each run goes — stop at an intermediate stocked step if that's all you need, such as a base mix banked ahead of demand or a sub-assembly built early, or carry the run through to the finished product. Each step can also be completed across multiple partial batches over time rather than in one pass.

Does staged production replace regular batch production runs?

No — they cover different situations. A standard batch production run from a single-level BOM is still the right tool for a product with no meaningful intermediate stage. Multi-step BOMs are for products whose production process genuinely has stages worth tracking individually.

Next Steps

If your production process has a real intermediate stage — something that gets held, batched ahead, or occasionally sold on its own — flattening it into one BOM line is the thing quietly costing you visibility. See how staged production works in Nstock → | Read the multi-level BOM cost rollup walkthrough → | See how WIP gets valued mid-production → | Read the production tracking guide → | Read the full help guide →

— Sarah Chen