How can I create filters using PrestaShop 9.2's Extra Properties?

From version 5.4.0, Advanced Search PRO supports PrestaShop 9.2's Extra Properties. This feature lets you create criteria groups based on additional properties assigned to products, combinations, categories, brands and suppliers.

For example, a property used to record a product's repairability score or a combination's delivery time can become a filter in your search engine.

Requirements

• PrestaShop 9.2 or later.
• Advanced Search PRO 5.4.0 or later. This feature is not available in the standard version.
• Extra Properties already defined in PrestaShop, for example by a module that provides them, and available for the shop concerned.
• The properties must be enabled for front-office use and have a supported type.

Advanced Search uses existing properties: it does not create their definitions or fill in their values for you.

Supported property types

• Integers and decimal numbers: these can also use the module's numeric range display options.
• Booleans: displayed as Yes/No criteria.
• Text.
• Dates.
• Choice lists.

Properties of type JSON or HTML are not supported. Text properties whose configured maximum length exceeds 255 characters are also excluded. Unsupported properties are not offered as available criteria groups.

Add a property to a search engine

1. Open the Advanced Search PRO configuration and select the search engine you want to modify, or create a new one.
2. In "Available criteria groups", locate the "Extra properties" family. The entity shown beside each property identifies whether it belongs to products, combinations, categories, brands or suppliers.
3. Click the property or drag it to "Active criteria groups", then configure and save the group using the options offered by the module.
4. Click "Reindex" for the search engine and wait for indexing to finish.
5. Check the filter and its results on the storefront.

The available display options depend on the property's type. For example, numeric properties can use a range, while boolean properties remain Yes/No choices.

Which values become criteria?

The criteria are built from the property values found during indexing. Identical values shared by several items are grouped into one criterion. An applicable default value defined for the property can also be indexed.

For a choice list, the module does not create a criterion for every possible choice simply because it is defined in PrestaShop. For example, if a list offers "24 hours", "48 hours" and "7 days", but only "24 hours" and "48 hours" are used, only those values are indexed, unless an applicable default supplies another value.

This differs from predefined feature values: the complete list of configured choices is not imported as a list of criteria. Storefront visibility also depends on the search context, the selected filters and the module's display settings.

How do combination properties interact with attributes?

When you combine native attribute filters with combination Extra Properties, the selected values must match the same combination.

For example, if a product's size S combination has a delivery time of 24 hours and its size M combination has a delivery time of 7 days, selecting size M and 24-hour delivery will not return that product merely because another combination has that delivery time.

A property or a value is missing: what should I check?

• Check the PrestaShop version and that you are using Advanced Search PRO 5.4.0 or later.
• Check that the property has a supported type, is enabled for front-office use and is available in the relevant shop. If another module provides it, check that module's availability for the shop.
• Check that the expected value is saved on an item associated with products included in the search, or that an applicable default exists.
• Check that the criteria group is active, then re-index the search engine.
• If the group is indexed but not visible on a particular page, check the search context and the settings for hiding empty groups or criteria.

With automatic indexing enabled, changes saved through the supported PrestaShop back-office forms update the affected groups. After imports or external updates that bypass those updates, run a manual re-indexing or schedule it after the import. For the different indexing methods, see this FAQ.