|
Gilda Taffet
|
February 3, 2017 at 1:59 pm
Hello,
My client, Soil Born Farms, wants to be able to add registrants who are on a custom payment plan through the backend of the website during the time that an early bird rate is in effect (set up as Ticket #1). The amount that the person on the payment plan should pay is more than the early bird ticket rate. How can we generate an invoice that reflects the correct/higher rate rather than the early bird discounted rate that is in effect at this time? Thanks for any strategies you have for this situation. I thought maybe there was a way to set ups ticket that can’t be seen in the front end but ave not been able to figure that out.. Thanks for your help! Gilda Taffet
|
|
Josh
|
February 3, 2017 at 3:50 pm
Hi Gilda,
One way would be to set up a ticket that can’t be seen on the front end. There’s another topic from earlier this week that shows how:
https://eventespresso.com/topic/bundle-pricing-flat-price-or-rounding/#post-230673
Another way would be you use the Attendee mover add-on. So after they add the attendee, they can reassign the attendee to have the new ticket that’s not for sale yet.
https://eventespresso.com/wiki/eea-attendee-mover/
|
|
Gilda Taffet
|
February 3, 2017 at 4:04 pm
HI Josh,
Thanks for the strategies. I have a couple of questions:
1) For the invisible ticket function approach, would I have to go in and add a new/additional ticket ID to the function code each time the client sets up that type of back-end-only ticket on an event (they have a LOT of events…) or can we re-use that ticket ID somehow on multiple events?
2) What do you think about using css to hide that particular type of ticket (so we could use the same ticket name for, for example, payment-plan tickets that would be invisible from the front end). Then we could give that ticket whatever price we needed to. Is this a valid strategy as well or is there a downside to using css to hide a custom ticket like this? Thanks for your brain, talk to you soon. Gilda
|
|
Josh
|
February 3, 2017 at 4:26 pm
The ticket ID is unique for each ticket, so the ticket ID could not be re-used from one event to another. CSS should work as a way of hiding the payment plan tickets too.
|
