Courts and peak pricing

A court, pitch or bay is booked like any other person or resource — add it on /app/bookings under Who takes bookings, with the Court / pitch preset if you want its own starting defaults. This page covers the two things specific to running several of them: the grid view, and pricing an hour higher when it’s in demand.

The court grid

On /app/reservations, a venue with at least one court gets a second way to view the day: a Grid toggle next to the usual timeline. Courts run as columns, time down the side, so you can see every court at once instead of one merged list.

The grid’s rows run through the venue’s open hours for the day, not only the hours something is booked — a quiet afternoon still shows every free row, not a gap. It’s the same day’s bookings underneath, just a different arrangement; there’s nothing new to load or keep in sync.

Peak pricing

A service can carry a list of peak windows — day of week, a start and end time, and a price for that window. When a booking’s start falls inside one, that price is used instead of the service’s ordinary one.

There is no dashboard screen for this yet. Set peak windows with your agent’s add_service or update_service tool, on the service’s peak field.

A few rules worth knowing:

• Windows can cross midnight. An end time earlier than or equal to the start means the window runs past midnight into the next day.
• The more specific window wins. If two windows both cover the same moment, the shorter one applies.
• Two equally short overlapping windows are refused when you set them, rather than silently picking one — you’ll need to adjust one so they don’t tie.
• A variant’s peak price scales with its own duration. If a 90-minute option is 1.5× the base service’s length, its peak price is 1.5× the peak price you set, rounded to the nearest unit — you set one peak number, not one per variant.

What’s frozen once a booking is made

The peak price that applied when a court was booked is recorded on the booking itself. Changing your peak windows tomorrow never re-prices a court someone already booked — the same principle as everywhere else in Book that a rule change shouldn’t reach into the past.

This also means the deposit a guest pays is always worked out against the peak price that applied at booking time, never today’s rule.

At the register

The register does not know about peak pricing yet — a peak court still shows at its ordinary catalog price, and your staff ring it up by hand. Book’s fiscal path is frozen this release, so nothing adjusts that line for you. Instead, your team sees the quoted peak price on the booking — on Today’s timeline and in the court grid — and rings that amount.

A deposit only covers the difference when it is a full deposit, taken at the quoted peak price: then there is nothing left to collect. A fixed or per-guest deposit is its own amount and does not follow the peak price, so the rest is collected at the register as usual. Moving a booking re-quotes it at its new time; money already taken is not adjusted.