|
Harry Parker
|
September 9, 2014 at 10:38 pm
This is regarding tickets.
Here is the use: I am selling skydives as a third party booker. That means they buy from me, redeem from the business.
I want the tickets to expire in 90 days.
I need 365 days of events.
1) Can I set expiration dates for the tickets? And can the event even handle this.
Example: A customer goes to the site, books a skydive for tuesday. But the ticket needs to be good for 90 days and actually expire, rendering it useless.
2) Can event espresso actually be set up this way? And if so how? One year long event? Or 365 individual events?
I hope this is clear enough. Thank you very much for your time.
HP
|
|
Dean
|
September 10, 2014 at 5:31 am
Hi Harry,
Thanks for your interest in Event Espresso.
How are you planning on accepting the tickets? Are you wanting them to be scanned or will it be a manual process?
You see, there isn’t a default way to expire a ticket, the only way I can think of currently would be to change the registration code to have the expiration date in it, so the business can check it against the current date.
|
|
Harry Parker
|
September 11, 2014 at 10:24 am
I am more than willing to talk development.
I am hoping we will scan the tickets at the business location. If not, The tickets will be collected and then scanned later to expire them.
It’s a complicated story based on the business owner, etc.
What cannot happen, is someone buying a ticket and then using it a year later. I want the tickets to expire after a specific time frame, ie, 90 or 120 days.
I want to be able to sell gift certificates based on this model as well. So they have to expire.
Perhaps there is another plug in that might work? Maybe I am trying to force something that was not meant for this purpose?
You guys are the closest I’ve been able to find to what I am looking for and LOVE the QR code scanning. It’s just our event is 365 days a year.
Suggestions?
Thanks again.
HP
|
|
Harry Parker
|
September 11, 2014 at 10:46 am
What if I found a Gift Certificate plug in? Could that be fitted into the sales process somehow when someone books their date?
Please forgive my newbness here. This is a major puzzle for me to put together.
|
|
Sidney Harrell
|
September 11, 2014 at 7:38 pm
The expiration feature would have to be built into the app side, which is a lot more difficult than server side customization, into the api add-on, into the server-side code, and custom fields added to the database. I would think the better strategy, buisness-wise, would be to use a ticket template that has something like “This ticket will expire on October 15th, 2014” in a huge, red font right next to the qr code.
You’ll need to consider that the ticket printing and scanning capability is only in the EE3 version. The feature is scheduled to be added in the next major point release of EE4. I would not try to add customization of this complex a nature to EE3 at this point in EE3’s lifecycle. It may be something that should be added as an add-on in EE4, and the development process for an EE4 version would be faster and easier to maintain.
|
