Set it up once and it rolls forward by itself

Describe your sessions as repeating slots, attach tickets to them, then add season passes, events and vouchers when you need them.

See it in action All features

You choose: how many months ahead sessions can be booked
1 to 12: month season passes
3 ways: to limit a voucher: reusable, single use, once per customer

Slots

A slot is a repeating bookable time. There is no calendar to maintain.

Repeating times

Set a capacity, the days of the week, a start and end time and an optional date window, such as the school holidays.

Sessions created for you

Each day a slot applies to becomes a session. You set how many months ahead riders can book, the window rolls forward every hour, and a saved slot generates its sessions immediately.

Safe edits

Change a slot and future unbooked sessions follow. A session that already has bookings is never moved or deleted, and you are told how many were left alone.

Switch off and on

Deactivate a slot and its future sessions without bookings are removed. Reactivate it and they come back.

Tickets

A ticket is what a rider buys.

Name, description and price

Add an optional ride count, and switch a ticket on or off at any time. Prices use one currency for the whole park.

Attached to slots

A ticket is sold only on the slots you attach it to. The server enforces this, so a ticket cannot be bought for the wrong session.

Child pricing

Give a ticket a minors price, or set it to zero so children ride free.

Changes apply to new bookings

Edit or disable a ticket and it takes effect immediately for new bookings. Existing bookings are left alone.

Season passes

Riders buy a pass once and stop paying for their own place.

Valid for 1, 3, 6 or 12 months

Each pass has a price, a description and the tickets it covers. It starts the day payment succeeds.

Applied automatically

When a pass holder books, the price of one place comes off: the dearest ticket the pass covers. Anyone else in the party pays as usual.

Personal to the holder

Returning customers confirm their email with a code before booking, so a pass is only ever used by its holder.

Bought on your own page

Riders buy passes from a passes page on your booking site and get an email with the dates they are valid for.

Terms are kept

A bought pass keeps its own copy of the name, price, tickets and duration. Editing or deleting the pass later changes nothing for holders.

Events

A one-off date with its own page, tickets and capacity.

A date, a price and a capacity

Set a date, a start and end time or all day, an optional capacity and a picture. Leave capacity blank for no limit.

On the calendar and on its own page

Events sit beside regular sessions on the booking calendar, and each has a page with a readable address and its own title and description for search engines.

Protected once booked

You cannot lower a capacity below the places already booked, or delete an event that has bookings.

Waiver optional

Mark an event as not needing a waiver and no waiver email is sent for bookings made up only of its tickets.

Vouchers and closures

Offer discounts and close the park without touching a booking.

Percentage or fixed amount

Create a code worth a percentage or an amount off, with an expiry date.

Choose what it applies to

Limit a voucher to certain tickets, exclude events, and decide whether it also works in your merchandise shop.

Control how often it is used

Make it reusable, single use, or single use per customer, with customers told apart by email address.

Closures

Close a single day or a date range, such as Christmas Day or winter maintenance. Existing bookings are not touched, and removing a closure makes the dates bookable again at once.

Ready to fill your next session?

Tell us about your bike park and we'll show you Gravity Pass in action.

Book a demo