When to use ticket packages

Learn when ticket packages should be used compared to individual tickets.

Ben Dharmanandan avatar
Written by Ben Dharmanandan
Updated over a week ago

This article will describe some use case scenarios to help determine when to use different ticket types (person ticket or packages), and when to create new categories. If you have not done so already, please read our “Understanding tickets and categories” article.

When do I use a ticket package?

Eventsforce provides event managers with the ability to create ticket packages to allow the purchase of a predefined combination of tickets and items, often at a discounted rate.

Ticket packages may not be needed in all events, as discounted group registration can also be done by creating a separate ‘Single person’ ticket type with a lower rate and an enforced minimum tickets per booking. 

A ticket package should be used if any of the following apply:

  • When multiple person tickets from different attendee categories are to be offered/sold together at a group rate

  • Selling a sponsorship style package which includes multiple person tickets and items as a total package price

Note: If offering discounted group registration but are limiting groups to the same ticket type, this can be accomplished without using ticket packages. Instead, create a new ticket type with the discounted rate and enforce a minimum number of tickets to be booked.

Should I create a ticket package or a new person ticket with min/max restrictions for groups?

Use ticket packages when:

  • person tickets from different categories are being offered together at a specific package price

  • Sponsorship package that includes multiple person tickets and items at a package price

Scenario 1: The cost of a single “Attendee” ticket is $100. The event manager wants to provide a group discount of $25 per ticket when 4 people register as part of a group.

  • Scenario 1 solution: No need to use ticket packages here, as no items are used. Add two ticket types, one with a price for single registration ($100), and another with the discounted ticket price ($75). The ticket type with the group rate should have a minimum of “4” tickets per registration. 

Scenario 2: The cost of a single “Attendee” ticket is $100, with the ability to add an ‘event dinner’ item ticket for $15. If a single attendee selects both, the total is $115 per attendee. The event manager wants to offer an incentive to register as a group by providing a free dinner to each person (or $15 off each) if 4 attendees register as a group.

  • Scenario 2 solution: Ticket packages should be used here. Create a ticket package containing 4 attendee tickets and 4 event dinner item tickets. When adding a price, enter “$100” as the total price (price includes ‘attendee’ ticket and ‘event dinner’ item). The total price to be paid for the entire ticket package would be $400 ($100 per attendee). 

Scenario 3: The event manager wants to offer sponsorship packages that include a certain number of sponsor tickets, a certain number of items, as well as a sponsorship ad space (item ticket). 

  • Scenario 3 solution: Ticket packages should be used here. The event manager can create a separate package for each level of sponsorship (Gold, Silver, etc). The “Gold Sponsor package” might be sold at $10,000 fixed rate and include “4 sponsor tickets, 4 gala dinner tickets, 1 full page ad”. 

Should I create a new category or add separate tickets?

If the questions and/or sessions for this attendee type are restricted or unique, we recommend creating a new attendee category. If the attendees see the same questions and sessions, but the price is different, we recommend building different ticket types.

Scenario 4: The event manager needs to allow registration of ‘Members’ and ‘Non-Members’. Members will see sessions that are not available to ‘Non-Members’, and ‘Non-Members’ see extra registration questions that are not visible to ‘Members’.

  • Scenario 4 solution: Eventsforce recommends creating a separate attendee category for “Member” and another for “Non-Member”. Once categories are created, corresponding tickets for each category will be added automatically. 

Scenario 5: The event manager needs to allow registration of different sponsorship levels (Gold, Silver, Bronze). The questions shown to all sponsor levels are the same, only the price is different.

  • Scenario 5 solution: Eventsforce recommends having just one category for “Sponsor”, then creating separate person tickets for “Gold Sponsor”, “Silver Sponsor”, “Bronze Sponsor” and configuring separate prices for each ticket.

Other articles you may find useful:

Did this answer your question?