A ticket is what a customer buys. It has a name, a description, a price, and a list of the slots it can be booked on. Manage tickets under Operations > Tickets. Event tickets live under Events and never appear here.
Create a ticket
Choose New ticket:
| Field | Notes |
|---|---|
| Name | For example “Day ticket”. Customers see it. |
| Description | Shown to customers when they choose a ticket, and in this list. Supports formatting (bold, lists, links). |
| Adult price | In your system currency. |
| Minors price (optional) | What a minor pays. Leave blank to charge everyone the adult price. Enter 0 for minors to ride free. |
| Rides (optional) | The number of rides included. Blank means unlimited. |
| Can be booked on these slots | Tick at least one. |
| Enabled | Untick to stop customers buying it without deleting it. |
A ticket can’t be saved or enabled without at least one slot.
Who can buy it
A ticket can only be bought for a session created by one of its slots, and only while it is enabled. The booking site only shows customers the tickets that fit the day they chose. A day with no enabled ticket isn’t offered at all. This is enforced by the system itself, not just the website.
Editing, disabling and deleting
| Action | Effect |
|---|---|
| Edit | Changes apply to new bookings immediately. Existing bookings are unaffected. |
| Disable / Enable | Stops or restarts sales. Use this for a ticket you’ll want again. |
| Delete | Customers can no longer buy it. Existing bookings keep their record of it. This can’t be undone. |
In the list, a ticket with no slots is flagged “No slots – can’t be booked”. Older tickets created before slots existed may show this: edit them to attach a slot.
Moving customers between tickets
If someone booked the wrong ticket, you don’t edit the ticket. You convert their booking.