Bundles and launch batches: reserve the components before packing
Define kit components, reserve shared stock and preserve customer order references through assembly and launch-batch fulfilment.
Reviewed 2026-10-07 · 4 min readGive the kit a bill of materials and a packing version
A bundle listing describes what the customer buys; an assembly instruction describes what the warehouse must use. Connect them with a kit SKU and a bill of materials. List every component SKU, variant and quantity per kit, together with the materials, insert version and finished packing requirements. Include the unit of measure: an individual item, a pair, a pack and a case should not be interchangeable words in the same instruction.
Assign a version and an approval date to the bill of materials. If an insert or component changes for a launch, identify which orders use the new version. Record whether substitutions are permitted and who approves them. Give the team a sample or visual reference when the presentation needs review, then preserve the approved result. A photograph can support the instruction, but the component quantities and variant choices still need to be written down.
Count the physical components once
Locate the real component stock before calculating how many kits can be made. Record the physical location, SKU, quantity and condition state. Separate actual stock pools from informational views or mirrored quantities. A dashboard showing part of the same inventory does not create an additional supply. If the store, warehouse and bundle tool each show a number, establish whether those numbers represent independent goods, subsets or different states of one physical count.
Shopify's reviewed first-party Bundles guidance says its bundle inventory uses overall stock rather than tracking by location. That makes the actual tool and location configuration a specific test requirement. Do not assume that a third-party kit app reads the same fields or respects the same operational holds. Ask the implementation owner which quantities it uses and how it calculates a kit's availability, then compare the result with the approved physical component list.
Reserve components for the intended sales mix
Shared components can be sold individually, used in several kits or held for a launch. Agree the allocation before publishing availability. In an illustrative batch, a kit needs two units of component A and one of B. Thirty approved units of A and thirty of B allow fifteen complete kits before any other allocation. If ten units of A are reserved for individual orders, twenty units of A remain for this batch, allowing ten kits.
Use this calculation as a planning record, then confirm how the actual stock system represents the reservation. Record batch reference, component quantity, reason, authoriser and the event that releases or consumes the hold. Do not reduce the physical count merely to represent a planned use. Also reserve packaging materials if their availability constrains assembly. A complete product set with no approved box or required insert may still be waiting for the agreed packing work.
Test what happens after the next stock update
A manual reservation should survive the updates that the live process will send. Test a normal stock push, a simultaneous individual sale, a kit sale, a cancellation and a connection retry. Capture the component balances and published kit quantity before and after each event. Include the actual location map and tool version in the record. If one update restores reserved stock to an unrestricted pool, identify the field ownership conflict before opening the batch to live orders.
Test kit changes as well. A revised component quantity, renamed variant or replacement packing version may affect existing orders differently from new ones. Agree which instruction the warehouse receives for each case. If a test creates an impossible kit count, place the affected allocation on hold, compare the source quantities and preserve the logs. Resolve the calculation and repeat the relevant sample before expanding use. There is no single app setting that proves the whole assembly workflow works.
Keep the production total linked to customer orders
A launch batch can summarise manufacturing or purchasing needs by component and variant while retaining separate customer orders. Keep a batch reference, cutoff used for that batch, expected receipt, planned kit quantities and original order references. Orders arriving after the agreed cutoff need a clear assignment. If the customer-facing estimate changes, the retailer should update it using the reviewed batch plan and its own communications process rather than a warehouse assumption.
When stock arrives, reconcile the actual quantities before allocating them to customers. A shortage in one variant should be visible against the affected orders instead of spreading silently across the whole batch. Record how the authorised allocation was chosen and who approves substitutions, partial release or a revised batch. Keep customer-specific packing requests associated with the original orders. Combining the purchasing quantity must not erase the address, variant or release instruction needed for each final parcel.
Release completed kits with a component reconciliation
Before release, compare components issued, kits completed, unused components, damage or scrap observations and any work still in progress. Record the actual packing version and requested checks. A partial assembly should remain identifiable so neither its components nor a finished kit are counted as fully available twice. Where product serials, expiry records or batch identifiers matter, specify how they are carried through the assembly and final package record before work begins.
Connect each released kit to its order, dispatch parcel and carrier reference. If a return later arrives, review the actual components and condition before deciding what can be restored to stock. Bring the kit list, reservation requirements and sample batch when discussing kitting or a custom stock connection with Jeton Express. Agree the handling, materials, field ownership and approval contacts together. The warehouse can then execute a definite assembly instruction while the retailer retains a checkable allocation history.