Hi @sermalefico,
I’ve tested with WooCommerce product today and can confirm the plugin does not apply random ordering on its own.
A few important clarifications, because several different parts are being mixed together here:
1. The plugin does not force any ordering
The filter widget does not apply orderby or order by default. If no sorting widget is used, the query order comes entirely from:
- The original Loop Grid / Posts widget query
- WordPress
- A custom function
- A 3rd party plugin
If multiple products share the exact same post date (this would be the case with a WooCommerce import), WordPress ordering will appear random. The same would happen when using the order by random parameter. This behavior is unrelated to the plugin.
2. Meta queries (stock status, etc.) are working on my side
Filtering by stock status works correctly, both via the documented bpfwe/filter_query_args/{query_id} filter, using the Filter Query ID, or via the “Default filter” section in the filter UI. If the same condition is added twice, the query may stack and this can cause unexpected behavior.
3. “Include Loop Grid Query ID” can change results
If Include Loop Grid Query ID is enabled, the plugin intentionally merges the Loop widget query with the filter query.
If the loop widget already added:
- Stock status
- Meta ordering
- Custom orderby
Then the same shouldn’t be added via a Filter Query ID, or both the targeted loop/post widget and the filter widget will inject the same arguments.
If the behavior still does not match what you expect after reviewing your settings, please enable the Query Debugging under the query section of your filter, and share the following details:
- The Filter Query ID used, and the function attached to it
- Whether the option “Include Loop Grid Query ID” is enabled
- Whether a sorting widget is active
- The debug output shown below the filter, after interacting with the filter
This information will make it possible to clearly see what query is being generated and understand where the difference comes from.
Without the final query output, it is unfortunately not possible to diagnose the issue accurately. Once those details are available, I will be happy to take a closer look.
Regards,
Dara