Feature Requests

Each booked attendee to be deducted from a subscription limit (to set payment for attendee rather than payment for a booking)
We are setting a reservation system for a child group. We have multiple attendee activity and need a parent to book for e.g 1 child/attendee or 2 children/attendees. When a subscription is sold with a limited number of booking (e.g. 20) for an activity with e.g. 10 max attendees, we need that the 20 limit applies on number of attendees rather than on number of booked timeslots. Current feature: subscription for 20 bookings (for an activity available to 10 attendees) allows one subscriber to book 20 timeslots for up to 10 attendees each. Hence the subscriber pays for 20 bookings (and we expect 20 time slots with 1 attendee - the price of the subscription is set accordingly), but the system allows to book up to 200 attendees (subscription limit multiplied by attendee limit). Request: to match subscriptions limit with number of maximum of attendees available for the subscriber. Practical use: Via subscription, a parent with e.g. 2 children would pay for 20 entrances to an activity and could "consume" these 20 entrances (attendees) in selected time slots (e.g. could book activity 20 times for 1 attendee or 10 times for 2 attendees). Hence the system would allow to set a price per attendee rather than per number of time slots. [ALTERNATIVE/WORKAROUND REQUEST: to set a maximal limit of attendees for each booking/timeslot in a multiple attendee activity - this would ensure that one booking in a subscription = one paid attendee (the app allows booking of the same timeslot, hence the parent with 2 children would need to book for the same time slot twice in which case the subscription limit is correctly deducted by 2 bookings)].
0
Load More