Developer forum

Sortby price is using the default price field on the ecomproduct table. So whatever value is in that fields, is what is used. If prices are later calculated, personal, chaned from price matrix etc, sorting will be off.

The index also has other price fields in a combination of country and currency to control i.e. vat.

So you can change to use one of those price fields:

Also see this post: https://doc.dynamicweb.com/forum/ecommerce-standard-features/ecommerce-standard-features/guidance-on-a-price-filter-with-prices-in-the-pricematrix

Hi guys,

I have investigated further and it seems that the inconsistency may be caused by the DefaultVariantComboID approach.
For products with a single variant, the price of the master product is changed in the back-end and in the front-end to the value of the variant (the first one in this case).

For products with more than one Variant, even if I select a Default Variant, the price of the MasterProducts is not updated.

Can somebody confirm my findings and maybe suggest a solution?

Thank you,
Adrian

Hi Nicolai,

Thank you for the response.

I have figured it out that the sorting will always be based on the Default price.

What I was wondering is how the system will/should behave when you set a Default variant on a product and set it to be displayed in the list instead of the master product.

The Product list will clearly display the variant but the sorting will still be based on the Master product price instead of the Default Variant price.

Maybe the value of the Price in the index should take into consideration this configuration. Or create another price field that would expose "Master or default variant price".

In my case, we've created a scheduled task that updates the value of the price on the master product but it does not feel right.

Thank you,
Adrian

Hi Nicolai,

I understand. That sounds like a good option.

I will try to set the query to list a mix of Master products (those without variants) and products with default Variant.

Thank you,

Adrian