Skip to main content

Setting a Minimum and Maximum Number of Tickets Per Order

How to sell tables of tickets

With Circolo, you can control how many tickets an attendee can purchase in a single order by setting a minimum and maximum number of tickets per order.

This is useful when you want to:

  • Require attendees to purchase a set number of tickets

  • Offer discounted pricing when attendees purchase multiple tickets

  • Sell tables for events such as gala dinners

  • Manage group bookings where one person purchases tickets for several attendees

For example, if you want to sell a table of 10 for a gala dinner, you can set the minimum and maximum number of tickets per order to 10. This means attendees can only purchase that ticket tier in quantities of 10.

What does minimum and maximum tickets per order mean?

Minimum and maximum tickets per order allows you to control the number of tickets that can be purchased from a specific ticket tier in one transaction.

The minimum number of tickets per order is the smallest number of tickets an attendee must purchase.

The maximum number of tickets per order is the largest number of tickets an attendee can purchase.

These settings apply to the ticket tier where they are configured.

When should I use minimum and maximum tickets per order?

You should use minimum and maximum tickets per order when you want to control ticket quantities for a specific ticket tier.

Common use cases include:

  • Selling a table of 10 at a gala dinner

  • Offering a discounted group ticket price

  • Limiting how many tickets one purchaser can buy

  • Requiring attendees to purchase a minimum number of tickets

  • Creating a ticket tier for corporate or group purchases

How to sell a fixed number of tickets per order

To require attendees to purchase a fixed number of tickets, set the minimum and maximum number of tickets per order to the same number.

For example, to sell a table of 10, enter:

  • Minimum tickets per order: 10

  • Maximum tickets per order: 10

When an attendee purchases tickets through your event URL, they will only be able to purchase 10 tickets from that ticket tier.

This setup can be used for table bookings, group bookings, team registrations or any other ticket tier where a fixed quantity must be purchased.

How to allow a range of tickets per order

You can also allow attendees to purchase a range of tickets.

For example, if you want attendees to purchase at least 4 tickets but no more than 10 tickets, enter:

  • Minimum tickets per order: 4

  • Maximum tickets per order: 10

The attendee will then be able to purchase between 4 and 10 tickets from that ticket tier in one order.

How discounted group pricing works

If you want to offer a discounted price for purchasing multiple tickets, enter the discounted price as the individual ticket price.

For example, your standard ticket price may be $100, but you may want to sell a table of 10 for a total of $800.

To set this up, calculate the individual ticket price first:

  1. Decide the total price for the group purchase.

  2. Divide the total price by the number of tickets included.

  3. Enter that amount as the ticket price.

Example:

  • Standard ticket price: $100

  • Number of tickets included: 10

  • Desired total price: $800

  • Individual ticket price to enter: $80

The attendee will purchase 10 tickets at $80 each.

The total order amount will be $800.

What information does the attendee need to provide?

When an attendee purchases multiple tickets in one order, they will be asked to provide details for each ticket included in the order.

This may include:

  • Attendee first name

  • Attendee last name

  • Email address

  • Dietary requirements

  • Any other required attendee information for your event

For example, if someone purchases 10 tickets, they will be asked to provide details for each of the 10 attendees.

What if the attendee does not know all guest details at the time of purchase?

If the purchaser does not know all guest names, email addresses or dietary requirements at the time of purchase, they can update these details later.

The purchaser will still need to enter a first name and last name for each attendee during the booking process. These names can be temporary because they are editable after purchase.

For example, the purchaser could enter:

  • Guest 1

  • Guest 2

  • Guest 3

  • Guest 4

After the booking has been completed, the purchaser can log back into their portal and manage the tickets.

From the portal, the purchaser can:

  • Update each attendee’s first name and last name

  • Transfer a ticket to the correct attendee using their email address

  • Allow the attendee to update their own dietary requirements

  • Allow the attendee to update any guest preferences linked to their ticket

This gives the purchaser flexibility if they are booking on behalf of a group and does not yet have all attendee details confirmed.

How to view bulk ticket purchases in Guest Management

You can view bulk ticket purchases within Guest Management.

Guest Management allows you to see:

  • Who purchased the tickets

  • How many tickets were included in the booking

  • The associated tickets linked to that order

  • The attendee details for each ticket

  • Dietary requirements for each attendee, where provided

This helps you manage group purchases, table allocations and guest information in one place.

Example: Selling a table of 10 for a gala dinner

A gala dinner organiser wants to sell tables of 10.

The standard ticket price is $100, but the organiser wants to offer a discounted table price of $800.

To set this up:

  1. Create or edit the relevant ticket tier.

  2. Set the minimum tickets per order to 10.

  3. Set the maximum tickets per order to 10.

  4. Set the individual ticket price to $80.

  5. Publish or update the event.

When an attendee purchases this ticket tier through the event URL, they will purchase 10 tickets.

Each ticket will cost $80.

The total order amount will be $800.

Key points to remember

  • The feature is used to set a minimum and maximum number of tickets per order.

  • Table bookings and group bookings are examples of how this feature can be used.

  • These settings are configured at the ticket tier level.

  • To require a fixed number of tickets, set the minimum and maximum values to the same number.

  • To allow a quantity range, set different minimum and maximum values.

  • Discounted group pricing should be entered as the individual ticket price.

  • Purchasers must enter a first name and last name for each attendee during checkout.

  • Temporary names, such as Guest 1 or Guest 2, can be used if the final guest details are not known.

  • Purchasers can update attendee details later through their portal.

  • Purchasers can transfer tickets to attendees using their email address.

  • Attendees can update their own dietary requirements and guest preferences after receiving the transferred ticket.

  • Guest Management shows the purchaser, associated tickets and attendee details.

Did this answer your question?