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 Price Modifier | Event Espresso - Staging Server
For example, you might setup a discount for the first X amount of tickets that are purchased. The surcharges are a way to help with administrative costs.
Event Espresso 4 does not currently support promotion/discount codes.
I am still not quite getting it. If I am globally modifying the price why wouldn’t I just change the price?
If I want to manually book people onto a course where I have collected payment another way, or I want to manually change the price for an individual sale, can I do that?
The price modifiers are used as line-item detail to customers in their order confirmation, etc.. For example, you may say the base price for a ticket is $100, then you have a +10% processing fee, but they have a -$20 discount. The order confirmation will provide all that information to the registrant. This is helpful and often required by organizations and tax purposes. Does that help?
Select the Registrations for a single event, then at the top of the page you can Add a New Attendee. Then follow the process which is similar to the front-end registration: http://www.screencast.com/t/1ZijyiuGp
Viewing 3 reply threads
The support post ‘Price Modifier’ 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.