Creating a Product Bundle
Use a Product Bundle to sell several items as one kit while keeping stock of the individual components. The customer buys the kit; the warehouse picks and delivers its components. You do not need to manufacture a finished item for this workflow.
This guide covers setup, pricing, a sales order, delivery, invoicing, stock checks, and returns for kits supplied from your own warehouse.
Before you start
Confirm that:
You have permission to create Items and Product Bundles, and to prepare and submit the sales documents required for your role.
The kit has its own Item record with Maintain Stock unticked and Allow Sales ticked. The parent must not be a fixed asset.
Each physical component has an Item record with Maintain Stock ticked and the correct Default Unit of Measure.
The component quantities for one kit are agreed, and enough component stock is available in the delivery warehouse.
The kit has a selling price, or your administrator has deliberately enabled pricing from component rates.
You know whether stock will leave through a Delivery Note or a Sales Invoice with Update Stock ticked.
Create a new non-stock parent Item when necessary. Do not change an established stock item into a bundle parent to work around stock history or validation.
Use this guide for ordinary warehouse stock. NexWave WMS does not support Product Bundles. A component tracked by both Item and Warehouse bin settings cannot be delivered through the bundle packing table. Agree a supported process with your administrator before processing such a kit. Do not turn off stock controls to bypass an error.
Decide what the kit represents
Business need | Suitable process |
|---|---|
Sell several existing components together without holding stock of the combined kit | Product Bundle |
Produce and hold a finished item, record manufacturing operations, or track production costs | Bill of Materials and the manufacturing process |
Sell a different pack size of one stock item | Review the item's UOM conversion before choosing a bundle |
A Product Bundle describes the sales kit. It does not create a finished-goods stock balance or a manufacturing order. Do not assume that a Purchase Order or an automatic drop shipment will expand the kit into component purchase lines. Confirm those workflows separately.
1. Open Product Bundle
Search for Product Bundle in the NexWave search bar. Alternatively, open the Stock workspace.
Stock workspace used to find item setup
Under Items and Pricing, select Product Bundle.
Product Bundle link in the Stock workspace
Select Add Product Bundle to create a new kit definition, or open an existing bundle to review it.
Product Bundle list and Add Product Bundle action
The list image shows an existing example. Your list will contain the bundles available on your site.
2. Define the components of one kit
Select the non-stock kit Item in Parent Item.
Enter a useful Description.
Leave Disabled unticked.
In Items, select Add Row for each component.
Set Item and Qty. Enter the quantity required for one parent item in its default unit.
Check UOM. The component unit comes from its Item record. Use quantities in that component's stock unit.
Review every component and select Save.
Use positive quantities. Do not use another active Product Bundle as a component, and do not add the parent as its own component.
A kit definition containing two camera bags and one camera
In this example, one Professional Camera Kit contains two Camera Bags and one Cannon Camera. The stock unit for each component is Nos.
Kits sold in the parent's default unit | Camera Bags required | Cameras required |
|---|---|---|
1 | 2 | 1 |
2 | 4 | 2 |
3 | 6 | 3 |
NexWave multiplies each component quantity by the parent quantity expressed in its stock unit. If you sell the parent in another UOM, its conversion factor also affects the component demand. Test the default unit first, then check any alternate selling UOM.
3. Set and test the selling price
For a fixed kit price:
Open Item Price.
Create or review a selling price for the parent Item.
Confirm Price List, Currency, UOM, Rate, and any validity dates.
Save the price.
Check the result on a draft sales transaction, including any applicable Pricing Rules.
Do not assume that the selling price equals the total of the component prices. In Selling Settings, Calculate Product Bundle Price based on Child Items' Rates controls whether component rates calculate the parent price. Ask your administrator to confirm the intended setting before testing. This setting affects bundle pricing across the site.
Use Price Lists and Pricing Rules for price maintenance and controlled discounts.
4. Prepare and check the Sales Order
Create a Sales Order for the correct Customer and Company.
Add the parent kit under Items.
Enter Quantity, Delivery Date, and the selling UOM.
Confirm the selling rate, currency, taxes, and total.
Save the draft and open Packing List.
Review Packed Items. Check each Parent Item, Item Code, Qty, and Warehouse. Open a packed row if its warehouse is not visible in the table.
Compare the component quantities with the kit definition and the number of kits ordered.
Submit the Sales Order when the commercial and stock checks are complete.
Packing List for one kit, showing two bags and one camera
The image shows the component quantities on a saved draft order. It does not show a completed delivery. The component Rate values are not a confirmation of the agreed parent selling price.
Saving or submitting the Sales Order does not reduce stock on hand. Check availability for each physical component, rather than looking for stock of the non-stock kit parent.
5. Deliver the components
Use a Delivery Note when your process records delivery separately from billing.
Open the submitted Sales Order.
Select Create, then Delivery Note.
For a partial delivery, set the parent quantity to the number of complete kits being delivered now.
Save the draft and review Packing List again.
Check each component quantity and source Warehouse. Confirm that the warehouse has enough stock of every component.
For batch-controlled or serial-number components, review the required batch or serial allocation on the component rows before submission.
Confirm that the picked goods match the component list.
Submit the Delivery Note when the goods are dispatched under your normal process.
For example, delivering one of two ordered kits should issue two bags and one camera, leaving one complete kit to deliver later. Do not retain the packing quantities for two kits on a one-kit delivery.
If your site uses a Desk Pick List, check the component quantities and their Sales Order links there before creating the Delivery Note. Do not send a Product Bundle through the WMS scanner workflow.
6. Invoice without issuing stock twice
After a Delivery Note has recorded the stock movement, create the Sales Invoice from that delivery. Confirm the parent kit quantity, rate, taxes, and total. Keep Update Stock unticked so the invoice bills the delivery without issuing the components again.
If your agreed process uses a Sales Invoice to record both sale and dispatch, select Update Stock, save, and review its Packing List and component warehouses before submission. Use this route only when the same goods have not already been issued through a Delivery Note.
Preview the customer print before sending it. Check the kit description, quantity, price, and any component details required by the customer. The chosen print format controls which details appear.
7. Confirm the stock result
After the stock document is submitted:
Open Stock Ledger.
Select the correct Company and date range.
Filter by a component Item and the source Warehouse.
Find the submitted Delivery Note or stock-updating Sales Invoice.
Confirm the outgoing quantity for that component.
Repeat for every physical component and compare with the number of kits delivered.
Review Stock Balance if you also need the remaining component quantities.
For two example kits, the stock document should issue four bags and two cameras. The non-stock parent should not have its own stock movement. A billing-only Sales Invoice should not create another issue for the same delivery.
Stop and review the source documents if the quantities or warehouses differ. Do not create an extra stock adjustment merely to make a report match.
8. Process returns and later changes
For a return of complete kits:
Open the original Delivery Note and select Create, then Sales Return. For a stock-updating Sales Invoice, use its credit-note return action.
Enter the number of kits returned as a negative parent quantity.
Save and review the negative component quantities in Packing List.
Check the receiving warehouse and any batch or serial identities against the actual returned goods.
Submit the stock return after inspection, then process the related credit under your normal returns workflow.
Check that the components returned to stock once and the customer credit is correct.
For the example kit, a return of one complete kit contains two bags and one camera. If only one component is returned, agree the stock and credit treatment before posting. Do not record a complete-kit return for goods that were not received.
Changing the Product Bundle definition does not correct an existing submitted stock document. Review open drafts after a definition change because saving them can rebuild their packing lists. For a changed kit composition, a new parent Item can make the new version clearer. Use Disabled to stop an obsolete bundle only after reviewing open orders and returns; do not delete a used definition to remove transaction history.
Review checklist
The parent is a non-stock sales Item.
Physical components maintain stock and use the correct units.
Each bundle quantity describes one parent item in its default unit.
The selling price and pricing setting are intentional.
The Sales Order and delivery packing lists match the kits ordered and dispatched.
Component warehouses, availability, and any batch or serial allocations are correct.
One stock document records each dispatch.
Stock Ledger shows the expected component movement.
Returns reflect the goods actually received.
Troubleshooting
Problem | Check |
|---|---|
The parent cannot be selected or saved | Confirm Maintain Stock is unticked, the parent is not a fixed asset, and no other enabled bundle already uses it. |
A component is rejected | Use a positive Qty and a valid Item. A component cannot itself be an active Product Bundle. |
No component packing list appears | Check that the bundle is enabled and uses the exact parent Item on the sales line. Save the draft. A Sales Invoice without Update Stock does not keep a stock packing list. |
Component quantities are too high or too low | Check the per-kit quantities, parent quantity, parent UOM conversion, and component stock units. Recheck after saving the draft. |
The kit price changes unexpectedly | Review the Selling Settings pricing option, the parent Item Price, and applicable Pricing Rules. |
Delivery is blocked by insufficient stock | Review each component in its source warehouse, including reservations and batch or serial availability. Stock of the parent cannot replace missing components. |
A Warehouse Bin error blocks delivery | Bundle component execution is not supported when both Item and Warehouse bin tracking apply. Ask your administrator for a supported process. |
Stock was not reduced | Confirm the Delivery Note or stock-updating Sales Invoice was submitted. A Sales Order and a billing-only invoice do not issue stock. |
A supplier order contains the kit rather than its parts | Product Bundle is a sales packing definition. Confirm the purchasing or drop-shipment process separately before sending the order. |
A return proposes the wrong components | Compare with the original delivered packing list and any later definition change. Resolve the difference before submission. |