--- schema_version: "1" id: 71e74c854e65bf4b9e47a77d643c92c5eca26f1fb4c2cd5de7b8e233bbb75607 title: Product Search Configuration in Point of Sale collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_cms_modules_product_search_settings.md canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_cms_modules_product_search_settings.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 82a5fa441cd3f8de5a46c6e7904bcb5d9ee26c55205ef373b79fbb16492fe058 description: Configure the product search function in the Point of Sale CMS to define the data fields used to match query text in search requests. products: - Commerce release: "264" --- # Product Search Configuration in Point of Sale Configure the product search function in the Point of Sale CMS to define the data fields used to match query text in search requests. Merchants can define which data fields are used to match the supplied query text in search requests. Additionally, filters can be added to refine search results, and certain products can be set to be "hidden" from search results. ## Accessing Product Search Config in CMS This feature can be accessed in the CMS by going to **Products > Search Config**. ## Query Fields These are the fields (that is, column attributes in the product feed) that a user can search for. Typically, these can include color, description, ID, title, and category. The list of query fields defines which data fields will be used in the search request to match against the supplied query text. For example, if only the query fields of title and description are defined, then the search engine will only look into those two fields to match against the supplied search text. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_note.png) Note Color, Material, MPN, and any of the CustomStrings aren’t case-sensitive. ## Boost or Demote by Value To boost only online items, you can give products whose "OnlineOnly" attribute equals "true" a strong boost.![An example of setting Online Only items to receive a strong boost](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_modules_boost_by_value.png) ## Sort Field The Sort Field should come in the feed as a numerical value so that results can be sorted in ascending or descending order. For example, if you include "RevenueByProduct" as an attribute in the feed, users can apply for a "Best Sellers" sort order.![An example of setting RevenueByProduct to sort in descending order](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_modules_sort_field.png) ## Backend Filters Backend filters allow you to specify conditions that must be met in order for products to be returned in the search results. For example, if you don’t want to show products with an inventory of two or less in the search results, this can be achieved with a backend filter as follows:![An example of a configured backend filter](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_modules_backend_filters.png) ## Advanced Users For more complex backend filtering options, the **Operation** can be set to **Expression**, and a search expression entered directly into the **Field Value**. Search expressions are in the form **fieldName:fieldValue**. You can include more than one field by using parentheses and logical **AND** and **OR** operations. Field values in these expressions can be of the following types: - String - Number - Boolean (true or false) - Range, for example: - \[1 TO \*\] to search for values >= 1 - \[\* TO 100\] to search for values <= 100 - \[2 TO 5\] to search for values >=2 and <= 5 ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png) Important If an **Expression** operation is specified in the backend filters, it’s only used for filtering. Any additional filters will be ignored. This includes any additional Expression based filters. ## App Filter Fields (aka Facet Fields) App Filter Fields differ from Query Fields in that they’re more specific. The filter fields include additional data for filtering the search results in the app. For example, defining a filter field for color includes a list of all color values in the search results along with the frequency at which each color appears. In the app, the user can select one of those color values and only see results that match that color.![An example App Filter Field configuration](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_modules_app_filter_fields.png) The **Field Name** specifies the target field name in the field mappings. The **Alias** specifies what the end-user sees in the app. ## App Filter Field Range (aka Facet Range Fields) The App Filter Field Range is commonly used to control the behavior of the price filter.![An example App Filter Field Range configuration](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_modules_app_filter_field_range.png) The end-user can filter by price range in the app. ## App Sort Fields The end-user can apply the app sort fields on the product search (aka PLP) page. ## Inventory Availability By configuring Alias or Display names for Availability filters (**Store Management > Store Settings > Search**), you can limit search results by available inventory. ![Example of Inventory Availability Filters configuration](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_modules_inventory_availablility.png) ## Variant Grouping Product search collapses results by variant group, so only one representative product from each group appears in results. By default, search collapses on VariantGroupID (item\_group\_id in the product feed), which is required for every product. If you map "item\_sub\_group\_id" (SubVariantGroupID) in the product feed, product search switches the collapse field to SubVariantGroupID for your entire catalog, even if no product has a value for it yet. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png) Important If you map "item\_sub\_group\_id", populate it for every product. Product search drops any product with no SubVariantGroupID value, not just from grouping. ## Known Issues and Restrictions - Only CustomString0 - CustomString5 are tokenized if they are indexed for search. - If product search returns no products but facets still show counts, check for a mapped but unpopulated "item\_sub\_group\_id" (SubVariantGroupID) field. See Variant Grouping.