Vinson

Depends if there's some specific feature you really require/want. For all the noise and fuss there's little improvement to the base theme or architecture, just a shit ton of loacl workflow changes to make your devs life difficult. We did Denali > Aconcagua and was not worth the effort for next to no improvement to the end customer. If you want to do a rebuild of frontend design/UX may as well go to latest version. What woul dbe a 'theme update/reskin" on another platform is basically a total rebuild on SCA anyway...

Hi Steve, I will have to disagree with you on this. There are major changes between Denaili and SCA 19.2, as well than from Vinson to SCA 19.2 If we talk about new features between SCA 19.2 and Denali, you have (in bold the ones for Vinson): - Google Tag Manager Editor - Merchandise Hierarchy - 3D Secure - Device Fingerprinting - Intercompany Cross-Subsidiary Fulfillment - Save Credit Card Information - SuiteTax for US and CA - Tokenization / Payment Instruments - Facets as URL Parameters - Service Controllers - Partial SuiteScript 2.0 support - Typescript support - Secure shopping Domain - Single Secure Domain - Cancel Order - Log in to see website - My Account columns management - Personalized Catalog Views - Pick up in Store - Quantity Pricing - Quick Order - Quotes - Store Locator - SuitePromotions - Commerce Categories - CCTs - Page Types and Layout Selection - Theme Customizer - Theme Skins On what regards to development you have - Extensibility API - Extension Developer Tools - Extension Manager - SDF Developer Tools support - Theme Developer Tools The big difference is the Extensibility API. If you create your “customizations” through the extensibility API without touching SCA core, then moving to the next major version or even next minor version will be much more easier than in the the past.

I will give you Single/Secure Domain (I forgot that we had separate checkout domains and http storefront - insane that either were ever a thing at all). Outside of that I don't think anything in that list warrants a $30k+ project, unless as I said there's something OP particularly wants/needs in there - the base theme is still same, Commerce Categories are a joke, CCTs the same. And in terms of local development workflow being a positive - I can tell you the releases of dev/theme tools and extension manager in the last 18months cost us over 50 wasted hours on our project, and were generally loathed by every dev who had to deal with them....

That´s ok, we don´t have to agree.

@Mandy Grzymala We had a pre-denali website, are currently on Elbrus and now working on upgrading to 19.2. For us the ability to have custom skins for different customer groups is critical and having more control for end users in marketing to edit the site without our help is invaluable. I would advise you go through this feature matrix https://developers.suitecommerce.com/suitecommerce-advanced-feature-compatibility-matrix If you have any questions on specific features listed in the matrix let us know as we are currently going through every single one to get a better idea of what it does

@Steve82 @Flo @Rehan Ali Thanks for your responses! Yeah, I do see some benefit to upgrading with the extensibility layer. Over the last few years we have added so many customizations that we have a good number of things that are now a new feature in 19.2, but with each passing upgrade, we're finding ourselves doing more and more fixes to old suitescripts... At this point we're not looking to make front end changes, so at the end of the day we're going to end up with a similar front end site that hopefully doesn't break as often...