A season pass is bought once, up front, and then covers the holder’s own place on the tickets you choose for as long as it lasts. Manage passes under Operations > Passes.
Create a pass
| Field | Notes |
|---|---|
| Name | For example “Summer season pass”. |
| Description | Shown to customers on the booking site. Supports formatting. |
| Price | Must be above zero, in your system currency. Paid in full on purchase. |
| Valid for | 1, 3, 6 or 12 months, counted from the day the customer pays. |
| Tickets it covers | Tick at least one. Events can’t be covered. |
| Enabled | Untick to stop sales. |
How a customer uses it
- They buy the pass on the booking site’s Passes page with their email address. That email becomes a customer if it isn’t one already.
- The pass starts the day payment arrives. Until then it shows as Awaiting payment and does nothing. They get a “Season pass purchased” email.
- When they book with the same email, Gravity Pass spots the pass by itself. If it’s still valid on the date of the session and covers a ticket in their basket, one place is free: the dearest covered ticket.
- Anyone else on the booking pays as usual. A pass is personal and can’t be passed on.
Prices are worked out in this order: tickets, then any season pass the booker holds, then vouchers. A booking that ends up at zero is confirmed straight away, with no payment.
The pass used is recorded on the booking and shown to you in Bookings, as a “Season pass” line in the price breakdown.
Editing and deleting
- Changes only affect passes sold from now on. Holders keep the price, tickets and dates they bought.
- Delete stops new sales. Passes already sold keep working until they expire.
- Passes show on the customer’s page in the portal, with their dates and an Active, Expired or Awaiting payment badge.