Kitting inventory: assembly, labor cost, and when to build kits ahead
Kitting inventory for small brands — kits vs bundles vs multipacks, what assembly does to your math, labor as a real cost, and build-timing strategy.
InventoryX is in development and not available today. ClearStock is the live Shopify app.
Kitting inventory: assembly, labor, and when to build kits ahead
Kitting is building a sellable product from multiple components at the moment of your choosing. That last clause is the whole subject: with a bundle, the components stay separate until the customer's order (Shopify's bundle mechanics handle the pairing — Shopify documents bundles as separate products sold together, created via a bundles app; see the Shopify Help Center, product bundles, accessed October 2026. The planning side is covered in the bundle inventory guide); with a kit, someone at your bench physically combines them first, and the moment you do it, your inventory converts, your availability changes shape, and a labor cost appears that never shows up in any component's price. This article covers the definitions, what assembly does to your numbers, how to price the labor honestly, and the pre-assemble vs. kit-on-order decision.
Kit, bundle, multipack: the definitions that matter
The words get used interchangeably, which causes real mistakes — each form has different inventory mechanics:
| Form | What it is | Component stock until sale | Availability math | Where it breaks |
|---|---|---|---|---|
| Bundle | Separate SKUs sold together (synced or pseudo-SKU) | Untouched — components ship as components | min of component sets (see below) | Velocity attribution, not physical work |
| Multipack | N identical units sold as one | Converted at assembly (or never separated) | On-hand of packs = units ÷ N | Miscounted as singles after conversion |
| Kit | Distinct components assembled into a new physical unit | Consumed at assembly | Finished kits on hand; components vanish from sellable | Everything below |
The bundle article's core rule — bundle availability equals the minimum of component sets, not the average — still applies conceptually to kits, but the moment of application moves. For a bundle, min() runs at sale time, every second, via sync. For a kit, min() runs once, at assembly: if you have 40 pouches, 12 treats, and 90 toy parts, an assembly session produces min(40 ÷ 1, 12 ÷ 1, 90 ÷ 1) = 12 kits — and the leftover 28 pouches and 78 parts sit as orphaned components until the next treat delivery. Assembly freezes the bundle math into physical reality. That's the extension of the rule: bundles recompute scarcity continuously; kits crystallize it, so the cost of bad proportioning becomes shelf inventory instead of a number.
What assembly does to your inventory numbers
Three conversions happen the moment kits are built:
- Components leave, kits appear. In Shopify terms this is an inventory adjustment: decrement each component, increment the kit SKU. Native Shopify has no BOM (bill-of-materials) feature to do this from one action as of October 2026 — the native admin's inventory tooling covers quantities, transfers, purchase orders, and counts (Shopify Help Center, inventory and locations, accessed October 2026), so each kit-build is a set of adjustments, done manually or via an inventory app. Keep the build log: date, kits built, components consumed. It's your batch record and your count reference.
- Demand history splits in two. Component sales now come from direct sales plus assembly consumption — and assembly consumption appears in no sales report. This is the same component-demand censoring that poisons bundle reordering, except kits hide it more completely, because the components stopped decrementing at sale time entirely. If you reorder components from their sales velocity alone, you'll under-buy exactly the parts your kits consume. The fix is a component demand line per kit build: direct velocity + (kit build rate × units per kit).
- The kit SKU inherits a new cost. Components' costs plus assembly labor (next section). Until you fold labor into the kit's cost per item, every profit report on that SKU overstates margin.
Labor is an inventory cost, so price it like one
The component cost of a brew kit might be: coffee beans $6.20 + pour-over dripper $4.80 + filters $1.10 = $12.10. But the kit also consumes 7 minutes of someone's time (assemble, bag, label, box). At a loaded labor rate of $22/hour — pay plus overheads; pick your own number honestly — that's 7 ÷ 60 × $22 ≈ $2.57 per kit, bringing the true build cost to about $14.67.
Three places that number has to show up:
- Cost per item on the kit SKU — set it to the loaded number, or the kit's profit reports lie by ~$2.57 forever.
- The kit's margin check. If the kit sells at $24.99, its margin is nothing like the $12.90 the component math suggests — it's $10.32 before shipping and fees. Some kits that look profitable at component cost aren't after labor; better to learn it on paper.
- Build-batch efficiency. Building 12 kits costs more than 12/60th of an hour plus setup — staging, cleanup, finding the label roll. Track time on your first few batches and use the real number; the estimate above is the floor, and treat the exact rate as your own input, not a standard.
Pre-assemble vs. kit-on-order
The central timing decision. Both work; each fails differently.
Pre-assemble (build ahead of demand) wins when:
- Kit volume is steady and predictable — a standing "starter kit" that sells 3–5/day.
- Assembly is fast per unit and components are stable (no version churn).
- Customers expect same-day shipping; assembly at order time would add a day.
Its failure mode is mechanical: pre-built kits are finished goods with one recipe, and when a component changes — new bean lot, redesigned dripper — pre-built stock becomes either wrong-versioned inventory or a rebuild job. Pre-build shallow and often, not deep and rarely.
Kit-on-order (assemble at sale) wins when:
- Volume is thin or spiky (a seasonal gift set that sells 200 units in December and nothing in February — pre-built stock is then a counting and storage liability for eleven months).
- Components are customizable (pick your own hot sauce trio), so assembly is per-order by definition.
- Component versions churn often.
Its failure mode is capacity: kit-on-order converts demand spikes into labor spikes. A BFCM weekend that sells 150 kits needs 150 × 7 minutes ≈ 17.5 hours of assembly somewhere — plan it, or the orders ship late regardless of stock.
A middle path worth naming: pre-assemble the constraint, kit-on-order the rest. In any kit there's usually one component or sub-step that dominates (the fiddly one — folding, wrapping, labeling). Do that step ahead in batches; finish at order time. You capture most of the speed with little of the version-churn risk.
Either way, the components feeding kits need buffers sized on combined demand — direct sales plus the build schedule — which is the corrected-demand logic from the bundle guide applied at purchasing time, with the safety stock formula run on the corrected number. And the build-rate input to component reordering should follow the same order-quantity method as anything else (how much inventory to order) — a kit build schedule is just demand with a different clock.
Common questions
What's the difference between a kit and a bundle? A bundle is separate SKUs sold together, with components staying whole until the order ships; a kit is physically assembled into a new unit before sale, consuming components at build time. The planning difference: bundle availability recomputes continuously (the min of component sets), while a kit's availability was fixed the moment you built it.
How do you track kit inventory in Shopify? Native Shopify has no bill-of-materials feature as of October 2026, so a kit build is recorded as manual adjustments: decrement each component by units per kit, increment the kit SKU, and log the batch. Component demand must then be tracked separately, because assembly consumption doesn't appear in any sales report.
How do you cost a kit? Component costs plus loaded assembly labor: time per kit × your fully loaded hourly rate (pay plus overheads). A $12.10 component set with 7 minutes of labor at $22/hour adds ~$2.57, making the true cost about $14.67. Put that loaded number into the kit SKU's cost per item or every profit report on it overstates margin.
When should I pre-assemble kits instead of building on order? Pre-assemble when volume is steady, assembly is fast, and components are stable. Kit-on-order when volume is thin or seasonal, assembly is customizable, or components churn. The middle path — pre-assembling only the fiddliest step — captures most of the speed with less version-churn risk.
How many kits should I build at once? Build shallow and often for pre-assembled kits — a few days to a couple of weeks of cover — so a component version change doesn't strand built stock. Size component purchases on combined demand (direct sales plus build rate), and size the build batch on real assembly-time data from your first few batches, not estimates.
Where to go next
Pick your best-selling kit and write down its true loaded cost — components plus timed labor. If the margin still works, the next task is the component demand correction: direct velocity plus build rate per component, feeding reorder math sized on the corrected number. The bundle guide's demand formula (bundle inventory) is the same arithmetic with a different trigger, and once kits are a real share of revenue, that weekly corrected-demand check is what keeps the components — and therefore the kits — selling.