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
Surcharge to be added per price and not per event | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Surcharge to be added per price and not per event

Surcharge to be added per price and not per event

Posted: September 5, 2013 at 10:20 am

Viewing 1 reply thread


Perry Sheraw

September 5, 2013 at 10:20 am

Hi,

Is there a way to make the surcharge only applicable to specific prices? Right now it’s adding the surcharge to each price.

Our setup is that each class/event offers installment payment terms and there is a one time charge for the annual fee ($20).


Jonathan Wilson

  • Support Staff

    •

September 5, 2013 at 12:11 pm

Hi Perry,

Yes. If you add multiple ticket types, you can add different surcharges to each ticket type, or you can choose to not add a surcharge for a ticket type.
Viewing 1 reply thread

The support post ‘Surcharge to be added per price and not per event’ 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 Jonathan Wilson 11 years, 5 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server