Best Practice for Handling Change Requests - Ticket Price Types in Altru

Bridget Brennan

Hello!

I'm curious if anyone has and would like to share their policy on accepting requests to add new ticket price types to Altru? I try to discourage anything that is not how we've structured our price type code table (currently: Adult, Senior, Student, Youth, Child; Group Adult, Group Senior, Group Student, Group Youth).

Examples: A few times we've looked at adding a ticket type in which the name can be changed per event (for partner events in which our partner wishes to have their name somewhere in the ticket) and a ticket type in which there are layered options for scheduled program events (Adult admission + reception). Ultimately, I've discouraged adding any ticket price types because I'm wary of the reporting implications down the line.

I wonder if we're (I'm) adhering to too rigid of a policy and if anyone has any general best practice thoughts on this topic. Thank you!

Crystal Bruce

@Bridget Brennan discussion moved to the Altru Community. Thanks!