> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Bundles
> Package tickets from multiple events into a single discounted purchase, as a fixed set or a flexible pick-and-mix, to increase bookings and grow participants per transaction.
Bundles let you group tickets from any events in your portfolio into one
purchase. A participant adds the bundle to their basket, fills in their details
once per ticket, and gets a discount for booking together, with no promo code
needed.
Bundles are set up at the organizer level, not per event, so one bundle can span
any combination of events you run. Bundles are limited to ticket entries;
add-ons cannot be included in a bundle.
Bundles are designed for a single participant booking several entries for
themselves, not for buying on behalf of a group. They are not built for
multi-participant purchasing flows where one booker enters many different
people, so don't use a bundle to sell team or group entries.
## Fixed and flexible bundles
Every bundle uses one of two buyer-choice rules, set under **Bundled tickets**:
| Rule | Setting in the dashboard | What the buyer does |
| ------------ | --------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Fixed** | **Every ticket required** | Buys every ticket in the bundle (all or nothing). |
| **Flexible** | **Let buyers choose a selection** | Buys a number of tickets you allow, within a minimum and maximum you set. The discount can scale up as they add more. |
A flexible bundle lets buyers build their own selection from the tickets you
include, and lets you reward larger selections with a bigger discount through
**tiers**. For example:
Offer three events and let buyers pick any two or more. Give 10% off for
two, rising to 15% off if they take all three.
One ticket group per event, each holding a choice of distances. Buyers enter
every event for a discount, picking Sprint or Olympic at each.
Bundle a Saturday race with a Sunday one (for example a 5K shake-out and a
Sunday half or full) so participants commit to both at a saving.
Pair a high-demand event with a smaller one to lift entries for both and
bring in participants who wouldn't have found the newer event on its own.
## Creating a bundle
Bundles are managed from the **Bundles** area of your organizer dashboard. Click
**Create bundle**, then work down the page.
Under **Bundle setup**, enter a **Basket label**, the label that appears in
the basket and identifies the bundle in your dashboard. You can also add the
details shown on the checkout card here:
* **Title**: a short heading shown on the bundle card in checkout.
* **Body**: body copy shown on the bundle card.
* **Banner copy**: a short promotional line displayed on the card.
* **Image**: a photo shown in the bundle card.
Under **Bundled tickets**, build the bundle out of **ticket groups**. Each
group is one slot in the bundle. Click **Select tickets** to add tickets
from any of your events. Different dates, locations, or categories all work.
A group can hold a single ticket, or several **options**. Click **Add
options** to give a group more than one ticket. When a group has multiple
options, the buyer chooses only one of them (for example a choice of
distances at the same event). Every group must have at least one ticket
before the bundle can go live.
Once the bundle has two or more ticket groups, choose how many the buyer must
take under **Buyer choice**:
* **Every ticket required**: a fixed bundle. The buyer purchases every
ticket group.
* **Let buyers choose a selection**: a flexible bundle. Set the
**Minimum** number of tickets the buyer must take and, optionally, a
**Maximum**. Leave the maximum as **No limit** to let them take as many as
you offer. The dashboard reads this back as, for example, "Buyers pick
between 2 and 3 events."
Under **Discount**, choose the **Discount type** and enter a **Discount
value**. The type controls how the saving is applied to the tickets:
| Discount type | What it does |
| ---------------- | ------------------------------------------------------ |
| **Percent off** | Takes a percentage off the qualifying tickets |
| **Money off** | Takes a fixed amount off the qualifying tickets |
| **Bundle price** | Sets a specific total price for the qualifying tickets |
To also discount the booking fee, click **Add booking fee discount** and
configure a second discount in the same way.
A bundle without a configured discount is still valid. You can use bundles
purely to let participants book multiple events in one checkout.
On a flexible bundle you can reward larger selections with a bigger saving.
Click **Add tier** and set **Unlocks at** to the number of events that
unlocks the better discount, for example a base discount at 2 events and a
higher tier that unlocks at 3.
Buyers get the single best tier they qualify for; tiers never stack.
Under **Visibility**, click **Choose events** and select the event
occurrences whose checkout pages should advertise this bundle. A bundle with
no events selected is saved but not shown anywhere in checkout.
Under **Usage limits**, set **Limit per booking** to cap how many times this
bundle can be added in a single checkout. Leave it as **Unlimited** for no
cap.
Under **Enable bundle**, switch the toggle on when the bundle is ready to go
live. The toggle stays locked until the bundle has tickets, a discount, and
at least one event selected. The readiness callout, "A few more steps before
you can enable this bundle," tells you what's still missing.
Click **Save** to publish.
## Bundle statuses
Each bundle in your list shows one of three statuses:
| Status | What it means |
| ------------ | ------------------------------------------------------------------------------ |
| **Enabled** | Booking is on and the bundle appears in checkout on its selected event pages |
| **Unlisted** | Booking is on, but no events are selected, so the bundle is not shown anywhere |
| **Disabled** | Booking is off, so participants cannot add the bundle to their basket |
You can turn booking on or off at any time from the Bundles list. Turning it off
removes the bundle from checkout immediately; you'll be asked to confirm first.
If a bundle isn't appearing in checkout, check that it is enabled, that the
relevant events are selected under **Visibility**, and that the readiness
requirements (tickets, discount, and at least one event) are all met. If the
**Enable bundle** toggle is locked, the readiness callout on the bundle page
shows exactly what's still needed.
## What participants see in checkout
When a bundle is enabled and linked to an event, participants see a bundle card
alongside the individual ticket options on that event's checkout page. The card
shows:
* The basket label and (if set) title and body.
* The tickets included in the bundle.
* The saving, for example "You save 10%".
For a **fixed** bundle, adding the card adds every ticket. For a **flexible**
bundle, the buyer picks their selection. Checkout prompts them to "Select at
least 2 of 3 tickets" (using your minimum and the number of tickets on offer),
and the discount that applies reflects the tier their selection reaches.
The discount applies automatically, with no promo code needed. It does not
affect a ticket's individual price; the discount only applies when the tickets
are booked as part of the bundle. Participants can also add individual tickets
alongside a bundle in the same checkout, and can add the same bundle more than
once unless you set a **Limit per booking**.
In the basket and order summary, each bundle appears as a grouped section
listing its tickets and a **Bundle discount** line showing the amount saved.
Once a bundle booking is confirmed it cannot be changed through self-service.
Contact your Let's Do This account manager or LDT support to discuss options for
that booking.
## Booking forms
Participants complete the information relevant to each event in the bundle,
filling in one booking form per ticket they take. Where a field is the same
across those tickets, we consolidate it and ask for it only once, so the
participant doesn't repeat themselves. Fields that are unique to a particular
ticket appear on that ticket's form.