If your Oracle ATG Web Commerce catalog uses price lists, a single item may have multiple prices. A customer is assigned a price list, and when that customer accesses a product or SKU, Commerce looks up the item’s price in that price list. Another customer looking at that same item might see a different price, if that customer is assigned a different price list.

The Indexing Price Data in Price Lists section of the ATG Search Administration Guide describes how to create a special price property to represent the price data stored in price lists, using the /atg/commerce/search/PriceListPropertyProvider component. When you index your catalog, the item prices are read from the price lists and used to construct meta tags in the XHTML documents. A separate meta tag is created for each price list, and the property name in the tag identifies the price list the tag is associated with.

When the index is queried, the search client must determine which price list is assigned to the customer issuing the query, and map the price property to the meta tag associated with that price list. To do this, the search client determines which user profile properties identify the assigned price lists, and checks the value of those properties to determine the price lists to use. It then creates a property mapping between the price property in the indexing definition file and the price properties in the index associated with those price lists.