# Configure WMS bundles and kits
URL: https://support.starshipit.com/articles/14700000000068-configure-wms-bundles-and-kits
Canonical: https://support.starshipit.com/articles/14700000000068-configure-wms-bundles-and-kits
Markdown: https://support.starshipit.com/articles/14700000000068-configure-wms-bundles-and-kits.md
Updated: 2026-11-08

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Choose exploding or pre-kitted bundles, add components and verify how WMS allocates their stock.

Configure a bundle when one sold SKU contains several component products. Choose whether workers pick the components for each order or build finished kits that carry their own stock.

## Before you begin

You need permission to manage products. Create the bundle SKU and its component products first. Keep the bundle and components within the same client ownership. If Cin7 Core or Shopify manages the bundle definition, change it there and follow its import guide so a later sync does not replace your WMS edits.

## Bundle products

Starshipit WMS supports bundle or kit SKUs made up of other SKUs. These are configured as **bundle products** and can be handled in two ways:

### Exploding bundles

An **exploding bundle** is a bundle SKU that breaks down into its component SKUs when an order is processed. The WMS does not pick the bundle SKU directly. Instead, it:

* Allocates and picks the *individual component SKUs*
* Tracks inventory at the component level
* Treats the bundle as a logical grouping for ordering and reporting

This is useful when you never hold a pre-built kit in stock but always assemble it from individual components when fulfilling an order.

### Require stock bundles (pre-kitted)

A bundle set to **Require stock** behaves like its own physical item. In this case:

* The bundle SKU has its *own inventory* that must be on hand to fulfil orders
* When stock is not available, WMS can create a **kitting job** prompting staff to assemble bundles from components
* Once assembled, the on hand quantity for the bundle SKU is increased

Kitting jobs support **Pending** and **Assigned** statuses, allow assignment management, and can auto-allocate components to speed up kitting workflows.

This mode is ideal when you keep pre-built packs on the shelf and want to ensure they are either available or explicitly assembled as a separate process.

WMS validates bundle setup during order and release workflows. If a bundle is missing required component information or stock rules, the error is surfaced so you can correct the product before warehouse work begins.

### Choosing the right bundle mode

* Use **exploding bundles** when you do not store pre-made kits and always pick component items.
* Use **require stock** when you store finished kits and want kitting to be a separate, trackable activity.

Quick comparison:

| Consideration | Exploding bundles | Require stock bundles |
| --- | --- | --- |
| **How it works** | Breaks down into component SKUs when an order is processed | Bundle SKU has its own inventory that must be on hand |
| **Inventory tracking** | At component level | At bundle level |
| **Picking** | WMS picks individual component SKUs | WMS picks the bundle SKU directly |
| **Kitting** | Components assembled at fulfilment | Pre-built kits stored on shelf; kitting jobs create bundle stock |
| **Best for** | Never store pre-made kits, always pick components | Keep pre-built packs on shelf and track as separate inventory |

## Configure the bundle

1. Open **Products**, then open the bundle product for editing.
2. On **Inventory**, set **Product Type** to **Bundle Product** and select **Save changes**.
3. Open the product’s **Bundle** tab.
4. Choose **Explode** for component picking or **Require Stock** for finished-kit inventory.
5. Select **Add Component**, choose the component product and enter its quantity. Repeat for the remaining components.
6. Review the component SKUs and quantities, then select **Save changes**.
7. Reopen the bundle and check the saved mode and components.

## Verify fulfilment

Use a controlled test order. For an exploding bundle, check that allocation uses the expected component quantities. For a require-stock bundle, confirm finished-kit stock is available or complete the required kitting job before fulfilment. Check both component and finished-kit balances after kitting.

## Troubleshooting

| Problem | What to check |
| --- | --- |
| Bundle cannot be saved | Add at least one valid component and check its quantity, client and any validation message. |
| An order is short of stock | Check the selected mode. Exploding bundles need component stock; Require Stock needs finished-kit stock or kitting. |
| A sync changes the configuration | Edit the bundle in the system that owns its definition, then re-import and verify it. |

## Related articles

* [Configure WMS products and inventory](/articles/14700000000006-configure-wms-products-and-inventory)
* [Build kits in WMS Mobile](/articles/14700000000028-build-kits-in-wms-mobile)
* [Sync exploding bundle availability to Shopify](/articles/14700000000048-sync-exploding-bundle-availability-to-shopify)
* [Set up Cin7 Core with Starshipit WMS](/articles/14700000000035-set-up-cin7-core-with-starshipit-wms)