All Collections
Result Grouping
Result Grouping
Florian Niedermayr avatar
Written by Florian Niedermayr
Updated over a week ago

Group by field

Result grouping enables you to remove duplicated search results which may occur due to multiple child products that were imported to the Nosto database. If these child products have a parent ID field it is possible to group the child variants to the parent ID - for each of the group fields (e.g. parent_ID) the search will return only the most relevant product.

Please note that the fields that you want to choose for grouping have to be added to the indexed fields beforehand.


  • Search returns one most relevant product for each group and it’s not possible to get the rest.

  • The total count returned and facet count represent the cumulative counts of all results that are not grouped.

SKU indexing

Indexing SKUs as single product

By default all SKUs are merged into one product. This ensures the best performance and works for the most cases. You can still use SKUs fields (like SKUs custom fields or availability).

When using facets or filters on SKU fields, certain limitations become apparent. For example, suppose you intend to retrieve all products that have a red color in their SKU custom field and are marked as in stock in the availability field. In this scenario, the search results will include products containing at least one SKU in stock and at least one SKU labeled as red, irrespective of their individual stock status. This occurs due to the method where the SKU fields are copied to the parent product, resulting in the loss of all specific relations between them.

Indexing SKUs as separate products

This option indexes each SKU as a separate product. Combine it with grouping by field to return only one product per parent product id (you can use productId field for grouping when this option is set). It will bring the following advantages:

  • Filters and facets will correctly work when using multiple SKU fields.

  • The search function will retrieve the most relevant SKU, allowing you to display that particular SKU (for instance, when searching for a "red shirt," displaying the image of the red SKU). In the returned data, the first SKU listed will typically be the most relevant one.


  • This feature requires full data sync after each change.

  • Enabling this option alters the product import process, potentially leading to the loss of certain product updates during toggling.

  • When deactivating this feature, it's advisable to temporarily set the grouping field to productId. Otherwise search will display individual SKUs as separate products until the the next data sync.

Did this answer your question?