Hello!
I'm wondering if anyone can share their process for upgrading from general admission to membership? We still have memberships set up as contributions but hope to transition to memberships as products soon. Our current process that I'll outline below is complicated for our ticket staff and often results in errors.
1. Customer purchases general admission and saves receipt. If they want to upgrade to a membership they can apply eligible price types towards a membership
2. Customer gives receipt to ticket staff the day of their visit and they pull up the original order, delete the eligible price types, and return the negative amount to the cash payment type. They DO NOT give the customer any cash. They make note of the price types returned and the balance.
3. In a new order they create the constituent record and add the membership to the cart. In the payments screen they apply the amount they returned as cash towards the membership. This balances out their cash drawer. It's also usually the step where mistakes happen.
4. Finally, they add the price types back to the cart at the member level and complete the transaction. The customer makes payment for any remaining balance.
This process is a major issue for our team. It also takes some time to process so it isn't a great guest experience. I'm open to any tips, tricks, solutions, etc! Thank you!!
Hello! I wanted to jump in here to say that this feature is being looking at in conjunction with the new Membership functionality coming out in v16! Some recommended practices regarding "Upgrade Ticket to a Membership" processes in v16 will be released with v16.0 or shortly afterwards. Membership Pricing Rules and Source Code tracking should help streamline this process in the new version.
In the meantime, Nancy's suggestion of using an On Account Payment Method for this process is definitely the way to go! To eliminate further opportunities for error, processing the exchange all in the original order would help as well, as long as there aren't other business needs (like High Museum's source code tracking) that would require the orders be kept separate.