Purpose

Understand the complete structure of an introduction-week sale before editing products, team choices, or checkout settings.

The sale is not one isolated product. It connects eligibility and team data, sellable products, a bundle checkout, payment, fulfillment, and reporting.

How the parts fit together

1. Community titles can represent existing teams, classes, or access groups.
2. Products define what participants can receive, such as coupons or other sellable benefits.
3. Event ticket types and membership plans supply ticket and membership choices where relevant.
4. A bundle combines the available choices into one checkout.
5. Bundle groups, rules, and questions control what the buyer must or may select.
6. Payment completes the order.
7. Fulfillment creates the memberships, tickets, or coupons included in the paid selection.
8. Bundle reporting and product redemption views show sales and later use.

Choose how to represent a team or “hold”

Use a community title when the team already belongs to the participant or must control eligibility outside checkout.

Use a bundle choice or checkout question when the participant selects a team during the purchase and the answer belongs to that order.

Do not create both representations without deciding which one is the source of truth. If a checkout answer must later become a community title, define who performs or automates that follow-up.

Step by step: map the sale before building

Create a simple inventory with:

• each participant type;
• each team or class;
• every included and optional product;
• ticket or membership requirements;
• quantities and stock;
• prices, fees, and discounts;
• required questions;
• dependencies and exclusions;
• the report each operational team needs afterward.

Have the sale owner approve this map before configuration begins.

Step by step: prepare the building blocks

1. Create or verify any persistent team titles in Community Titles.
2. Create or verify the required products in Products.
3. Create or verify events and ticket types when the sale includes event admission.
4. Create or verify membership plans when the sale grants membership.
5. Test each building block’s name, validity, stock, and instructions before adding it to a bundle.

See Manage community titles and Create and manage products.

Step by step: build the bundle

1. Open Bundles and create or open the introduction-week bundle.
2. Add the groups that organize the buyer’s choices.
3. Add the relevant products, tickets, and memberships to each group.
4. Set which selections are required or optional and how many may be chosen.
5. Add price overrides only when the bundle price differs from the normal item price.
6. Configure dependencies, exclusions, or conditional questions where one choice affects another.
7. Add checkout questions for information that belongs to the order, such as a buyer-selected team.
8. Review availability dates, stock, payment settings, and confirmation content.
9. Save the bundle and review the buyer-facing result.

For the editor’s controls, see Create and manage bundles.

Test before opening sales

Use test participants that cover at least:

• every required team or participant type;
• the cheapest and most expensive valid selection;
• optional items selected and skipped;
• dependency and exclusion rules;
• sold-out or capacity-limited choices;
• successful payment and expected fulfillment;
• confirmation and reporting data.

Record the expected total before checkout and compare it with the displayed total and completed order.

Review orders and payments

1. Open the bundle’s reporting or order view.
2. Confirm the order status and payment result.
3. Review the buyer’s selected team, products, and questionnaire answers.
4. Confirm that included tickets, memberships, and coupons were fulfilled as expected.
5. Reconcile bundle totals with the relevant finance or payment report.
6. Use product redemption reporting later to measure actual consumption, not only sales.

See Review bundle orders and waitlists for operational follow-up.

Change control during a live sale

Before changing a live bundle, determine whether the change affects only new buyers or also requires action for existing orders. Avoid renaming choices in ways that make old and new reports ambiguous.

For material changes, record what changed, when, why, and which existing orders were reviewed.

Troubleshooting

The total is wrong

Compare base price, selected items, price overrides, discounts, and fees. Reproduce the exact selection from the affected order.

A participant received the wrong item

Review the order’s selections, group rules, dependencies, and fulfillment result. Do not edit historical orders to hide a configuration problem.

Team reporting is unclear

Confirm whether the team is stored as a community title, a bundle choice, or a questionnaire answer. Standardize the source of truth before the next sale.