Displaying price ranges in the storefront

Prices are displayed in the storefront by using several approaches with WebSphere Commerce search.

For example, depending on your configuration, price ranges are not displayed in the storefront when the price mode is set to indexed (1) in WebSphere Commerce Search.

To index and display price ranges in the storefront:
  1. Set the Search profiles global defaults property for SearchProfilesPrice to mixed mode (2) in the extended wc-component.xml file. For more information, see Search properties in the component configuration file (wc-component.xml) (WebSphere Commerce EAR).
  2. Set the wc.search.priceMode property to mixed mode (2) in the STORECONF table. For more information, see Search configuration properties in the STORECONF table.
    Then, if you are changing the price mode to 0 or 2:
    1. Locate the extended wc-search.xml file. For more information, see ../tasks/tde_wcsearch_newcustomindexfield.html. see
    2. To enable the calculated price features, update the extended wc-search.xml file to include the following changes.
      
      <_config:profile name="IBM_findProductsByCategory" indexName="CatalogEntry">
      <_config:query inherits="true">
      <_config:postprocessor 
          classname="com.ibm.commerce.foundation.server.services.rest.search.postprocessor.solr.SolrRESTSearchCatalogEntryViewSKUQueryPostprocessor"/>
      <_config:postprocessor 
          classname="com.ibm.commerce.foundation.server.services.rest.search.postprocessor.solr.SolrRESTSearchCatalogEntryViewComponentsQueryPostprocessor"/>
      </_config:query>
      <_config:result inherits="true">
      <_config:field name="components"/>
      </_config:result>
      </_config:profile> 
      

      These postprocessors are disabled by default for performance considerations. The following sections describe why they are needed for calculated price modes:

      The SolrRESTSearchCatalogEntryViewSKUQueryPostprocessor is required so that SKUs are retrieved from Solr in the same request as products in search results.

      For example, when you view search results in grid mode, it enables price ranges to be displayed for all SKUs and contracts. When you view search results in list mode, it enables products with a single SKU the ability to be added to the shopping cart.

      The SolrRESTSearchCatalogEntryViewComponentsQueryPostprocessor is required so that components of a dynamic kit are retrieved from Solr in the same request as dynamic kits in search results.

      For example, when you view search results for components, the price is displayed. With the postprocessor disabled, the price is shown as pending.

    3. Deploy the changes to the search server.
    4. Restart the WebSphere Commerce Search server.