In the standard pricing model (where the price is stored directly in the SKU in the product catalog) there is a listPrice property and a salePrice property. The SKU also has a boolean onSale property that indicates that the given SKU should be priced using the sale price.
In the price list model, a price repository item has a listPrice (or a complexPrice) but no salePrice. You implement sale pricing using price lists by creating a sale price list.
In this situation, you could store all the list prices for a specific customer in one price list and all the sale prices for a specific customer in another price list. This set up provides flexibility. For example, you could have different sale prices for two different customers, even if they have the same price list normally. It also allows us to inherit sale prices while overriding the list prices (or vice versa).
Follow these steps to implement sale pricing using price lists.
Create the sale price list as described in the Guide to Setting Up a Store or the Merchandising Guide for Business Users.
Create a sale price list the same way you create other price lists. Structurally there is no difference between a sale price list and any other price list.
Assign the sale price list to a user as described in Assigning a Price List to a User.
View a price through a JSP using JSP code.
Using the
PriceDropletservlet bean retrieves the list price. Create another instance of this servlet bean to retrieve the sale price. For example:$class=atg.commerce.pricing.priceLists.PriceDroplet
$scope=global
priceListManager=/atg/commerce/pricing/priceLists/PriceListManager
profilePriceListPropertyName=salePriceList
useDefaultPriceList=falseThis servlet bean is used in the same way as the
PriceDropletservlet bean.
