Help Center

by Happenings

Build, test, and launch a bundle sale in Connect

Connect Web

Assemble tickets, memberships, and coupons into groups, configure pricing and eligibility, test combinations, and publish safely.

Purpose

Build a bundle checkout that delivers the intended items and calculates the correct price for every valid buyer choice.

Prepare the building blocks

Before creating the bundle, create and verify every ticket type, membership plan, and coupon product it will use. A bundle references those existing items; it does not replace their stock, validity, or eligibility rules.

Write down the valid combinations and expected totals before opening the wizard.

Step by step: create the draft

  1. Open Bundles.
  2. Select Create bundle.
  3. Under Basic information, enter Title and Description.
  4. Choose an Event (optional) when the bundle belongs to one event, or leave it page-level.
  5. Add an optional Cover image.
  6. Select Continue.

Build groups and items

  1. Under Groups and items, give each group a clear title.
  2. Choose the group’s Selection type:
    • All required includes every item automatically.
    • Pick one requires one choice.
    • Optional (any) allows any number or no choice.
    • Optional (single) allows one choice or no choice.
  3. Add the appropriate Ticket type, Membership, or Coupon items.
  4. Set Quantity and Max quantity.
  5. Use Included in base price or Price override only when the pricing design requires it.
  6. Add further groups and dependencies.
  7. Use Depends on specific items when a later group should appear only after an exact choice.
  8. Review every group’s valid and invalid combinations.

Configure pricing

Choose Fixed price when every valid selection costs the same. Choose Sum of selected items when the total should be calculated from the buyer’s choices.

Set:

  • Bundle price and Original price for fixed pricing;
  • optional Member price or Student price (school-verified);
  • early-bird price and end rule when required;
  • physical pickup information when Physical bundle is enabled.

Verify that displayed savings are truthful and that reduced member or student prices are not higher than the normal bundle price.

Configure eligibility and availability

  1. Choose No restriction, Page members only, or School verified only.
  2. Use Who can buy this for community-title restrictions.
  3. Use Who can see this when visibility must be narrower than general discovery.
  4. Set Total available. Use 0 only when inventory should be unlimited.
  5. Set Sale starts and Sale ends.
  6. Enable Waitlist when sold out only when your team will operate the resulting offers.

Eligibility and visibility are different. A visible bundle may still be unavailable to an ineligible buyer.

Add checkout questions

Use Checkout questions for answers that belong to the bundle order. Prefer fixed options for teams, classes, meal choices, or sizes that need reporting.

When a question controls another question, test every conditional path. Use order answers for choices that belong to this bundle order, and use community titles only when the grouping should remain on the member beyond the purchase.

Review and save as draft

  1. Open Review your bundle.
  2. Compare title, items, quantities, pricing, eligibility, sale window, inventory, and questions with the approved sale map.
  3. Under Ready to publish, choose Save draft.
  4. Confirm that the bundle appears with status Draft.

Saving as draft creates the bundle without making it available for purchase.

Test the buyer journey

Test at least:

  • every eligible audience;
  • an ineligible buyer;
  • each choice in every Pick one group;
  • optional groups selected and skipped;
  • dependencies and conditional questions;
  • minimum and maximum quantities;
  • fixed, member, student, and early-bird prices;
  • sold-out behavior and waitlist when enabled;
  • successful payment and fulfillment of every included item.

Record expected and actual totals for each case.

Launch and monitor

  1. Correct the draft and repeat failed tests.
  2. Select Publish only after approval.
  3. Confirm Bundle published.
  4. Verify the buyer-facing bundle with an eligible account.
  5. Monitor orders, units, revenue, inventory, and failed orders.
  6. Use Pause if sales must stop temporarily. Use Archive when the bundle should leave sale but retain history.

Troubleshooting

A group does not appear

Review its group and item dependencies. Exact item dependencies take priority over group dependencies.

The total is wrong

Confirm Pricing mode, included items, overrides, buyer eligibility, and early-bird rules using the exact choices from the affected order.

The buyer received the wrong item

Inspect the order’s included-item breakdown and fulfillment status. Pause the bundle if the same configuration could affect more buyers.

connect-webbundlescheckoutproductsticketsmembershipslaunch
Was this helpful?

Analytics choices

Happenings can use optional analytics cookies to understand usage and improve the product. They stay off unless you allow them.

Read cookie policy