If six of your padel courts are identical, asking a customer which one they want is a question with no useful answer — and it is actively expensive. They pick court two, court two is taken at seven, and they leave, while courts four and five sit empty. Dynamic allocation turns the question into the one they actually care about: what time. The booking then lands on whichever equivalent court is free.
Two costs, and most venues only ever notice the second one.
Someone wants seven o'clock. They tap court two, which is taken, and get told so. What a venue hopes happens next is that they try court three. What usually happens is that they close the tab — because they did not want court two, they wanted seven o'clock, and the system just told them no on behalf of a court they had no opinion about.
Left to choose, customers scatter. By Wednesday every court has a stray hour in the middle of the evening, and none of those hours are long enough for the 90-minute slot people actually want. You have plenty of availability and nothing sellable — the worst version of a full calendar, because it looks busy on the screen and quiet at the till.
Three steps, none of which the customer has to think about.
Tell the system which resources genuinely do the same job — the identical courts, the interchangeable pitches, the lanes.
The customer picks the activity and the time. Availability is answered against the whole group, not one court.
The booking is assigned to a free resource in that group. You still see which one, and staff can move it.
This is a tool, not a rule. Applied to resources that are not really equivalent, it produces complaints instead of revenue.
A show court, the one with seating, the pitch with proper floodlights. People choose these deliberately and will notice being moved off them. Keep them selectable in their own right.
The shallow-end lane for a beginner, the studio with the good sound system, the pitch nearest the car park for a junior session. If a customer would be annoyed to be reassigned, the resources are not interchangeable.
The four who have played on court one at eight on Tuesdays for three years are not looking for optimisation. Some venues run allocation for casual online bookings and keep standing arrangements pinned where they are.
Where you have several resources that do the same job — six identical padel courts, four 5-a-side pitches, eight swim lanes — the customer books the activity and the time, and the system places the booking on whichever of those resources is free. They never have to know they are on court four. You still see exactly which resource holds which booking, and staff can move it.
Because customers choosing for themselves scatter. Three bookings across three different courts at three different times can leave every court with an awkward hole in it, and a 90-minute gap split across two courts is two gaps nobody can book. When the system places bookings instead, it can keep them together and leave the free time in usable blocks. Same demand, more sellable hours.
Yes, and this is the part venues underrate. A customer who has picked court two and been told it is taken has hit a dead end, even when the venue is half empty — most people do not patiently try court three, they leave. Asking for a time rather than a court number means availability is answered once, against everything you own.
When the resources are not actually equivalent. A show court, the pitch with better floodlights, the studio with the good sound system, the lane nearest the shallow end for beginners — customers have real preferences there and overriding them creates complaints rather than efficiency. Use allocation for the interchangeable ones and let customers choose where the difference genuinely matters.
Every plan, including the free one. It is part of the booking engine rather than an upgrade, because the venues that need it most — a site with a row of identical courts — are not necessarily the largest ones.
On every plan, including the free one.