Ability to include add-on pricing to camps based on registration questions
We allow camp participants to add a la carte lunches & after care. Currently this requires multiple events per week of camp. It would be much more user friendly to add the lunches & after care to the form with a fee associated to the questions that can already be added to the registration forms - i.e. checking "yes" to Monday lunch adds $10 to the registration. It would make sense that these would be added in Altru as "fees" and these fees would be associated with registration questions.
Guest
I came here to suggest this and see that it's been in "discovery" since 2018 but hasn't been implemented yet. We are trying to set up camps that offer full day and half day (either morning or afternoon) sessions, as well as optional before and after care for all sessions, but there does not seem to be any way to set up all the different permutations that we would need. It would be so much easier to just add registration options so that people can choose full or half day and then add before and/or after care as needed. We are probably going to have to find a separate camp management software to manage our summer camps because of this shortfall.
Attachments Open full size
Hi everyone!
We are currently in discovery for this idea. If you'd like to participate in the discovery process and provide feedback to our team about event add-ons, please email me at jillian.lewis@blackbaud.com to schedule a call.
Thank you!
Attachments Open full size
or perhaps a better implementation of this request...
allow logic-based price types to appear as sub-price types if the main price type is selected.
In my example, we will register someone for a concert. This is a pre-registered event. So if they select adult/child ticket and they would like to add pre-show dinner to the ticket, once they select a main ticket, the sub-ticket for dinner would show up with its own quantity field. The sub-price type's quantity would max out when it equals the main price type, so one person can't buy two dinners accidentally.
I think this implementation would help the OP and be more intuitive for other users to set up for their own organizations.
Attachments Open full size