What is a Kit SKU?
A Kit (sometimes called a bundle) is a product type in Luminous that groups two or more existing component SKUs together and sells them as a single unit. A gift set made up of three individual products is a classic example.
Key things to know about kits:
- Kits carry no inventory of their own. Luminous calculates the kit's available quantity dynamically from its components. If a kit requires 2× Widget A and 1× Widget B, and you have 10 of A and 6 of B, the kit shows 5 available (the bottleneck component wins).
- Selling a kit automatically deducts component stock. When a kit is shipped, Luminous reduces the on-hand quantity of each component by the required amount.
- You cannot add or adjust inventory directly on a kit SKU. To increase kit availability, receive or adjust inventory on the component SKUs instead. See Why can't I add inventory directly to a kit?
Creating a Kit SKU
- Go to Inventory → SKUs and click Create(same as creating a normal product).
- Under Product Type, select Kit.
- Fill in the Name and SKU.
- Under the Kit Items tab, add each component SKU and set its required quantity per kit.
- Click Save.
You can also bulk-import kits: use Tools → Imports → Product Catalog → Kits (set the Type column to Kit), then Import Kits to attach the components. All component SKUs must already exist in Luminous before uploading the kit-components file.
For a full walkthrough, see How to Set Up and Manage Kits in Luminous and How to Create and Manage Kits (Bundles) in Luminous.
Configuring a Channel to Expand Kits for Fulfillment
By default, when a kit order is sent to your fulfillment center, the fulfillment order carries the kit SKU as a single line item. Turning on Expand Kits for Fulfillment tells Luminous to instead break the kit into its individual component line items before pushing the fulfillment order — useful when your warehouse or 3PL needs to pick and pack each component separately.
How to enable it
- Go to Manage → Channels and open the Sales channel you want to configure Locate the Expand Kits for Fulfillment toggle.
- Switch it ON.
- Save the channel.
Which channel takes priority? Luminous checks the fulfillment channel first (if your fulfillment order is routed to a specific fulfillment channel). If that channel does not have the setting enabled, Luminous falls back to checking the sales channel that the order came from.
What changes when it is on
| Setting | Fulfillment order line items |
|---|---|
| OFF (default) | One line item for the kit SKU |
| ON | One line item per component SKU, with the quantity multiplied out |
This only affects how the fulfillment order is structured. The original sales order still shows the kit SKU. Inventory is always deducted from the components regardless of this setting.
Why is the Product Type dropdown greyed out when I edit a SKU?
When you open an existing SKU for editing, the Product Type selector is automatically disabled — you will see the current type (Product, Kit, or Non-Inventory) displayed but you cannot change it.
Why Luminous locks the type
The product type determines the entire data structure of a SKU:
- A Product SKU can have inventory stock, cost layers, receiving history, and lot tracking.
- A Kit SKU relies on component relationships and derives its quantities from those components.
- A Non-Inventory SKU is never stocked.
Once a SKU has been created, it can accumulate transactions (sales orders, purchase orders, receiving records, shipments, cost layers) and integration links (channel mappings, alternate SKUs, UPC codes). Converting between types after that point would leave these records in an inconsistent state — for example, a former Product SKU's cost layers and inventory adjustments would have no valid meaning if it became a Kit, and a former Kit's component relationships would be orphaned if it became a Product.
To prevent this data corruption, the type is locked as soon as the SKU record is saved.
What to do instead
If you need a SKU of a different type, the supported path is to create a new SKU with the correct type from the start. If you need to migrate historical data (for example, you have a product that you want to treat as a kit going forward), contact Luminous Support — the team can assist with bulk conversion tooling on a case-by-case basis.