If predictive search (which is not editable self-serve) has a different lookup compared to the default search which is broader, it will often return empty results creating an issue that can only be resolved with development. Some themes have default predictive search that cannot be disabled. This is a bad UX and likely bad for commerce.
Topic summary
A user reports a UX issue where predictive search functionality uses a narrower lookup algorithm compared to the standard storefront search, frequently returning empty results even when products exist.
Key Problems Identified:
- Predictive search settings are not accessible through self-service tools
- Some themes have predictive search enabled by default with no option to disable it
- The discrepancy between search methods creates a poor user experience
- Resolution requires developer intervention
Impact: This inconsistency is flagged as potentially harmful to both user experience and sales conversion. The discussion remains open with no resolution or response provided.