Create tickets, registrations and booking options

Prepare the event before adding tickets

Save the event’s title, date, location and maximum attendance first. For a recurring programme, decide which occurrence a customer is booking and how allocations should work across dates. Confirm the payment setup for paid tickets.

Open Tickets, Registrations or Bookings. An empty related-items list means that no ticket records are attached here; publishing the event description alone does not create an admission offer.

Add the admission or registration record

1. Choose Add new Tickets, Registrations & Bookings when you are ready to create a ticket record. The action begins a real draft, rather than opening a disposable demonstration form.
2. Complete the fields offered by your configured ticket editor. Use a clear title, the correct type and a description of what is included.
3. Set the price, permitted quantities and sale window. Configure the allocation and any registration form required by your account.
4. Save the child record and confirm it appears in the event’s related list.
5. Add other genuinely different admission choices, then review their combined capacity and public presentation.

Ticket editor fields vary with the website configuration. The following reference covers the ticket information used by the current booking website; your account may show additional fields.

Ticket field reference

Title

The choice shown to the customer, such as General admission or Table for four. Avoid ambiguous titles such as Option 1.

Description

Explain inclusions, eligibility and any important restrictions. Make clear whether the price covers one person, one table or another unit.

Type

Select the configured ticket, registration or booking type. Types can affect the public flow; test the chosen type rather than assuming changing the label alone changes what the customer receives.

Price

The configured price for one unit of this ticket type. Use a free offer only when no admission payment is intended. Check the final customer total and your account’s fee treatment.

Minimum quantity

The smallest allowed booking quantity for this ticket type. Use it only when a customer must book at least that many units.

Maximum quantity

The largest allowed quantity in a booking for the type. This is different from the event’s total capacity or the ticket’s available allocation.

On-sale date

The opening of the ticket’s sales window. A published event can remain visible before the ticket is available.

Off-sale date

The end of the sales window. Check the intended time as well as the date, particularly for sales that close before doors open.

Third-party ticket link

A configured external booking destination for the ticket record. Test the complete URL and confirm whether the public event should use this external route or native Eventsity checkout.

For registration forms, arrange the questions and whether they apply to the buyer or each attendee. A purchase of four places is not automatically four separately named registrations. Test that the answers appear in the registration report.

Plan the registration questions →

Reconcile ticket allocations and room capacity

Treat allocation, event capacity and per-booking quantity as separate controls. A 100-person room might offer several ticket prices, but that does not mean each price gets another 100 places. Confirm the shared-capacity configuration and verify a mixed-ticket order.

• Set the ticket allocation and event maximum to match the intended capacity. Do not use zero or a negative value to mean unlimited.
• Check that minimum quantity is achievable and does not exceed maximum quantity.
• For recurring events, test the exact date customers will choose; do not assume every occurrence receives an independent allocation.
• Allow for temporary checkout reservations when reviewing availability. An active cart can hold stock until its deadline.
• If a customer reports a payment problem, check the order before asking them to pay again. A bank’s pending entry alone does not establish a completed booking.

Add products and optional extras

Open Ticket Options. Use Link existing Products & Options to attach a reusable record, or Add new Products & Options to create a new draft. Save a new record and check that it is attached to the event.

These are related options, separate from the main admission ticket. For an extra such as a meal or programme, confirm the title, price, allowed quantities and how it is selected in your configured booking journey. Linking a record does not by itself prove that every checkout template will display or charge for it.

• Check an existing product before reusing it; changes to a shared record can affect other events.
• Where ordering controls are available, put the options in a sensible display order and verify the public result.
• Use the relationship’s remove action to detach an option from this event when appropriate. Detaching is different from deleting the product itself.
• Test a booking with and without the extra. Confirm the total, confirmation and booking report before promoting the option.

Understand the event’s Options settings

Don’t Issue Tickets

Found under Details → Options → Ticketing. This is a configured workflow setting for events that should not issue admission tickets. Confirm its effect on your website and confirmation process before enabling it. It does not cancel existing orders or refund customers.

Bond Amount

Found under Details → Options → Bookings. Stores a bond value for a configured booking workflow. Confirm how it is charged, recorded and released before offering it. The field alone does not establish automatic collection or refunds.

Test the customer journey before opening sales

Eventsity’s published Red Label offer is 50¢ per order plus 2.2% processing, including GST. Confirm how your account displays and handles fees. Google Pay and Apple Pay require the configured payment service and an eligible device or browser; test the methods your customers will be offered.

1. Save and publish the intended event and ticket records, or use your agreed staging and test-payment setup.
2. Open the event as a customer and choose the correct occurrence.
3. Try one ticket, a group quantity and each relevant price or registration type. Check minimum, maximum, on-sale, off-sale and sold-out states.
4. Add optional extras and verify their quantities and effect on the total.
5. Complete an agreed test booking. Check the event date, price, confirmation, ticket delivery and registration answers.
6. Find the resulting booking and attendee records. Resolve discrepancies before sharing the event link.