> For the complete documentation index, see [llms.txt](https://docs.elitebundleapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elitebundleapp.com/create-bundles/multi-option-bundle.md).
# Multi-option bundle
Complete guide to creating Multi-Option Bundles in Elite Bundle Builder, including options, single-product mode, discounts, design customization, and FAQ.
A **multi-option bundle** sells a fixed group of products where the shopper picks one item for every option. It lives on the product page and uses the theme's own Add to cart button, so it looks native.
## What shoppers see
{% stepper %}
{% step %}
They open the bundle's product page and see each option as a labelled group: "Shirt", "Trousers".
{% endstep %}
{% step %}
For each option they pick one product or one variant combination.
{% endstep %}
{% step %}
The price shows the running total and any discount.
{% endstep %}
{% step %}
They use the theme's **Add to cart** button. The discount applies at checkout.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
Needs the **Elite Embed Core** app embed. The **Multi-Option Bundle** app block is optional: by default the selector sits just above the theme's Add to cart button, and the block only matters when you want it somewhere else. The **Publish** tab has a one-click **Add app block** step.
{% endhint %}
## The editor tabs
Seven tabs: **Template**, **Options**, **Config**, **Offer**, **Design**, **Publish** and **Settings**. A multi-option bundle always renders inside the product page, so Template picks its layout rather than where it shows.
## Template tab
| Layout | Looks like |
| -------------- | --------------------------------------------------------- |
| Stacked cards | White cards on one panel, joined by a plus |
| Divided list | Catalog rows: a big image, the price in its own column |
| Numbered cards | An outlined card per item with its number and a big image |
| Tinted cards | Cards filled with a tint of your primary colour |
| Grid | Two cards per row with the image on top |
① The layout in use, ② the preview
The layout and its card style are set here only, like build-your-own templates. Picking one also switches off prices inside the choices, since each item's header already shows its price; the header and choice settings stay editable in **Design → Choices**.
## Options tab
① A Products option, ② a Product with options option, ③ its Colour and Size choices in the preview
### Option name
A clear label for the product group: *Shirt*, *Trousers*, *Hat*.
### Option mode
{% tabs %}
{% tab title="Products" %}
You pick several products and the shopper chooses one item from the combined list. Each product contributes its selectable variants.
Add a product **whole** so every variant becomes a choice, or tick **particular variants** in the picker so only those appear. Drag products to set the order.
{% endtab %}
{% tab title="Product with options" %}
You pick exactly one product and the shopper builds a variant from its own Shopify options, for example Colour then Size. Combinations that do not exist or are out of stock cannot be selected.
{% endtab %}
{% endtabs %}
Modes can be mixed: option 1 can be a list of shirts while option 2 is one jacket with size and colour selectors.
### Free gift option
Turn on **Mark this option as a free gift** at the bottom of an option and whatever the shopper picks there is free: "buy the kit, pick a free sample". Set the **Gift label** shoppers see in place of its price ("Free gift"). The option shows a **Free gift option** badge in the Options tab.
{% hint style="info" %}
The gift is one pick per bundle and never counts toward the discount. At checkout it is its own line at $0 with the message "Free gift", only while the paid options are in the cart, and never on a subscription plan. It needs at least one paid option beside it.
{% endhint %}
### Managing options
**Add option** creates one (a bundle needs at least one); drag the number badge to reorder; **delete** removes it.
## Config tab
A multi-option bundle takes exactly one item per option, so Config has no quantity rules. It holds the bundle's extras:
| Page | What it controls |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Subscriptions | One-time purchase or subscribe, with plans from your subscription app. Every product must be in one plan there, which the bundle connects. The picker shows above the theme's Add to cart button when every chosen item is in that plan. See [Subscriptions](/create-bundles/subscriptions.md). |
| Upsell | A card for the bundle on other product pages. See [Upsells](/grow-and-manage/upsells.md). |
## Offer tab
A multi-option bundle is a fixed combo, so there are no quantity tiers. Its Offer tab has one switch and one value:
* **Percentage off** the bundle total, or
* **Fixed amount off** the bundle total
The discount applies whenever the bundle is added to cart. No trigger, no minimum.
### Bundle add-ons
**Offer → Add-ons** has bundle add-ons: a gift message, To & From, a delivery date, an email, a choice or a gift box, filled in once for the whole bundle. Pick a ready-made card and it's added; edit its label, type, price and whether it's required. Shoppers fill them in just above your theme's Add to cart button, and what they enter goes on the order with the bundle ("To: Anna"). A price (a fixed amount or a product's price) is charged once per bundle, shows in the total and never gets the bundle discount. A required one that's missing stops Add to cart and points the shopper to it. **Show** makes one appear only once another is filled in, like a name field under a ticked Gift card. Multi-option bundles have no product cards or quick view, so product add-ons (engraving, gift wrap) are for build your own bundles.
## Design tab
| Page | What it controls |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Variant display | Click **Fetch variant options**, then give every option a **Label**, **Swatch** or **Dropdown** style with images or colours per value. A *Products* option appears as **Product choices**. |
| Choices | The item header (image, product title, price, compare-at price), per-item prices, hiding sold-out choices, the discount badge, + between items |
| Branding | Colours, corner rounding, button shape, swatch and thumbnail sizes |
All covered in [Design and customize](/customize-and-publish/design-and-customize.md).
**Product data** is set in the preview, not on a page: hover an option and click **+** to show text and product data (SKU, vendor, metafields and more) as a badge on the picked item's image, a line under the picked item in its header, a line under the choices, or on each product choice. **Above the total** takes your own text for the whole bundle, with cart variables such as `{saved}` or `Add {remaining} more for {next}`. **On each product choice** shows only in options that list products, on label buttons and image or colour dropdowns, not on swatches or a plain text dropdown. See [Product data](/customize-and-publish/product-data.md).
## Frequently asked questions
### Can a shopper buy two of the same bundle in one go?
Not in a single action. Each add to cart adds one of each option, and the theme's quantity field does not apply. To buy the set twice, add it, then build and add it again.
### What happens if a variant combination is out of stock?
It shows as sold out and cannot be selected. In **Product with options** mode, choosing a colour narrows the sizes to the ones that exist. If every choice in an option becomes unavailable, the bundle cannot be completed. Turn on **Hide sold-out choices** in Design → Choices to drop them instead of showing them disabled.
### How is the price calculated?
The sum of the selected items across all options, minus the discount at checkout. A free gift option adds nothing.
### Where is the Add to cart button?
The bundle hooks the theme's existing button rather than drawing its own; it stays disabled until every option is chosen. The theme's price and dynamic checkout buttons are hidden because the bundle supplies its own total. In the editor preview a dashed placeholder marks where the button will be.
### Can I change how an option is displayed after launch?
Yes. **Design → Variant display**, switch between Label, Swatch and Dropdown, preview, save.
### Can shoppers subscribe to the bundle?
Yes, when every product in it is in one plan in your subscription app. Turn it on in **Config → Subscriptions**. The chosen items go to the cart as separate lines, because Shopify does not merge lines that carry a selling plan. See [Subscriptions](/create-bundles/subscriptions.md).
### Do I need the app block?
No. Add it only when the selector should sit somewhere other than above the theme's Add to cart button.
### Can each multi-option bundle have its own design?
Yes. Layout, variant display, choices and branding are per 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.elitebundleapp.com/create-bundles/multi-option-bundle.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
