Problem/Motivation

I am currently migrating existing Drupal 7 sites to Drupal 11.

In Drupal 7 I used the Simple Reservation 7.x-1.0 for appliances / equipment usage reservation. It fulfilled he requirements we had.
People reserve appliances / equipment that they will borrow for a certain period (days). They check if it is available, they reserve it, and it’s done.

In Drupal 11, it seems that BEE could fulfill our requirements.

I installed BEE. Also Commerce and BAT as they are required. It seems that BAT is not maintained / available anymore (at least this is what the « checking updates report » indicates).

I nevertheless installed all that was required and tried to move forward.
I had a look at the « outdated » video
https://www.youtube.com/watch?v=rhSqDvgfrCU&list=PLa9YKhpnU_AxCLeOHuJPyM...

I also went through
https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib...

Right now, I feel like I am stuck. Not knowing exactly what to do in order to put my hands into the BEE solution, understanding how it works and being able to build with it for the reservation solution I am looking for.

Any advice on how I could move forward ?
Thanks in advance.

Regards.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Sponsorship

Comments

dpierre created an issue. See original summary.

afagioli’s picture

afagioli
Location Rome
commented

Thank you for reaching out and for your interest in using the BAT and BEE modules for your equipment reservation system in Drupal 11. We appreciate your detailed explanation of your migration from Drupal 7 and your efforts to explore these modules.

Clarification on Module Maintenance

First, we’d like to assure you that BAT and BEE are actively maintained. The latest stable releases are compatible with Drupal 11, and we are committed to ensuring they remain up-to-date. If the "checking updates" report indicates otherwise, it may be due to a temporary caching issue or a misconfiguration. We recommend:

Ensuring you have the latest versions of BAT and BEE

Checking the official Drupal.org pages for these modules for the most recent updates:

Breaking Down Your Project into Manageable Steps

We understand that building a reservation system can seem overwhelming at first. To help you move forward, we suggest breaking down your project into smaller, actionable steps. Here’s a suggested progression:

# Set Up Your Equipment as Bookable Entities

## Use BAT to define your appliances/equipment as "units" that can be reserved.

## Configure availability settings for these units (e.g., default availability, booking states).

# Configure the Booking Workflow

## Use BEE to create a booking entity type tailored to your needs (e.g., "Equipment Reservation").

## Define the booking workflow (e.g., pending, confirmed, canceled).

# Create the Reservation Interface

## Use BEE’s built-in views and forms to allow users to check availability and make reservations.

## Customize the booking form to capture necessary details (e.g., dates, user information).

# Test the Reservation Flow

## Simulate reservations to ensure availability checks, conflicts, and notifications work as expected.

## Test both the frontend user experience and backend administrative tasks.

# Refine and Extend

## Add additional features, such as email notifications or integration with Drupal Commerce for payments (if needed).

How to Seek Further Help
As you work through these steps, please feel free to post specific questions or issues you encounter. For example:

# "How do I set up custom availability states for equipment in BAT?"

# "How can I customize the BEE booking form to include additional fields?"

# "How do I display availability calendars for equipment?"

By splitting your project into smaller slices, you’ll find it easier to troubleshoot and make progress. The Drupal community and our module maintainers are here to help with specific use cases.

I'm confident that with a step-by-step approach, you’ll be able to build a robust reservation system tailored to your needs. Don’t hesitate to reach out with specific questions as you progress!

Let us know how it goes

afagioli’s picture

afagioli
Location Rome
commented
Status: Active » Postponed (maintainer needs more info)
pozi’s picture

pozi commented

Hello, @afagioli, thank you for detailed explanation on each step. I am about to implement reservation of "Commerce Core" (old "Drupal Commerce") entities. I picked as bookable entity/bee unit will be "commerce_product_variation--default" not "commerce_product--default" since it stores the price. Let me know please if this is a good apporach? I checked "Bee Hotel" module, where commerce entities was only referenced in a filed. I want to use custom price alterators (i saw "Bee Hotel" alterators but for my usecase it is too much) i just need "Commerce Core" ecosystem alterators "Commerce Promotion", "Commerce Pricelist". Or you think easier for my usecase will be to base on "Bee Hotel" module? This implementation will be headless so i will reuse REST APIs too for checking avaiability. Thank you in advance for any suggestions.