Booking types

A booking typeThe category of ticket a person chooses first when registering. Each booking type has its own price, sale dates, availability, and eligibility. Examples: Early Bird, Standard, and Premium for a party; Bunkroom, Cabin, and Villa for a camp. is a kind of ticket someone can choose when they register, for example Early Bird, Standard, or a Weekend Cabin. Every ticketA single booking for one person to attend an event. One person can hold several tickets, for example a parent booking for their children. Most things attach to a ticket rather than to a person: add-ons, questions, and check-in. Every ticket belongs to exactly one booking type. is exactly one booking type, so this is the first thing to set up. A booking type carries its own price, availability, and rules, and this page walks through all of them.

Create a booking type

Registration → Booking Types → New

A booking type’s settings are grouped into tabs: General, Pricing and availability, Requirements, and Changes and add-ons.

To get one on sale, you only need a few things:

1. From Registration → Booking Types, choose to add a new one.
2. Give it a title (what attendees see), and a price.
3. Set the inventory (how many can be sold) and the sales open and close dates.
4. Leave it enabled and visible, and save.

Everything else refines how it behaves. The rest of this page covers each tab.

General

• Title and Description: the name and details attendees see. The description supports Markdown formatting, so you can add headings, lists, links, and even tables.
• Image: an optional picture shown with the booking type.
• Enabled and Visible: two separate switches. Enabled decides whether the booking type can be bought at all; Visible decides whether it shows in the list at registration. A booking type that is turned off or hidden only shows at registration for staff and for someone who applies a voucherA code a customer enters at checkout to get a discount on specific items, or to unlock an item that is otherwise unavailable to them. A voucher applies to the booking types, add-ons, or merch you choose, not to the whole order. It can be a single shared code or a set of unique single-use codes. that unlocks it, and only they can book it. There is no separate link that reaches it. This is how you run a private ticket, such as a guest pass: hide it, then hand out a voucher that unlocks it. See Discounts and unlocks.
• Booking a hidden or turned-off type for someone: staff with the Administrator or Registration role can book it for a customer who has no voucher. Staff need to create the booking and submit it. A customer can’t continue, pay for, or submit a saved booking on it themselves, though they can still cancel it. Once staff submit it, the customer pays for the order from My Account. The exception is a place you offer from the waitlist: the customer can pay for and submit that booking themselves, even if its booking type or add-ons are hidden or turned off, unless an add-on’s whole group is turned off.
• Sort Order: where it appears among your booking types (lower numbers first).
• Day Pass and Day Pass Day: mark this as a single-day ticket for a multi-day event, and choose which day it covers. Add-ons can be limited to day passes and to matching days. Leave Day Pass off for a normal full-event ticket.
• Auto-assign tags: tags automatically added to every ticket of this type, handy for finding or grouping these attendees later.

Pricing and availability

• Price: what the ticket costs. Set 0 for a free ticket.
• Require payment upfront: whether buyers of this type must pay when they book. This can only add an upfront requirement, never remove one: payment is required upfront if your event’s payment setting requires it or this booking type does. So you can force upfront payment on a single type even when the event allows paying later, but you cannot let a type be paid later when the event requires payment upfront.
• Payment due date: the date and time payment is due for tickets that are not paid upfront, in your event’s time zone.
• Total inventory and Available inventory: how many can be sold, and how many remain. Availability counts down as tickets sell.
• Inventory counts: what one unit of inventory means. Per attendee (the default) counts each person, so a booking for four people uses four. Per booking counts the whole booking as one, however many people it covers, which is how you sell a fixed number of cabins or tables. Price is always charged per attendee in both modes.
• Sales open and sales close: the window during which this booking type can be bought. Outside this window it cannot be bought. To let specific people buy before sales open, unlock the type with a voucher; to collect interest before sales open more broadly, see pre-fill.
• Allow guest registration: let someone register for this type without signing in first. Leave it off to require an account. A guest who has a voucher needs to log in to apply it.

Requirements

• Collect attendee details: ask every attendee for their legal name and date of birth. On by default. Turn it off for bookings where you only need a badge name and email. Staff can always register someone without these details.
• Minimum and maximum group size: how many people one booking can include.
• Minimum age: the youngest age allowed for this booking type. Leave it at 0 for no age limit.
• Create a room for each booking: creates one room for every order, holding everyone in it, so you can allocate them together.
• Room type: shown when rooms are created. Choose another booking type to create rooms of that kind instead, for example selling single bunks that are grouped into a six-bunk cabin. The room’s capacity comes from that booking type’s maximum group size. Leave it empty to use this booking type.

Tip

Selling a container rather than a seat, such as a cabin or a table of ten? Set Inventory counts to Per booking, so each booking uses one unit however many people it covers.

Note

Stock for a per booking type is not returned when someone cancels, because other people may still be in that room. Check the room, and if it is free, return the stock by adjusting Available Inventory. See Rooms and registration.

Changes and add-ons

• Allowed type changes (pre-fill): the other booking types a person can switch their saved booking to before they register. This is especially handy when premium tiers sell out fast: someone can pre-fill for a premium type and switch if they miss out. As long as the type they switch to is cheaper, their existing payment hold carries over, so they do not have to enter payment again.
• Allowed type changes (after registration): the other booking types a person can switch themselves to once registered, for example upgrading their own ticket. Leaving both empty means no self-service switching; staff can still change a booking type from the ticket.
• Restrict available add-ons: by default every add-on that allows this booking type is offered. Turn this on to narrow it to a chosen list of add-ons instead. This is one of two ways to line up add-ons with booking types; the other is set from the add-on side.

Note

Switching a booking type can change the price. When a person or staff member switches a ticket, there is an option to update the price to match the new type. See Transfers and type changes.

When nothing is on sale

If none of an event’s booking types can be chosen right now (they are all hidden, turned off, or outside their sale dates), the registration page says no tickets are available and points people to the voucher box. A voucher holder can still enter their code there to unlock a hidden or closed booking type. Visitors who aren’t logged in see a prompt to log in and apply their voucher.

Bundling merch with a booking type

You can include a merch item with a booking type, such as a shirt that comes with every weekend ticket. This is set up on the merch side rather than here. See Included merch.