In regard of the sharing the Resource between Services I am not quite sure if the function does works as excepted and or if it's a possible bug: 

"For example, you’d add a resource named “Chair” and set its quantity to “3“. When you select the share option, all available services will share these 3 chairs, so even though you have 6 barbers that are providing the same services, only 3 people will be able to book at the same time,"

When adding a Resource to in the Appointment sections we are provided this option"

1. Resource quantity is shared among the selected items - The resource quantity will be shared among all selected services, employees, and locations. 

2. Resource quantity is unique for selected services / The resource quantity will be counted for each selected service separately."

From what I understand - The difference between the two services is that either the Resource is available for every service, (employees and locations) or the Resource is only available for only one service.

But there is no option in regard of the making the Resource available unique for each Appointment, bookings. 

Let say the number of people who can join that service is set to 10 and the quantity for the resource is set to 10, that would allow 10 persons to book the same Resource independent of number of different bookings. In worst case - 10 different persons could book the same Resource at the same time. In other words, if the resource is a chair at the barber shop, then everyone must stay in que and wait for the other ones before them to be finished. That make no sense. 

Of course, if the Resource at a Barber shop is a chair, then you set the capacity to 1. But if the Resource is a table or room, and the capacity is above 1, it would allow different Appointments to book the same Resource as long the as long the Resource have capacity until it is fully booked.  The only option not to get double booked is to set capacity to 1. 

If a group of yoga trainers who train together at the same time each week at the same training room, (Resource), another group of yoga trainers could join the same training room to the same yoga session as long the quantity of the Resource allows it. I am not sure the first group of yoga trainers would appreciate that.

On the other hand - If the quantity of Service is set higher that the quantity of the Resource, it will not tell the person who books, that the Resource is fully booked. The only schedule time it cannot book is when the Resource is occupied - In other words:

"Everything related to time slots will continue to work in the same manner if you don’t add any resources – meaning that if you have a single service and 3 employees assigned to that service during the same working hours, an appointment will be bookable as many times as there are employees."

In other words - If there is noe chair available to be barbered, you can still book, but you must stand or laydown on the bench or the floor, whatever... Or if the yoga class is fully booked, you must do the exercise at the corridor, outdoors, whatever, because the Resource is full.

In my opinion - This does not make any sense - 1. The quantity of how many who can join the service must be limited to the quantity of the capacity the Resource, or 2. The "Resource quantity must be unique for each booking" (not the service). and or 3. If there is no Resource available, the Customer must be placed on a waiting list or forwarded to another Resource that is available., either at the same location or at another location.

The capacity a service should first of all be connected to the number of employees at work who can deliver the service - Different productions require different numbers of employees. Thereafter, the number of bookings at the same time should be limited by the quantity of the Resources available when the production of the service is scheduled. If one booking require all of capacity of one Resource, even some chairs etc. is not occupied, it should be marked is fully booked when the Customer require that. 

If done in this way, it would WP Amelia would be a more generic booking system that also could be used for booking table at a restaurant. With the options in Wp Amelia today, all the tables must be listed in a Catalog-booking-form because each table as a Resource the quantity cannot be higher than 1. If the quantity is above 1 the booking system will fill up the next chairs around the table which I am not sure if the customers would appreciate....

In regard of my remarks here - The option "Minimum Capacity" does not have a practical meaning unless the "Resource quantity must be unique for each booking". If you are going to book a Resource that have a lot of capacity, then it makes sense if each booking must fulfill a minimum. For example, if someone wants to make an exclusive booking for their group of yoga trainers, a number of minimum 10 participants should be fair if the capacity of the training room is 15.

Regards

PAA