Commerce BAT Availability

Commerce BAT connects Drupal Commerce with BAT (Booking and Availability Tools) so you can sell bookable products and services through Commerce’s cart and checkout. It supports date-range rentals, reservations, appointments, lessons, and tickets, with configurable schedules, inventory capacity, and administrator availability management.

The 3.x series uses Commerce BAT’s own reusable native calendar for customer booking and administrator blockouts. Booking rules and reservation validation remain server-side, separate from calendar presentation.

Release status and important warnings

The 3.x series is currently alpha software. Test upgrades and booking workflows on staging before deploying to a live shop. Automated tests cover Drupal 10 and 11, but an alpha release is not a guarantee of production readiness.

Do not use the following releases:

• 1.5.0
• 2.x releases from 2.0.0 through 2.2.0-alpha2, inclusive

These releases contain a known Drupal 10 checkout compatibility defect: the checkout handler calls Transaction::commitOrRelease(), which is not available in Drupal 10. The 2.x fix was released in 2.2.0-alpha3. This identifies one confirmed defect; it does not mean that later releases are free of other issues.

Features

• Reusable Booking Types for date ranges and timeslots.
• Date-only bookings or timed date ranges with explicit start and end times.
• Native embedded and popup calendars on Commerce add-to-cart forms.
• Availability Profiles for opening hours, recurring schedules, exceptions, and valid times.
• Capacity Presets, independent inventory, shared capacity pools, and seats-per-quantity rules.
• Configurable minimum booking notice for timeslots and timed date ranges, enforced during booking validation and checkout.
• Date-range pricing that includes billable days in the unit price, with Commerce quantity applied normally.
• Administrator blockout and restore workflows for all or part of a resource’s capacity.
• UTC storage for time-based bookings and booking-aware date/time formatting.
• Reservation synchronization for order placement, cancellation, and supported order-item changes.
• Audit logging, BAT relationship reports, health checks, and bulk order synchronization.

Included companion modules

• commerce_bat_calendar: the reusable native calendar presentation.
• commerce_bat_ui: an optional configurable booking page/block with a product catalog, calendar, selection controls, and Commerce add-to-cart integration.
• commerce_bat_example and commerce_bat_ui_example: demonstration configurations for exploring booking setups and presentation options.

Templates, presentation options, component plugins, and service interfaces support custom integrations. Example modules are intended for development and evaluation, not automatic production-shop configuration.

Post-installation

1. Enable Commerce BAT, its dependencies, and commerce_bat_calendar for interactive calendars.
2. Open /admin/commerce/config/commerce-bat.
3. Create Booking Types and configure their schedules, capacity, booking windows, and optional minimum notice.
4. Assign a Booking Type to each bookable product variation.
5. Confirm the BAT Date/Time Picker widget on the order-item add-to-cart form display.
6. Configure shared calendar presentation settings and, optionally, enable commerce_bat_ui for dedicated booking interfaces.
7. Manage blockouts at /admin/commerce/config/commerce-bat/blockout.
8. Verify add-to-cart, cart, checkout, order changes, cancellation, and shared-capacity behavior before launch.

Additional requirements

• Drupal 10 or 11, with compatible Drupal Commerce and BAT releases.
• Drupal Commerce and its required product, order, cart, store, and price modules.
• BAT and its required unit and event modules.
• Core date-range support for the canonical booking field.

The 3.x native calendar does not require FullCalendar or Flatpickr. Bundled third-party calendar integrations have been retired. Developer-provided integrations remain supported through the calendar plugin API.

Upgrading

Back up the database, review the README’s migration instructions, run database updates, rebuild caches, and validate booking workflows on staging. Upgrades from older versions can change configuration and calendar presentation, so review custom templates and integrations carefully.

Similar projects

BEE (Bookable Entities Everywhere) provides BAT-based booking for Drupal content and supports Commerce payment integration. Commerce BAT focuses on Commerce product variations, reusable booking configuration, shared inventory, and customer and administrator calendar workflows.

Supporting this module

Please use the Drupal.org issue queue for bugs, support, and feature requests. Include the module version, Drupal version, reproduction steps, and relevant error messages.

Documentation

See the README and documentation included with the module for setup, migration, extension points, and verification guidance.