> For the complete documentation index, see [llms.txt](https://bpie.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bpie.gitbook.io/docs/catalog/bundle-products.md).

# Bundle and kit products

A bundle (or kit) is a single product made up of other products you already sell. A good example is a **Gift Hamper** — one product on the catalogue, but made up of one pen, one notebook, and one chocolate. When the hamper sells, BillingPie pulls those three component items out of stock automatically.

> 🎥 **Watch this in action.** A short video for this screen is on our [YouTube channel](https://www.youtube.com/@BillingPie). Look for "Bundle Products".

> 📷 **Screenshot needed:** the Add Product page with the Normal / Bundle toggle and the Bundle Product tab open.

***

## ⭐ Highlights

| What you can do                                                                      | Why it matters                                           |
| ------------------------------------------------------------------------------------ | -------------------------------------------------------- |
| Create a bundle from any group of products you already have                          | Festive hampers, combos, and kits go live in minutes.    |
| List the included products with quantities                                           | One hamper = 1 pen + 1 notebook + 1 chocolate.           |
| Selling a bundle drops **component** stock automatically                             | No second entry, no missed item.                         |
| Set a **fixed bundle price** or let the total come from the components               | Pricing flexes to your offer.                            |
| Bundles show across **Products list**, **quotations**, **orders**, **stock reports** | Flagged so you can tell them apart from normal products. |

***

## 📋 In this page

* [What is a bundle product](#what-is-a-bundle-product)
* [Create a bundle product](#create-a-bundle-product)
* [How stock moves when you sell a bundle](#how-stock-moves-when-you-sell-a-bundle)
* [Bundle pricing](#bundle-pricing)
* [Where bundles show up](#where-bundles-show-up)

***

## What is a bundle product

A bundle is a "wrapper" product. It has its own name, code, and price — but its stock is tied to the products inside it.

Typical uses:

* **Gift hamper** — a few items sold together for a festival.
* **Combo offer** — buy a shirt + tie + pocket square at a special price.
* **Starter kit** — a printer with a sample paper pack and one ink cartridge.
* **Repair kit** — a tool, two screws, and one washer in a single SKU.

For the salesperson, it feels like selling one item. For your stockroom, it pulls every component automatically — no second entry, no missed item.

***

## Create a bundle product

1. Open **Products** from the side menu.
2. Click **+ Add Product**.
3. Open the full edit page from the **Create Product** box (or click an existing product to edit it).
4. At the top of the form, switch the **Normal / Bundle** toggle to **Bundle**.
5. Fill the basics — **Product Name**, **List No**, **Category**, **Brand**, **Price**, **GST** — just like a normal product.
6. A new tab appears: **Bundle Product**. Click it.

> 📷 **Screenshot needed:** the Bundle Product tab with the component search box and the table of added components.

7. Search for the first component product. Pick it from the dropdown.
8. Set the **Qty** of that component (how many go into one bundle).
9. Click **Add**.
10. Repeat for every component.
11. Click **Save** at the bottom of the page.

The bundle is now a normal product on your catalogue — but flagged as a Bundle.

> ⚠️ **Note:** A component can be any product already in your catalogue, including one with attributes (colour, size). If a component has variants, you'll be asked to pick the exact variant when you add it.

***

## How stock moves when you sell a bundle

When a sale order with a bundle product is marked **Complete**:

* BillingPie does **not** drop stock of the bundle itself.
* BillingPie **does** drop stock of every component, using the quantity ratio you saved.

Example: a **Gift Hamper** has 1 pen + 1 notebook + 1 chocolate. If you sell 5 hampers, BillingPie pulls 5 pens, 5 notebooks, and 5 chocolates from stock.

> 📷 **Screenshot needed:** a sale order line for a bundle product showing the component breakdown in the row's expanded view.

### What if a component is out of stock

If you try to sell a bundle and one of its components is short:

* The salesperson sees a low-stock warning on the order line, naming the short component.
* If your shop is set to **block negative stock**, the order cannot be saved until you restock the component.
* If your shop allows negative stock, the order goes through and the short component drops below zero.

To check before you sell, open the bundle product's detail page — the Bundle Product tab shows each component's current stock side-by-side.

***

## Bundle pricing

You have two ways to price a bundle:

| Pricing mode                       | What it does                                                                                                                       | When to use                                                                               |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Fixed bundle price** *(default)* | Type a single price on the bundle. Every sale uses that price, no matter what the components add up to.                            | Festival hampers and combos where the bundle is cheaper than buying the items one by one. |
| **Sum of components**              | Leave the bundle's own price blank. The order line price is the total of each component's price multiplied by its bundle quantity. | Starter kits and repair kits where the price should always match the parts inside.        |

GST on the order line uses the bundle's own GST rate. The components keep their own GST rates for your purchase and stock reports, but the customer-facing tax on the bundle is the rate you set on the bundle product.

> 📷 **Screenshot needed:** the Bundle Product tab with the Fixed price field and the Sum-of-components option shown.

***

## Where bundles show up

* **Products list** — bundles show with a small **Bundle** badge so you can tell them apart at a glance.
* **Quotations and sale orders** — when you search for the bundle name, it appears like any other product. The order line shows the bundle name; expanding it shows the component breakdown.
* **Stock reports** — bundles themselves don't show a stock number (they don't carry stock). The component products show their normal stock, including the units that went out as part of bundles.
* **Sale reports** — bundles show by name on the sales reports. To see which components moved because of bundle sales, open the [Stock reports](/docs/reports/stock-reports.md) and filter by the component product.

> 💡 **Pro Tip:** Run a small test sale of one bundle before you launch a festival offer — it's the fastest way to confirm the components, the GST, and the price come out the way you expect.

***

## 🎬 Watch the video

> 🎥 **Video placeholder:** Embed a short video from the BillingPie [YouTube channel](https://www.youtube.com/@BillingPie). Pick the one that fits this page.

***

## 🔗 Related pages

* 📄 [Add a product](/docs/catalog/add-product.md) — the form that the Bundle toggle lives on.
* 📄 [Products list](/docs/catalog/products-list.md) — find a bundle and see its badge.
* 📄 [Product details](/docs/catalog/product-details.md) — the Bundle Product tab for an existing bundle.
* 📄 [Stock](/docs/inventory/stock.md) — check component stock before you sell a bundle.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bpie.gitbook.io/docs/catalog/bundle-products.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.