Okey team, is time to talk...
There is no way we still do not have the option to limit the number of bookings per email / user.
Limiting just by frequency, is very restricted for such an amazing product as Fluent Booking.
Consultants, creators and many other FB users need you here ;)
eg.: You sell a service, x bookings included. Fluent Booking limits feature allows you to set this up. Done.
The current picture, is a really boring workaround of credits systems, custom fields... No bueno :(
Thank you!
At the moment, FluentBooking does not have a built-in UI option to limit the number of bookings per attendee email or user. I will take this as a feature request and forward it to our R&D team for further investigation. Hopefully, they will conduct a thorough review and pass it on to our development team for future implementation.
However, this can be achieved using custom code by leveraging the fluent_booking/before_creating_schedule hook. This hook runs before a booking is created, allowing you to prevent duplicate or excessive bookings.
For example, if you’d like to allow only one active booking per email per event, you can use the following snippet:
A few variations you might find helpful:
-
Apply the limit across all events: Remove this line:
->where('event_id', $calendarEvent->id) -
Only count upcoming/active bookings (exclude completed): Use:
['scheduled', 'pending', 'reserved']
This approach gives you the flexibility to define booking limits based on your specific requirements.
Hopefully, this might help you in this matter for now.
Ruman Ahmed thank you Ruman! I did not know it was possible to make this customization: as always, impressed by the flexibility of the fluent products!
That being said. I really hope this could become native to the core 😄
Jorge de los Reyes thank you so much for your kind words! I’m really glad to hear that the customization worked for you.
I will take this as a feature request and forward it to our R&D team for further investigation. Hopefully, they will conduct a thorough review and pass it on to our development team for future implementation.