Need your input: Ticket PDF features

Dear customers

Today, I released version 2.6.0 and will start version 2.7.0 development. The two new features I want to work on is :

1. Allow collecting registrants information while using shopping cart (it has been asking by customers but I can only get back to it by now)

2. Ticket PDFs : Generating tickets PDF and send to registrants after payment completed. This ticket PDF can then used for registrants to bring to events and and process checking

3. Allow adding new members / removing members from existing registration

What I need help is about the feature #2. Do you need this feature? If so, for group registration, do we need to generate multiple PDF tickets (each for one group member) ? Do you have sample ticket layout which you want to use (or you would like to use)

Looking forward to receiving your feedback so that I can implement the features better

Regards,

Tuan

1. One of the odd things is that I can't have a group size = 1. So if this could solve that I'm interested.

2, Yes it would be useful. And the ability to split the PDF to individuals makes sense. QR Code to check them in please. (But need to find a way so that nosey people who scan the QR code don't check themselves in by mistake!)

3. Including from back end

Hi

Group size = 1 was supported from long time ago. Just edit the event, set "Min Number of Registrants For Group Registration" option to 1 and It would solve your issue

Regards,

Tuan

Oooh... will need to try that.

Yes it would be useful, although the users can also print out their email as ticket (as in one can simply turn the registrant confirmation email or the Thank you email into such a ticket, and that quite easily as well). I do see that there would be some added value but not that much.

Tim you are right but there are a few situations it is helpful:

- Someone buys the ticket as a present
- Multiple people on one invoice (e.g. a business purchase all arriving separately)
- Large numbers of people arriving together and wanting to check people in quickly on multiple locations (doors etc) (Thats the QR code bit)
- Places where it would be hard to tell if everyone really paid/booked etc because there are lots of people and no restricted number of seats
- Situations where there is a risk of ticket copying. The barcode would identify that.
- Ticket for free when might not invoice for free events?

All of the above can be done via the confirmation emails:

- Someone buys the ticket as a present -> Print out the "Registration confirmed" email (you can modify the email per event, although I see what you mean... Sometimes the price on it may not be that nice)
- Multiple people on one invoice (e.g. a business purchase all arriving separately)-> Set "Send confirmation email to all registrants of a group" and you are fine. Each one will get their own QR code in the email.
- Large numbers of people arriving together and wanting to check people in quickly on multiple locations (doors etc) (Thats the QR code bit)-> Each registrant of a group gets their own QR ticket anyway as of the last version. You can set it somewhere in the configuration. I forgot where, I am not using that feature yet.
- Places where it would be hard to tell if everyone really paid/booked etc because there are lots of people and no restricted number of seats-> print out each entrance ticket that each person will have received via the "Send email to each registrant of a group"
- Situations where there is a risk of ticket copying. The barcode would identify that.-> You can already. Just send different QR code to all using the stuff I said above.
- Ticket for free when might not invoice for free events? Dont put the bar code on the invoice, put it on the registration confirmed email...

At least that is the process that I am using/wanting to use...

3. Allow adding new members / removing members from existing registration
+1 : 3. Including from back end
+1: including modify on back end and support quantity custom fields (see this post )

1. Great! That'll be incredibly useful.
2. Personally, we don't need this.
3. We run 2 events concurrently, based on age. Sometimes I need to move one member of a group from 1 event to another, while leaving the remaining members of the group as they were. Sometimes, I need to cancel 1 member of a group.

As per other discussions in the past, a ticket feature is essential to me! That said, I have been managing by using the invoice feature although it does have some issues doing it that way and probably makes more sense to keep Invoice and Ticket as separate.

Features I think important:
* Being able to have a QR code on ticket.
* Allowing purchaser to specify if they want a single group ticket or individual tickets generated (and for group ticket, ability to show total number of people the ticket covers.)
* Generating tickets even no money paid (eg free tickets or 100% discount code used)

With current system the invoice misses out giving a full breakdown (since if you charge an amount for card transactions, say, that isn't shown) so would be good to also sort that out if separating out invoicing and ticketing.

Many thanks for making a great product and for fabulous developments!