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 Clarify Costs and Fees | Event Espresso - Staging Server
In addition to the paying the Business Fee license annually, is there a per registrant cost associated with using your product?
No. The reason it is different with our software is because Event Espresso runs on your site/server, whereas Eventbrite is a third-party provider who is hosting your events for you, so you need to go through their system. We have absolutely no way to take a percentage out of each registration.
Are we correct to understand that by purchasing the Business License, we have UNLIMITED registrants manageability?
The only limits to the number of registrants for a specific event are those that you put on the event yourself or are otherwise imposed by software restrictions (we currently have a hard limit of 99999 for the maximum number of attendees — but that’s more or less just an arbitrary number because we needed to have a value, and, if you were really doing more registrations than that, we could alter the code to add another nine (or several) as needed until we implement a more unlimited ceiling for unlimited registrations).
The only other note that I would add is that, since Event Espresso is software that installs on your server, you are responsible for maintaining your own site. If you are doing thousands of registrations a day, you will most likely require a dedicated server to handle the load.
Viewing 1 reply thread
The support post ‘Clarify Costs and Fees’ 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.