ThunderTix logo

Support Forum

How is Package Pricing Split Across Events in Reports? - Fri - Feb 27, 2026 - 5:31pm

  • When you sell a season pass or package using Package Ticket pricing, ThunderTix can now divide the package price evenly across all included performances and show that revenue directly in your event‑level reports.

    This article explains:
    • What “package pricing” means
    • How ThunderTix distributes the package value
    • How coupons and discounts are handled
    • Where you’ll see this in reports
    • Important limitations and edge cases

    What is “package pricing”?

    This feature applies when you use Package Ticket pricing for a season pass or package (not the “bundled discount” option).
    • The customer buys one package at a single price (for example, $100).
    • The package includes multiple performances (for example, 4 or 6 events).
    • ThunderTix:
      • Keeps the full price on the Package Ticket.
      • Also splits that price across all child tickets (one child ticket per performance in the package).
      • Uses those split values in your reports.

    Customer‑facing views (checkout, confirmation, receipts) do not change—each ticket still appears as Included in the package.

    How the package price is divided

    When an order with a Package Ticket is completed:
    1. The Package Ticket holds the full package price.
    2. The system divides the package price evenly across the tickets in the package.

    Example:
    • Package Ticket: $100
    • 4 performances in the package
    • 4 child tickets created (one for each performance)
    • Each child ticket receives: $100 ÷ 4 = $25.00

    These per‑ticket values are stored for reporting only; the buyer still sees each ticket as “Included,” not as $25.

    Handling uneven splits (rounding)

    If the package total cannot be divided evenly (for example, $100 divided by 6 performances):
    • ThunderTix calculates the per‑ticket share.
    • Any rounding remainder is assigned to the last ticket in the package.

    For example, $100 ÷ 6:
    • 5 tickets might be $16.67
    • 1 ticket might be $16.65
    • Total still equals $100.00

    This guarantees that the total of all child tickets always matches the original package price.

    How coupons and discounts are applied

    ThunderTix supports coupons that apply per ticket and per order. Package revenue is always reported based on the net amount actually paid for that PackageTicket.

    Coupons applied per ticket (package ticket)

    If a coupon is applied directly to the PackageTicket:
    1. The coupon reduces the package price.
    2. The discounted package price is divided evenly across the child tickets.

    Example:
    • PackageTicket price: $100
    • Coupon applied to that ticket: $8 off
    • Net package price: $92
    • 4 performances in the package

    Each child ticket receives: $92 ÷ 4 = $23.00 in revenue in your reports.

    Coupons applied per order (multiple packages)

    If the coupon is per order, and the order contains multiple packages:
    • The order‑level discount is associated with specific ticket types, so each package ends up with its own net price.
    • Each package’s net price is then split only among that package’s child tickets.

    Example conceptually:
    • Package A: $100
    • Package B: $50
    • A $20 discount is associated with Package B

    Result:
    • Package A reports as $100 split by its events.
    • Package B reports as $30 (after the $20 discount) split by its events.

    These appear as separate line items in reports, preserving accurate revenue per package.

    How package edits affect reporting

    The revenue split is always based on the tickets that exist in that specific order at purchase time, not on the package’s current definition.

    Example: package updated after some sales
    1. You configure a package with 4 events for $100.
    2. Customer #1 buys the package:
      • PackageTicket: $100
      • 4 child tickets created
      • Reports show $100 ÷ 4 = $25.00 per event.
    3. Later, you edit the package to include a 5th event.
    4. Customer #2 buys the package after the change:
      • PackageTicket: $100
      • 5 tickets created
      • Reports show $100 ÷ 5 = $20.00 per event for this second order.

    Customer #1’s order is not retroactively changed. It still has 4 tickets and continues to report $25.00 per event.

    Where you’ll see package revenue in reports

    1. Settlement by Event and Performance

    In the Settlement by Event and Performance report:
    • Each child ticket from a package contributes its split amount to that event/performance.
    • Package revenue appears alongside regular single‑ticket revenue, so you can see:
      • How much revenue each performance earned from season packages.
      • The sum of all package‑related child tickets across performances will equal the total package revenue (after discounts).

    2. Multi‑Event Report (Package Tickets)

    In the Multi‑Event report, under Package Tickets:
    • Each child ticket shows its allocated share of the package price.
    • You can view:
      • Package revenue per event
      • Package revenue per performance
      • Totals across a season or date range

    Because the split amount is stored on each child ticket, the Multi‑Event report can accurately roll up:
    • Total package revenue for a given performance or event
    • Total package revenue for specific package types
    \

    This gives you clear visibility into how much each event in your season actually earned from package sales.