WooCommerce Bookings

When booking is a product rather than a side feature, the WooCommerce-native answer is WooCommerce Bookings: sell time or date-based inventory – appointments, rentals, reservations, tours – as products inside the store customers already know. Bookable products carry durations, availability windows, resources with capacity, and person types, and the checkout is WooCommerce’s own, so bookings ride the same cart, payment, and order flow as physical goods.

The current 3.10.0 release (September 2026) is a serious maintenance chapter – a shared-capacity resource setting solving overbooking, a query-count reduction that speeds booking forms, and a full access-control pass across booking data. Here’s the working review.

Competitive Features

• Bookable products inside WooCommerce. Bookings are products – they enter the cart, check out, and manage like any WooCommerce order. No separate booking system to maintain or pay for separately.
• Resources with capacity. Assign resources (rooms, instructors, equipment) to bookable products, each with schedules and capacity – and 3.10.0’s new “Share max bookings per block?” setting makes multiple resources share one booking allowance, closing the overbooking path where a full slot remained bookable through a different resource.
• Duration flexibility. Fixed-duration blocks, customer-defined durations with min/max ranges – appointments, rentals, and multi-day reservations in one product type.
• Person types. Different pricing for different participant categories – the group-booking and per-person pricing model.
• One-query availability loading. 3.10.0 cut booking-form queries from one-per-block-and-resource to a single query – complex products with many resources load noticeably faster.
• Rescheduling built in. Reschedule any booking straight from the admin – the operational reality that bookings change.
• Google Calendar sync. Two-way calendar integration with imported event summaries rendering correctly.
• Access-control discipline (3.10.0). Availability and slot requests no longer expose unpublished products, store-wide calendars are restricted to editors, saved cancellation links follow current policy – roughly a dozen permission gaps closed.

Key Features

• Availability rules. Booking windows, buffer periods, blocked dates, and per-day/time availability – the scheduling constraints real operations need.
• Requires confirmation mode. Bookings can require manual confirmation before payment – and 3.10.0 stopped orders containing unconfirmed bookings from being paid prematurely.
• Cancellation policies with cutoff. Policies with cutoff windows enforced on saved links – not the policy captured when the link was generated.
• CSV import/export. Booking data moves in and out with source-file retention after import.
• Cached availability correctness. Cached requests no longer mix “show unavailable times” with “hide them” modes – the cache-integrity fix.
• Block checkout compatibility. Works with the Cart and Checkout blocks, with place-order labels handling the confirmation state correctly.
• Performance work. Slow checkout performance fixed for high-volume sites – the scale path taken seriously.
• Email notifications. Booking confirmations, reminders, and cancellations ride WooCommerce’s email system.

Comparison with Competitors

WooCommerce Bookings vs Order Delivery Date Pro

The bookable-inventory versus order-scheduling boundary – the most common confusion in this category.

Aspect	WooCommerce Bookings	Order Delivery Date Pro
Model	Bookable resources with time inventory	Delivery scheduling for orders
Capacity	Per resource, shared pools (3.10.0)	Per slot lockout
Use case	Appointments, rentals, tours	Local delivery fleets
Person types	Native	Not applicable

If customers book time on a resource, the delivery scheduler is the wrong tool; WooCommerce Bookings is the right one – and delivery businesses have the reverse need.

WooCommerce Bookings vs Amelia

The platform-native versus standalone comparison for appointment-heavy businesses.

Aspect	WooCommerce Bookings	Amelia
Commerce integration	Native WooCommerce	Own payment stack
Customer panel	Via WooCommerce account	Dedicated panels
Packages	Via person types/bundles	Native packages
PMS-style reports	WooCommerce order data	Booking-specific analytics

Amelia wins for service businesses that want a standalone scheduling app; WooCommerce Bookings wins when the booking needs to live inside the store’s commerce flow – cart, checkout, receipts, refunds all unified.

Recommended Stack: Bookable products pair naturally with the same checkout optimization as any store – hospitality operations outgrow generic bookable products into the Vik Booking PMS – rooms, seasonal rates, channel distribution – the industry-native escalation path this product starts.

Official Changelog

The registry tracks one version line for this plugin; the changelog below covers the current registry version.

Version 3.10.0

Release Date: September 2, 2026

• New “Share max bookings per block?” resource setting: one shared booking allowance across all resources on a product – prevents double-booking through competing resources
• Performance: availability for all blocks and resources loads in one query instead of one per block-resource combination
• Orders containing bookings still awaiting confirmation can no longer be paid for
• Imported Google Calendar event summaries render as text in the schedule
• CSV import source files are kept after the import finishes
• Cached availability no longer mixes show-unavailable and hide-unavailable request modes
• Access control: public availability/slot requests no longer expose unpublished or non-public booking products; store-wide calendars and notifications limited to booking editors; cancellation links enforce current policy and cutoff; roughly a dozen additional permission checks across admin and REST workflows

Frequently Asked Questions

What kinds of businesses is it for?

Anything selling time on a resource: appointments, rentals, tours, classes, equipment, spaces. Bookable products define duration, availability windows, resources with capacity, and person types – all inside WooCommerce’s product system.

Is the GPL version the full plugin?

Yes. The GPL build is the complete source under its original license with all booking features enabled – resources, person types, confirmation flows, calendar sync. The vendor license key for auto-updates and WooCommerce.com support is the only absence.

Can I use it on multiple sites?

The GPL license permits unlimited installations across personal and client sites without per-domain activation.

What does the shared-capacity setting do?

The 3.10.0 “Share max bookings per block?” setting turns per-resource booking allowances into one shared pool – a booking on any resource counts against all of them. It’s the fix for equipment pools and spaces where only one group can be present regardless of which room was selected.

How does it handle confirmation workflows?

Bookable products can require manual confirmation. The 3.10.0 release specifically stopped orders containing unconfirmed bookings from being paid – customers can no longer pay before you’ve confirmed availability, eliminating the refund-after-payment failure mode.

How is the security posture?

Actively hardened: 3.10.0 closed public availability/slot exposure of unpublished products, restricted store-wide calendars to booking editors, bounded requests by booking window and a one-year limit, and added roughly a dozen permission checks across admin and REST workflows. Running the current release is the safe configuration.