Documentation /Events and dates
Ticket types
A ticket type is a thing the customer can buy: Standard, Front row, Child, Member. An event needs at least one, and can have as many as it needs. They live on the event's Tickets tab. With Pro the list is headed Tickets & packages, because packages sit in the same list.

The list
Each ticket is a row that folds shut. Closed, it says what it is: the name, the price, and Inactive or Package only when either is true. Click it to open the fields. Add ticket adds a new one, already open.
A ticket with a mistake in it stays open until the mistake is fixed, so a problem is never hidden inside a closed row.
The fields
Name and Price
: What it is called and what it costs. A price of 0 makes a free ticket that
still produces a real ticket with a real code, which is what you want for a
free talk with a fixed capacity.
Description : A line under the name on the booking form. "Rows A to C", "Under 16s".
Capacity : Two ways to count:
- Shared with event: draws from the event's total. Sell one and every ticket type has one fewer place between them.
- Own limit: this type has its own number, under Slots. Twelve front-row seats out of a room of sixty. Leave Slots empty and the ticket takes no place at all, like a livestream pass.
Sale window : Sale starts and Sale ends. Outside the window the type is not offered. Use it for early-bird pricing: an Early bird type that stops selling on a date, and a Standard type that starts on the same one.
Limit per order : Min per order and Max per order. "Minimum 2" is how you sell a table for two; "maximum 4" stops one person taking the room. It limits one booking, not the total: ten bookings of four still fill forty seats.
Deposit : Turn it on to let the customer pay part now. Choose Percent (%) or Fixed amount and give the value. The rest is recorded as due, and a workflow can chase it before the date. Deposits have to be allowed globally too, under Settings → Payments → General. See Currency and deposits.
Ask each attendee for : Which of First name, Last name, Email, Phone the customer must fill in for every person on the booking, not just for themselves. Ask for nothing and one name covers the order; ask for a name and each seat gets its own attendee record, its own code, and its own line on the door list.
Template : Paid. Which ticket PDF design this type uses. Off, it prints with your default template. See Ticket templates.
Only sold in packages : Paid, shown once the event has a package. The booking form stops offering this ticket on its own; only a package that contains it can book it. Its price then reads In the package, because the package sets it. See Packages.
Active : Turn a type off without deleting it. Bookings already made keep working.
Copying a ticket
Tickets on one event usually differ in a line or two. Open one and press Duplicate: the copy appears right under it, named {name} (copy) and already open for its new name.
The copy keeps the price, the capacity, the sale window, the limits, the deposit, the questions asked of each attendee and the PDF template. Two things stay with the original, because they belong to it alone: the prices it has on particular dates, and the seat category a hall sells it as.
Order
Use Move up and Move down on a row. The order here is the order on the booking form, so put the one most people want first.
What the customer sees
On the booking form each type is a row with its name, its description, its price and a counter. Several types can go into one booking: two Standard and one Child is a single order with three tickets and three codes.