Four different things under one roof, and three different systems
The ropes course books by the session. The lanes book by the hour. The play area lets people wander in all afternoon. The cafe seats them afterwards. Almost nobody sells software that handles all four, so most venues run several and join them up by hand.
One customer, one booking, one night
A family books the ropes course, adds a lane, and eats afterwards. Three systems make that three unrelated transactions and a customer record in each.
One account makes it one visit. You can see what the afternoon was actually worth, and so can whoever is on the desk when they ask to add something.
And they should not all be forced into one shape
- Sessions
- Sessions with a fixed capacity.
- Hourly bookings
- Hourly bookings on a resource.
- Timed entry
- Timed entry with a cap on how many are inside.
- Tables
- Tables that push together.
Set each attraction up the way it actually works. None of them has to be squeezed into a model built for something else.
The same people run more than one thing
If one supervisor covers the ropes course and the climbing wall, both cannot run at once no matter what the booking screen says.
Staff and equipment count towards availability. Your team stops finding out the hard way at two on a Sunday.
What the whole site did, not four separate answers
Takings across everything under the roof, in one place, going back as far as you have been trading. Which attraction carries the weekend. Which one is quietly costing you money to open.