WooCommerce Bookings 3.10.0 adds a “Share max bookings per block?” resource setting, cuts the number of queries a booking form runs, and closes a long list of permission gaps across booking data.
The new setting solves an overbooking problem. Until now, max bookings per block was held separately by each resource on a bookable product, so a slot that was effectively full could still be booked again through a different resource. Turn on “Share max bookings per block?” and that allowance becomes a single shared pool — a booking taken on one resource counts against every other resource on the product. If you rent equipment from a common pool, run a space that can only host one group at a time regardless of which room is selected, or otherwise have resources competing for the same finite capacity, this is the setting that stops double-booking.
Booking forms are also faster. Availability for all blocks and resources now loads in one query instead of one query per block-and-resource combination. The more resources and the longer the scheduling window, the more noticeable the difference — forms that were slow to appear on complex products should load noticeably quicker.
There’s also a fix worth knowing about at checkout: orders containing bookings still awaiting confirmation can no longer be paid for. Previously a customer could pay before you’d confirmed the booking was available, which left you refunding. A few other corrections: imported Google Calendar event summaries now render as text in your schedule rather than as raw markup, the source files you select for a CSV import are kept after the import finishes, and cached availability no longer mixes up requests that show unavailable times with requests that hide them.
The bulk of this release is access control. Public availability and slot requests no longer expose unpublished or non-public booking products, and are bounded by the product’s booking window and a one-year limit. The store-wide booking calendar and store-wide booking notifications are now limited to people who can edit other users’ bookings. Saved cancellation links enforce your current cancellation policy and cutoff rather than the policy in force when the link was generated. Roughly a dozen further permission checks were added across admin and REST workflows. None of these change how the extension works day to day — they close gaps in who could reach what.
How to get it
Update to WooCommerce Bookings 3.10.0 in your WooCommerce dashboard. “Share max bookings per block?” is off by default and appears in the resource settings on a bookable product — switch it on per product where resources should share one allowance. Everything else applies automatically. If you rely on saved cancellation links, note that they now follow your current policy and cutoff rather than the one captured when the link was made.
Get WooCommerce Bookings | WooCommerce Bookings Documentation