Understanding Price Lists
Price lists are used to set the value of products
Price lists are available for all products within the scope, however not all products have a value within a given price list. This means that not all products are systematically affected by every price list.
For example, you create a Summer Clearance price list that is valid from September 21st to October 15th in the hopes of heavily discounting seasonal items like camping equipment and air conditioners. Later on, you access the Orchestration Console to edit the price of winter boots. When you select a price list to edit, you will see the Summer Clearance price list among possible choices, however, it will not contain a price for winter boots. In other words, the Summer Clearance price list will have no effect on the price of winter boots.
Price lists can have start and end dates and priority levels. Both of these settings determine which price list has precedence over the others and, therefore, which price the customer needs to be charged right now.
Your Orchestration Console comes equipped with two price lists:
| • | Default price list - enables you to set a base price for all your products |
| • | Discount price list - enables you to set a sale price for all your products |
The Current Price is a price that is applied based on price list dates and sequence number, regardless of its type.
A price list is valid for an entire scope. Price list values can be set for a specific product
| • | All price values must be positive. The price list set as the default in a sales or dependent catalog cannot be null. |
| • | You can have one or more price lists of type Regular. For example, price changes by provider/supplier or past season products. |
| • | You can have one or more price lists of type Discount. For example, Clearance or On Sale items. |
REFERENCES