Channel prices
This page is for administrators: the operations described require access to the administration area.
A product can have multiple prices: different price lists by country, currency or customer type. The channel specifies which prices it needs by selecting price codes.
Price groups, types and codes
A product's prices are stored in the Prices attribute, of type PriceListValue. Its configuration defines:
- price groups, each with a name, the countries where it applies and a currency;
- price types for each group, such as list price or recommended price. The types are the values in the PriceType reference data list;
- one or more price codes for each type, such as
IT-RETAIL.
On the product page, each code has its own price. For details on configuring groups, see How to configure an attribute.
Prices used by the channel
The channel selects from the configured codes:
| Price | Use |
|---|---|
| MSRP Price | The recommended price. In the product overview, if it is higher than the selling price, it appears crossed out alongside the discount percentage |
| Retail Price | The channel's selling price. The currency of its group is the channel's currency. In the product overview, it appears in the Selling Price column |
| MAP Price | The minimum advertised price |
| Other Prices | Other prices received by the channel |
The names MSRP Price and Retail Price are used in the standard configuration and may differ in your installation.
Prices and validation
If the Prices attribute has a validation rule with Required for the channel's type, openlane checks that each product has:
- a non-zero price for the Retail Price code;
- a non-zero price for the MSRP Price code, if the channel has one;
- non-zero prices for Other Prices, only if the channel has Validate Other Prices enabled.
The MAP Price is not checked. For details on validation rules, see How validation works.
The Omnibus price
With Track Omnibus Price enabled, openlane records the selling price of products in production on the channel every day and uses this history to calculate their Omnibus price. The result is saved in the product's Prices attribute, with the price type OMNIBUS and a code matching the channel key.
For details on configuring a channel's prices, see How to configure channel prices.