|
Upstairs Circus
|
April 5, 2023 at 11:54 am
I am in the process of investigating migration from EE3 to EE4 and hit what I am thinking is a major road block for us…
We use EE as a reservation system (free registrations). In our use, one Primary Registrant manages the reservation (registration). In EE3, this is how the system works. One reservation for a party of 4 = one registration code. In EE4 it appears that one reservation for a party of 4 = four registration codes. This makes updates to party size (increasing parties or decreasing parties) rather difficult. It also makes the check-in process more labor intense because, in the case of large parties, it has to be done for each attendee rather than the one Primary Attendee.
My question is this: can the multiple registration codes in EE4 be turned off to work more like EE3 with a single registration code for the entire party? We’d like to use EE4 for the additional features, but may not be able to without the ability to turn the multiple registration codes off.
Thanks for your help!
|
|
Garth
|
April 5, 2023 at 2:06 pm
Hi there,
EE3 and EE4 are different in this area, with Event Espresso 4 trying to be more granular and transparent.
In EE4, the attendee data is split into Transactions and Registrations. Transactions are a one-to-many relationship (one transaction for many registrations), kind of like EE3. Registrations are a one-to-one relationship so that each attendee (even if the same person) has a registration record.
In EE4 the number of registrations or tickets to be sold are set on the number of registrations you allow at an event. Each type of ticket in EE4 can have a separate quantity too. Each event can have multiple types of tickets. So, there is a lot more flexibility with Event Espresso 4.
That fundamental system in EE4 cannot be changed. But how you set up Event Espresso could work so that you only accept registrations for one person, and I presume estimate the number of attendees and likewise the number of people being checked-in when scanning one ticket or checking-in one attendee. That seems far less accurate to me, but I don’t understand the business decision for your process.
|
