|
cmccreery
|
March 12, 2015 at 10:13 am
We have registrations for an event that allows users to pay by cheque. These users aren’t be counted as registered since they haven’t technically paid. But this creates an issue that if we have set a limit on registrations it’s possible that people paying online can fill the cap before someone paying by cheque. Is there a fix for this, or is this by design? Any suggestions on how to stop this?
Thanks,
|
|
Lorenzo Orlando Caum
|
March 12, 2015 at 10:29 am
Hi, that is currently by design. The problem with it working the way that you described is handling non-payments. For example, if you had an event with 30 spaces and 30 people registered but only half paid, then you would have an issue.
Here are the explanations of the various options:
Approved
A status of Approved means that a registration has been accepted as complete. The registration will count towards the registration limit, remaining tickets, and calculations for available seats. Payments (if necessary) can also be made by primary registrants with this status.
Pending Payment
A status of Pending Payment means that a registration has not paid but they ARE able to make payments (if necessary). Pending Payment registrations do NOT count towards registration limits, remaining tickets, and calculations for available seats. If registration for a free event occurs, then registrations are automatically set to Approved. For paid tickets, Pending Payment registrations are set to Approved when full payment is recorded.
Not Approved
A status of Not Approved means that a registration has not paid and they cannot make payments for towards an event. Un-approved registrations do NOT count towards registration limits, remaining tickets, and calculations for available seats. This setting differs from the “PENDING PAYMENT” default in that free ticket registrations and paid in full ticket registrations do NOT automatically switch the Registration to APPROVED. Instead, the event admin must manually set the registration to either “PENDING PAYMENT” for registrations requiring payments, or “APPROVED” for free events.
For a workaround, add a payment to the pending transaction for a penny with a note like this and set the status to Approved:
Event Admin – Waiting for Check
Then when the payment arrives, you can apply the full payment using the transaction details screen (same page as above).
—
Lorenzo
|
|
cmccreery
|
March 12, 2015 at 12:33 pm
Thanks Lorenzo.
Another question. Can I simply change the ticket prices for an event that is underway? The event had discounted ticket prices (no modifier used) like an earlybird discount. We’d like to change the tickets to the full price now but are confused with how this affects the current attendees or those that are pending payment.
|
|
Lorenzo Orlando Caum
|
March 12, 2015 at 1:26 pm
Hello again,
Since there are existing registrations linked to a specific ticket / pricing option, then Event Espresso will archive that ticket option and create a new pricing / ticket option in the same name and pricing.
—
Lorenzo
|
|
cmccreery
|
March 12, 2015 at 4:18 pm
Thanks Lorenzo. In our case can we remove the tickets we have (3 different types) and replace them with one new ticket type (regular price)? Or would it be better to just change the price of the other 3 to the new amount?
Thanks again.
|
|
Lorenzo Orlando Caum
|
March 12, 2015 at 4:29 pm
Hi, Event Espresso will automatically archive them once you change the pricing so you won’t be able to remove them.
If it did let you remove them and they were removed, then any attendees/registrants that are linked to those old tickets would now have missing ticket / pricing information.
Also, those archived tickets won’t appear on the front end. They are for your reference and to keep accurate pricing / ticket information for existing attendees.
—
Lorenzo
|
