If a customer has a category pricing plan (CPP), at POS the system searches the category pricing plan in a specific order. When you post an item in POS, the system determines the price after searching the category records of a plan in this specific order. The order is:
vendor code (first Primary vendor, then Manufacturer vendor)
For example: You have plan called PLUFX. The description is Plumbing Fixtures and the plan consists of the following:
Category |
Type |
Method |
Percent |
Price |
5 |
D (dept) |
D (down from retail) |
10 |
|
56 |
C (class) |
X (down from list) |
15 |
|
12345 |
S ( SKU Part ) |
* (user defined price) |
|
29.95 |
At POS, a customer purchases several plumbing fixture SKU Part s. You enter SKU Part 77564 (which is department 5, class 52, fineline 50001, product code 22). The system looks at the customer record to find the category plan that applies to this customer. It then searches the plan and looks for the following in this order:
A category that matches the SKU Part number. In this example, there is no match.
A category that matches the SKU Part 's product code. In this example, there is no match.
A category that matches the SKU Part 's fineline code. In this example, there is no match.
A category that matches the SKU Part 's class code. In this example, there is no match.
A category that matches the SKU Part 's department code. In this example, there is a match.
When the system finds the match with the department code, it calculates a selling price based on the category plan of 10% off the retail price. This price is then used at POS or used in the best price evaluation, depending on the how the Best Price field is set in the Category Pricing Plan window.
What if a SKU Part is sold at POS that falls into two categories? For example, SKU Part 77575 is in Department 5 and Class 56. Both categories are part of the plan. The system still uses the same search hierarchy: SKU Part , product code, fineline code, class code, department code, vendor code (first Primary vendor, then Manufacturer vendor). As soon as it finds a match, it uses the price for that category. In this example, it doesn't find a match with SKU Part , product code, or fineline code. It does find a match with the class code and uses that price (15% down from list).