@iworks Hey! If you change the price manually then the plugin does not work properly.
If I manually update the product price (e.g., change it from 100 to 90 and then back to 100), the lowest price in the “lowest price” message does not reflect this change unless the price was set as a promotion. For example, in this case, the lowest price should show 90, but the plugin only records and displays the highest price (100).
It seems the plugin only tracks price changes made through promotions, not manual updates. This behavior doesn’t fully align with the requirements of the Omnibus directive, which should reflect the lowest price in the last 30 days, regardless of whether the change was due to a promotion.
Could you please advise if there’s a way to address this or if it’s possible to add support for tracking manual price changes?
hi
It seems the plugin only tracks price changes made through promotions, not manual updates. This behavior doesn’t fully align with the requirements of the Omnibus directive, which should reflect the lowest price in the last 30 days, regardless of whether the change was due to a promotion.
@glancus
No. You are wrong. Only “sale” prices have to be reflected in Omnibus. Regular price is beyond this directive. The purpose is to show manipulation over “promotion price”, not regular.
Source: https://eur-lex.europa.eu/eli/dir/2019/2161/oj
M
