How can we improve WHMCS?

@WHMCS

It's much much better to have any adjustments made at the afterwards before the payment page than to have bounce drop off from sales closing because the promo discount does not apply upon viewing the cart and prices. We have this problem and it is quite concerning. It's really shocking it's not been addresses and fixed already as we see so much bounce rate using promo code url's, more than not using them and it does point out to the promo code not being effective on step 2 where you need to setup configurations then only to find out that the discounts do not apply until you hit CONTINUE.

At the very very least a embedded popup or clear ATTENTION message should show saying discounts are not calculated until you proceed to hit the CONTINUE button. Or something like that. I had put this at the top of my header and a popup chat with this on load of the cart.php:

!! IMPORTANT NOTE: You must hit the 'CONTINUE' button to see the effective discounts applied. !!

Still a preliminary discount calculation is far more preferrable than not having that upon promo cart url loading. If they drop off due to some other calculated condition in the next page, that is another issue entirely unrelated to the discount on this primary step 2 cart page and should not be a concern for this request.

Please please please, do implement the discoutn code calculation on Step 2 of the cart. We have needed this for a long time and I'm sure we will get better results from reduced bounces.

Even though there was an update to the whmcs v8 (CORE-17740 - Update Google Sign-In integration libraries) in March 2023, the 2014 Google reCAPTCHA v2 is still needed! https://backyardbaseball.io/

In March 2023, despite a subsequent whmcs v8 (CORE-17740 - Update Google Sign-In integration libraries) update, the 2014 Google reCAPTCHA v2 is still required to be used!
After four years, Google reCAPTCHA v3 has still not been implemented.
https://geometrydashworld.net

It would be fantastic that **if the promotion code can be evaluated** that it shows.

For example - a promo code that requires a bundle or something else in the cart - well - don't show it on the first step [or until it can be evaluated].

If a promo code isn't particularly special and could apply on the first step [i.e. no bundle is required] - then show it.

We've had to put a "Discounts applied on next step" warning on the first step of the cart because otherwise we get people asking why we told them one price and then want to bill them another - or they just click order and then navigate out of the funnel due to the price shown being higher than promised.

First step: https://www.screen-shot.net/2023-05-15_22-44-12.png [the promo code, in this case, **could** be evaluated on this step].
Second step: https://www.screen-shot.net/2023-05-15_22-45-04.png

If the templating for this were a bit better it would be easier to modify but most of this looks to be getting handled by heavily minified javascript. Javascript that it appears you don't intend for anyone to override or modify.