• Resolved bba01

    (@bba01)


    Hi and thank you for an amazing plugin!

    When adding product fields that adds to the original price of the product it doesn’t show in the recently viewed items widget in Elementor.

    Example:

    Original price is 4000. There are addons A (+1000), B (+2000), and C (+3000) as radio buttons so A is always chosen by default and it’s not possible to buy the product without at least A.

    I expect the recently viewed widget to show the product’s price as 4000 + 1000 = 5000. But it doesn’t. It shows the price as 4000 so the customer gets disappointed when visiting the page again and sees that no the price wasn’t 4000, it’s 5000.

    It’s not only the recently viewed widget that has this problem but also the “You might also be interested in…” widget.

    Is there a way of fixing this issue?

    With best regards,

    bb

    • This topic was modified 2 weeks ago by bba01.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Maarten B

    (@maartenbelmans)

    Hi @bba01

    What you are seeing is expected behavior, unfortunately. Elementor’s recently viewed / related product widgets use the normal WooCommerce product price, so they only know about the base product price — in your example, 4000.

    APF field prices are calculated when the product form is loaded and the customer makes or submits their selections. Those Elementor widgets do not load the APF form logic, so they do not know that option A is selected by default and adds +1000.

    There is currently no built-in APF setting that changes prices shown in third-party product widgets, because those widgets do not calculate APF option prices.

    Sorry I don’t have a better answer for you here.

    Thread Starter bba01

    (@bba01)

    Hi again @maartenbelmans!

    Thank you for your answer. Maybe I’ll just raise the price on the default product and remove the +1000 on the A option.

    Have a nice week!

    With best regards,

    /b

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.