By season and time of day
A date range, and within it either the whole day, a band that repeats daily — six until nine every evening for a fortnight — or a specific list of departure times. Happy hour and twilight pricing without a spreadsheet.
Tickets and pricing
Timed entry, tours and sessions — priced the way demand actually behaves.
This is where most of the money is, and where most platforms stop at a calendar with one price on it. Here is everything underneath ours.
The pricing rules editor
Product editor → Pricing, with a schedule rule and an inventory rule both configured on one ticket type. Show the conflict check passing.
Three ways prices can move
Set them separately or stack them. Rules are checked against each other before you publish, so you cannot accidentally leave two fighting over the same Saturday.
By how full it is
The price climbs as the departure fills. The last seats earn what the last seats are worth, and nobody has to sit watching the calendar to make it happen.
By how far ahead they book
Early-bird pricing for the organised, last-minute pricing for the spontaneous, in as many steps as you want.
The rest of the pricing picture
- A 'was' price that stays honest. The struck-through price is worked out from what you are charging right now, not typed in once and forgotten. So when a busy Saturday lifts the real price, the saving shown next to it is still true — instead of quietly vanishing at exactly the moment it would have helped most.
- One ticket, four seats. A family pass is a single ticket with a single code, but it takes four places on the boat. Tickets issued and places taken are counted separately, which is why a twenty-seat vessel can never be sold twenty family passes.
- Minimums and maximums that make sense. A "minimum four" family ticket type means four if you take it at all, not four on every booking — so the type stays declinable. The stepper jumps the unsellable gap, and the rule is checked again at checkout rather than trusted to the browser.
- Tickets that are not tied to a date. Open-dated admission that expires at the end of its last valid day in your timezone — not at midnight UTC, which is how other systems kill a ticket on the morning it should still work.
Availability, waitlists and what you need to run the trip
- Private hires close the departure. Sell a whole boat to one group and the remaining seats stop being sellable — automatically, and without hiding the option from the people you want to sell it to. A departure that already has bookings on it cannot be bought out, so nobody turns up to find strangers aboard.
- Sold out stays visible, with a waitlist. A calendar full of gaps looks broken; one showing what has already gone looks busy. When space frees up, the people waiting are told in the order they joined, in the language they joined in, with a link that rebuilds their basket. Nothing is held for them, and the message says so.
- Boats, guides, rooms and kit. Attach the things a departure needs, and see the clash before it becomes a problem. A tentative plan only warns; something already committed — a booking taken, or a resource you pinned by hand — blocks properly.
- Change a lot of departures at once. Move times, change durations, adjust capacity, cancel, or open a waitlist across a whole run of dates. Anything already booked is left alone unless you say otherwise.
Forms and waivers, without a second subscription
Most platforms make you buy a forms product and glue it on. That is also why the answers end up somewhere useless.
Ask the right person
Not everyone on the booking.
- A form can be attached to specific ticket types, and to specific guest types within them — so the under-18 waiver reaches the child on a family ticket and never bothers the adult sitting next to them.
- Collect it once for the whole booking, or once per attendee. Make it required before payment, or offer it without blocking the sale.
- Nineteen field types including date of birth, file and photo upload, across as many pages as you need.
Ask at the right time
This is the setting nobody else gives you.
- Every form has a validity window in days. Zero means a fresh answer every single visit. 365 means an annual waiver. Anything up to ten years.
- That one number decides whether your regulars get asked again, and it is a setting rather than something baked into the software.
- Guests can update their own answers later, or you can lock them — because a countersigned waiver that someone can quietly rewrite afterwards is worse than no waiver.
Answers go somewhere useful
- Mapped onto real records. A form answer can land on the booking, the person who paid, the individual attendee, or the guest record itself — so it is data you can search and segment on, not a PDF in a folder.
- Locked away at rest. Answers, names, addresses and phone numbers are encrypted, and matching runs on a scrambled version of the contact details.
- Written once for the whole group. Head office can author a form and push it to every site, so the waiver is the same wherever a guest signs it.
A ticket type with forms attached
Product editor → Forms, showing an assignment narrowed to a guest type with a validity window set.
See it running on your own products.
Bring one activity, one ticket type and one price. We will show you what it looks like in a real checkout.