Posted: April 4, 2018 at 9:36 am
Is it possible that registrants with the status “not approved” and “pending payment” would be counted to the maximum ticket/datetime attendee count? The reason for that is that events can only start at a specific count of attendees and the current procedure is, that we send out the invoices after the start. Current procedure: Desired procedure: |
|
Hi there,
No, only Approved registrations count towards the sold values of an event.
If you have a set number of registrations on the event then you need to set the default registration to ‘Approved’, as you are now, or use ‘Not Approved’ and the admin would need to monitor the registrations themselves.
What problem do you have with this method? |
|
If only approved registration count towards the sold values of an event, than we can’t use the registration and let the people pay at the same time. The Problem is, that if we have 15 spot available and we have e.g. 13 approved on that list. It is clear that the event can start and I set them to “pending payment” so that they can pay for the event, the result is that all 15 spot are available again and the event could easily be overbooked. Thats why I was wondering if the registrants with the status “not approved” and “pending payment” could reserve a spot in the event. |
|
Ok, but why are you changing the users from Approved to Pending Payment? The users can still pay for their registration whilst the registration status is Approved. |
|
Okay, still figuring out the system, thank you for the clarification. I would like to prevent the attendee to pay for the event before we confirm the start. I know I could manually check/uncheck the pay-method the attendee can see at the registration (Add-on pay method pro), but I would need to do that for every event (hide before and check after the confirmation). It would be much easier if the registrant with the “not approved” status would reserve a spot. |
|
That’s the only way I can think of doing what you are trying to do. Or use the DRS of ‘Not Approved’ and then manually monitor the registrations, if you need X amount of registrations before an event can take place then you set them to Not Approved, and then when you have X amount of registrations, set them to Approved manually and trigger the emails to request payment.
Whilst it may sound easier, that a whole lot of logic that needs to be added to monitor the not approved status to increment/decrement the sold values when a registration is set to/away from that status. It’s really not as simple as it sounds. |
|
I understand that the logic behind that is complex. Because you have a much deeper understanding of the system, I wanted to ask and geht all important information. Thank you for the clarification. I’ve tested the system and the workflow for that and we can make that work that way. |
|
The support post ‘Invoice after Eventstart’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.