Core Bookings 0.9.0: seat limits for individual sessions, with an interactive demo

I've released Core Bookings 0.9.0. You can now give each scheduled group session its own seat limit instead of using the same capacity for every time.

For example, a service can have a default of 6 seats, with 4 at 10:00 and 12 at 14:00. Changing one session doesn't change the others.

• Blank uses the default. Clear an override to return that session to the service's normal capacity.
• Zero closes an empty session. It won't appear among the available booking times.
• Existing reservations are protected. A lower limit can't undercut confirmed bookings or active payment, approval and waitlist holds.
• Customers see seats left. The booking form limits their quantity to the selected session's remaining places.
• The checks apply throughout the booking. Rescheduling, payment confirmation, waitlist claims and imports all use the relevant session limit.

There's a new hands-on seat-limit demo where you can try the whole workflow:

1. Compare the live table of custom, default and closed sessions.
2. Try the last available place in the 4-seat session, or book 8 places in the 12-seat session.
3. Open the workshop settings in the demo workspace and change an individual limit.
4. Reschedule or cancel your test booking, then reload the table to see the seats return.

After each daily reset, the 10:00 session starts with 3 sample seats reserved. The demo resets at midnight IST, with its dates and seat limits advancing together. Please use made-up details; payments and outbound email are disabled.

You can update from WordPress Dashboard > Updates with your Core Bookings license active. Core Bookings is still in beta, so I recommend checking your setup on staging first.

If you run into a booking rule that doesn't behave as expected, reply here with the steps and I'll look into it.