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 switch from eventespresso to prestashop | Event Espresso - Staging Server
I am seriously about to quit eventespresso because of its lack of flexibility for consumers regarding the UX experience.
For organizers, it’s ok. For consumers, who could expect to have a simple shopping cart and easy to buy process (woocommerce integration), I personally don’t think eventespresso is the right solution except for you spending more with developers to implement such a thing.
My question is simple: what are the best advantages of eventespresso compared to a simple prestashop ecommerce site with an event plugin management offering possibility to print e-ticket and to check in participants on android and iphone?
Budget: Eur 270.
Paypal adaptive solution: Price: Eur 150
Total budget with developers: Eur 600.
FYI: you are selling tickets so this makes sense (since you’re starting the business and expect net ROI on 6 to 8 months.
The challenge: developing a business around the chosen technology and hiring people to develop the business.
The risk: well, if the technology does not satisfy customers/Final consumers/attendees, then, you are stuck to it because you’re almost married to the technology.
I think it is worthy to take it seriously.
As I stated in my email reply to you a few minutes ago, we appreciate your constructive feedback. I will pass this along to Garth and Seth, our co-founders, for their consideration. I’m positive they will want to discuss the matter further.
Thanks again.
Viewing 1 reply thread
The support post ‘switch from eventespresso to prestashop’ 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.