Support

Home Forums Event Espresso Premium EE4 Price Modifier – Strategy?

EE4 Price Modifier – Strategy?

Posted: June 24, 2018 at 3:52 pm


Thomas

June 24, 2018 at 3:52 pm

Hello,
I’m holding an EE4 Everything License, after many years running EE3 together with the EE3 pre-release Price Modifier Beta plugin. I was looking forward to integrating this nice little add-on after upgrading to EE4, as my Site is using it. Now I got to know that this is only available as a third-party plugin (Aparna).

I have to say that I’m really disappointed not getting this offered by EE. The EE4 Everything License description states all add-ons beging included. Sounds great, as I assumed that an add-on (even just a pre-release) available for EE3 should eventually be available for EE4 as well.

The great thing in EE3 was that this price modifier allowed you to set questions that then affect the ticket price. The Road map discussion Shows that there are lots of other Users wishing it to get integrated in the official EE4 release.

The main reason for an EE4 Everything License is to get everything from ONE vendor. Now seeing that the SAME functionality previously offered in EE3 is only available for EE4 as a third-party plugin is somehow disturbing, i.e. why should I pay now for someone external for something that was already part of EE3, leading to another dependency.

Please let me know about EE’s product strategy regarding this EE3 functionality described above.

Thanks, Thomaa


Tony

  • Support Staff

June 25, 2018 at 4:40 am

Hi Thomas,

I’m sorry your disappointed with the price modifier add-on only being available from a 3rd party at this time, I’l try to answer some of your points below.

I have to say that I’m really disappointed not getting this offered by EE. The EE4 Everything License description states all add-ons beging included.

That it does and all of our current EE4 add-ons are included with the EE4 Everything license.

All of the available add-ons included with the package are listed in that package here: https://eventespresso.com/product/everything-license-ee4/

The reason we currently still offer both EE3 and EE4 is not all of the use cases that EE3 covers are covered by EE4 and not all of the add-ons for EE3 are covered by EE4. We don’t force users to update to EE4 for that very reason, it’s your choice to switch over to EE4 and all EE3 packages include EE4 to allow you to update at any time on a dev site and see if EE4 will suit your specific needs.

Sounds great, as I assumed that an add-on (even just a pre-release) available for EE3 should eventually be available for EE4 as well.

That’s the plan, however, there’s a huge gap in development time between EE3 and EE4, EE3 has been active for a lot longer than EE4 has been and it takes time to build equivalent EE4 add-ons that match EE3.

As far as I am aware we have not stated that this add-on will not, eventually, be available from ourselves?

The great thing in EE3 was that this price modifier allowed you to set questions that then affect the ticket price. The Road map discussion Shows that there are lots of other Users wishing it to get integrated in the official EE4 release.

The roadmap does indeed show interest in a price modifier add-on with 51 votes:
https://trello.com/c/uJhRDmvT/104-price-modifier-add-on

However we have to prioritize our development time for features with the most requests, so with a quick snapshot of the roadmap as it stands today – http://take.ms/TYmVA

The price modifier add-on is the 7th most requested feature, 9th if you include the planned features which are originally from feature requests in the same board (Recurring events::102 votes and Automated messages::76 votes).

Simply put, it takes time to work through the requested features and there’s a lot going on in the background to allow for various features to be added, that and the fact that we need additional work to support WordPress 5.0/Gutenberg slows things down some.

The main reason for an EE4 Everything License is to get everything from ONE vendor. Now seeing that the SAME functionality previously offered in EE3 is only available for EE4 as a third-party plugin is somehow disturbing, i.e. why should I pay now for someone external for something that was already part of EE3, leading to another dependency.

As it stands right now, if you need a Price modifier add-on for EE4 then yes you would need to purchase an add-on from a 3rd party as we do not currently have one but as mentioned, we don’t force users to update to EE4.

You could continue to use EE3 with its price modifier as is until EE4 includes the feature you need, we include all of the add-on’s listed in all packages to allow you make an informed choice of when to move to EE4.

Please let me know about EE’s product strategy regarding this EE3 functionality described above.

Eventually, we plan to support all of EE3’s functionality in EE4 in one form or another.


Thomas

June 26, 2018 at 3:43 am

Hi Tony,
Thanks for your prompt and comprehensive feedback, it’s appreciated.
I understand from your reply that it will take quite a while until the price modifier in its original pre-release form (allowing you to set questions that then affect the ticket price) will be available in EE4.

However, quoting your last sentence:

Eventually, we plan to support all of EE3’s functionality in EE4 in one form or another.

does not really guarantee or explain which features exactly the future official EE4 Price Modifier Add-On will eventually cover.

I understand that this has not yet been decided on your end.
Anyway, let me stress again my interest in getting the same (and maybe more) features in EE4 as we had in EE3 so far for the sake of backward compatibility.

Is there any rough and vague time range until when this add-on can be expected in EE4? Perhaps by the end of 2019?

Finally, I just voted for the price modifier on Trello, to give more weight to my request 😉

Regards, Thomas


Tony

  • Support Staff

June 26, 2018 at 4:28 am

does not really guarantee or explain which features exactly the future official EE4 Price Modifier Add-On will eventually cover.

I understand that this has not yet been decided on your end.

As the add-on hasn’t moved into the planning phase I can’t tell you what features it will support as we don’t know as of yet.

EE4 works differently to EE3 so I can’t say it will work exactly the same as EE3 but can say that it will at least allow you to assign a value to a question and if that question is selected during the registration, the value will be added to the transaction.

Is there any rough and vague time range until when this add-on can be expected in EE4? Perhaps by the end of 2019?

Not currently, anything I give you would be a complete guess and likely incorrect. We need to finish up WP5/Gutenburg work, then recurring events before we will have even a rough idea on the next add-on (be that the price modifier or another).

Finally, I just voted for the price modifier on Trello, to give more weight to my request

Great, the cards do help.

As you mentioned above that my comments don’t clarify the features that will be included you could add a comment to the card with details on the features you would like to see included in the add-on. The requests in the comments don’t mean they will be included but we do review them when planning the add-on’s so if there’s something you feel would be good to include by all means add it to the board.


Thomas

June 26, 2018 at 3:02 pm

Thank you, Tony, for pointing that out, I left my 2 cents at the Trello board.

The support post ‘EE4 Price Modifier – Strategy?’ 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.

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: closed

Updated by  Thomas 1 year, 4 months ago ago

Topic Tags

Notifications

This topic is:
pending
Do NOT follow this link or you will be banned from the site!
[for="input_96_5_3"]
[for="input_96_5_3"]
[gravityform id=96 title=false description=false]
  • This field is for validation purposes and should be left unchanged.
[i]
[i]
[gravityform id=69 title=false description=false]
  • This field is for validation purposes and should be left unchanged.