When filtering products with a price filter, the min and max values change.

[ujike-ryota]

Hello,

When applying a price filter to a collection, the minimum and maximum prices that can be used for filtering within that collection change. For example, let’s say the input values for the price in the filters object, when no filter is applied, are returned as follows:

"{"price":{"min":0,"max":10000.0}}"

This indicates that the collection can be filtered within the range of 0 to 10,000. Next, if you filter the products in this collection to a range of 1,000 to 5,000, the filters object would then look like this:

"{"price":{"min":1000.0,"max":5000.0}}"

At first glance, this seems correct, but there is one problem. When providing a UI that allows users to set the minimum and maximum prices, such as with a slider, if the returned min and max values change, the min and max of the slider will also change. Even if the collection is filtered to 1,000 to 5,000, I would like to set the min and max of the slider to the original values of 0 and 10,000, which were available before filtering.

Due to the fact that the page is reloaded each time the query parameters change, it’s not possible to retain the original values of 0 and 10,000.

Is there a way to retrieve the original min and max values for price even after the collection has been filtered? Alternatively, if there are any best practices for this, could you please share them with me?

[juanpprieto]

One option would be to define your collection filters and settings globally with metafields or metaobjects.

[HH-SW]

So with every price change, every added or deleted product, sold out product, ... a flow has to update this value in the collection?
At the latest with sold out, it is clear that this is dependent on other active filters and cannot be solved in this way.
The corresponding GraphQL API must be extended by min & max price as described.

[ujike-ryota]

The proposed method might be one workaround.

However, if we do this for each collection, it will result in enormous operational costs.
There is also the possibility that unintended prices could be set due to human error.

Another way to avoid this is to request an additional simple collection query without applying filters.
This would allow us to obtain unfiltered information, but it cannot be considered a very good implementation.
Currently, I am proceeding with implementation using this method, but I hope this topic will be discussed🙏