Price List Hierarchy
If a customer is on more than one price list and the "Force Lowest Price" check box is NOT ticked in [ System Values | Sales | Pricing ] then the system will use the following hierarchy:
- Base Prices apply first and retrieve an applicable price.
- Secondly the Modifiers are applied, so the applicable price will be combined with things like Customer Discounts.
- Finally, after this has been chosen the system will apply the Post Selection restrictions to this price.
For instance with "Stop Structure discounts" enabled only the "Stock item" base price will apply at this point.
The higher the priority the more likely it will be applied.
Note: by default percentage discounts applied to Sales Orders are added together or the one higher up the hierarchy will take precedence. This can be changed so that they are multiplied for example a keycode for 50% and a pricelist discount of 20% will both will apply. The compound aspect means that the 50% discount applies, and the 20% discount applies to the remainder so the overall discount is (50 + ((50 /100) * 20) = 60%). The Compound Discounts option is enabled in [ System Values | Sales | Pricing ].
Base Prices
| Pricing Type | Price From | Priority |
|---|---|---|
| Base Price | Special Offer | 10,000 |
| Base Price | Keycode | 9,500 |
| Base Price | Up/Cross Sell | 9,000 |
| Base Price | Catalogue Price | 7,000 |
| Base Price | Customer / Stock Item | 6,000 |
| Base Price | Price List / SCS Child Stock Item* | 5,002# |
| Base Price | Price List / SCS Parent Stock Item* | 5,001# |
| Base Price | Price List / Stock Item | 5,000 |
| Base Price | Customer / Stock Type | 4,000 |
| Base Price | Price List / Stock Type | 3,000 |
| Base Price | Stock Item | 1,000 |
Modifiers
| Pricing Type | Price From | Priority |
|---|---|---|
| Modifier | Keycode Discount | 8,000 |
| Modifier | Bogof Discount | 7,000 |
| Modifier | Customer Discount | 5,000 |
| Modifier | Processing Charge | 1,000 |
Post Selection
| Pricing Type | Price From | Priority |
|---|---|---|
| Post Selection | Stop Structured Disc | 7,000 |
| Post Selection | Guide Prices | 5,000 |
| Post Selection | Low Limit (disabled) | 3,000 |
Within this Price List hierarchy the promotion code the user gives to the promotion will also affect which promotion takes priority. The system uses the following rules when deciding which promotion to use:
- The digit zero '0' is higher than nine '9'
- The digit nine '9' is higher than the letter 'Z' (numbers are higher than letters)
- A lower case 'a' is higher than 'z' (capitalisation is ignored)
Therefore, if a customer was on two price lists, 'bct1' and '8drt' then prices on the '8drt' price list would be used because it is higher alphanumerically.
Note: Processing Charges and Guide Prices are not enabled on all systems.
Base Price Notes:
* - Only where applicable if an item is not in a SCS relationship these priorities are irrelevant.
# - Force Lowest Price has an impact on the priority which will apply as explained here
- ForceLowest ON, parent price (Low) present on price list and child price present (High) on price list = Parent Price
- ForceLowest ON, parent price (High) present on price list and child price present (Low) on price list = Child Price
- ForceLowest OFF, parent price (Low) present on price list and child price present (High) on price list = Child Price
- ForceLowest OFF, parent price (High) present on price list and child price present (Low) on price list = Child Price
- ForceLowest ON/OFF, parent price present only = parent price
- ForceLowest ON/OFF, child price present only = child price
Examples
Example One
This example shows which price list the system will use when selecting the price of an item on a sales order. There are three prices lists:
- Price List/Stock Item attached to customer's record.
- Price List/Stock Item applied using Keycode.
Note: both these price lists are the same level in the hierarchy, see above. - Mini Price List in Keycode.
Result: the system will apply the Price List that is highest alphanumerically and Keycode Associated Price lists will be treated as another price list, not as a keycode price.
In this scenario you could start your Price List code with a number to ensure that one Price List takes priority over another Price List.
Example Two
Two Price Lists are attached to the customer's record in the following order:
- Price List/Stock Item with 10% discount.
- Price List/Stock Item with 50% discount.
Result: with Force Sales Order Lowest Price on the system will use the second Price List (50)%, with Force Sales Order Lowest Price off it will use the first Price List (10%).