Skip to main content

Searching products

General product searching

There are two settings influencing your general product search:

  • App:Search:DefaultMethod This setting dictates what the default search should be based on. Either perform the SearchProducts on CustomID or regular EVA ID.
  • App:Search:DefaultUserTypeOverride Employees can find and open all products. When you're trying to find products available to your shoppers however, this might not be desired. By specifying another UserType, such as Customer, all searches on the specified OU and app will be performed based on that value. Note that this only works from the perspective of employees (it's not possible for a shopper to pretend to be an employee).
Not specified / 1The app will display the search as if you are an employee.
2The app will display the search only with products, available to the shopper.

You can expand your regular product search with filters of your choice by means of the following app setting: App:Search:ProductProperties.

This determines the properties that we filter on, the setting takes PIM properties, such as color.

You can add as many as you like, combining multiple properties to obtain a more specific result. The following example would allow you to filter by color, price, and fit: color,display_price,quality_fit.


For this functionality to work, App:Search:ProductLogicalLevel should not be set.

Index properties

To index properties for search and filtering, you can configure this through IndexType in the ImportProducts service. More on ImportProducts here.

By setting the enum value of IndexType as 3, the property will be indexed both as a keyword and as text. However, assigning it as 1 will result in the property being indexed solely as a keyword.


It's important to consider that indexing properties may have an impact on the response times of services such as SearchProducts.

Logical level

The app setting App:Search:ProductLogicalLevel determines which logical level to do a product search on. When set to root, the app will only return root products as search results. When set to child, only child properties (i.e. size, colors, etc) will be returned. When App:Search:ProductLogicalLevel is not set, we filter on properties based on the configuration specified in App:Search:ProductProperties, as detailed above.

Adding filters to your PDP

You can add 1 (default) filter to your product display panel, which is the display you get when choosing a configurable product.

This filter is then added to the side pane along with the regular size/color filters. Depending on your settings, your new filter may be pre-applied or not.

Use the following settings to set it up:

  • App:ConfigurableProduct:FilterProperty: Here you specify the property you want to create a filter on. Use no more than 1 property in this setting.
  • App:ConfigurableProduct:FilterValues: Here you specify which of the property's values you want to include in the filter.
  • App:ConfigurableProduct:FilterDefault: Do you want the filter to be applied automatically? If so, specify 1 one of the values from the FilterValues setting. If this not set, no filter is pre-selected.

Here's a practical example to make it clearer:

You want to include a filter on type_fit, which has three possible values: slim, regular and wide.

  • App:ConfigurableProduct:FilterProperty: type_fit
  • App:ConfigurableProduct:FilterValues: slim,regular,wide
  • App:ConfigurableProduct:FilterDefault: slim

Now with this setup, you filter will preselect the Slim type but you can filter on the other two types by using the filter sidebar.

You can remove a configured default filter by deleting the App:ConfigurableProduct:FilterDefault setting.


This filter only works with custom product properties of type string.

You can make finding the right product in your product search easier by having the products sorted on size.

If you want to enable this in your environment, you need to have your products configured with a size product property.

EVA goes through the following steps to come to a product search sorted by size:

  1. When an ImportProducts request (or STEP/EXCEL/OCAPI import) is done
  2. And the content contains a language-independent (OR English) size property
  3. Then EVA analyzes this size property against (for now) a hard-coded terms list
  4. If matched, a new property variation_index is created on a language-independent layer for this product
  5. This resultant variation_index property is then automatically used in the background for sorting when calling GetConfigurableProductDetail (instead of the default alphabetical order)

This variation_index could also be manually uploaded as any other product property if you want to define your own sorting; EVA will then not overwrite this value.

For now the list is limited to the following:

Extra Extra Small
Extra Small
Extra Large
Extra Extra Large