Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Different Price for a second, third, etc. attendee | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Different Price for a second, third, etc. attendee

Different Price for a second, third, etc. attendee

Posted: September 8, 2012 at 6:50 pm

Viewing 1 reply thread


mminten

September 8, 2012 at 6:50 pm

I have an event that costs 100.00 for the first attendee and 75.00 for each additional attendee. How can I set up the event to work like this?


Sidney Harrell

  • Support Staff

    •

September 10, 2012 at 11:00 am

While we don’t have an out of the box solution for your use case, I can suggest the Volume Discounts add-on. You could set it to take 15% off the cart total after the first ticket.
With your model, 1 ticket is $100, 2 tickets is $175, 3 tickets is $250, 4 tickets is $325, and 5 tickets is $400.
With the 15% off model, 1 ticket is $100, 2 tickets is $170, 3 tickets is $255, 4 tickets is $340, and 5 tickets is $425.
The only way I can see to do exactly what you’re asking would be to start writing it with customized code to override some of the core functions in EE.
Viewing 1 reply thread

The support post ‘Different Price for a second, third, etc. attendee’ 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.

The original Forum description...

Status: closed

Updated by Sidney Harrell 12 years, 4 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server