Product Search in the GraphQL API has moved from public beta to general availability. You can now use the productsSearch query in production workloads with the same support level as other generally available GraphQL features.

With productsSearch, you can retrieve Product data directly in the search response, selecting exactly the fields you need, fetching both the search results and their Product data in a single request. Because GraphQL lets you request only the fields relevant to your use case (for example, just name, price, and image for a product listing page, or a focused set of fields in an agentic scenario), this is generally the most efficient approach and the recommended default for most storefront use cases. It reduces round trips and keeps result ordering intact.

Retrieving IDs first and then fetching data separately via the Product Projection API can still be the better fit, for example, when you already have an established ID-based retrieval flow.

To learn how to search products and retrieve matching product data, see our documentation.

This transition to general availability also includes one behavioral change: a fix to faceted search with ranges. The GraphQL API now requires typed range values, unlike the REST API. See Retrieve facet calculation for an example.