We have some customers who have specific “contract” pricing for certain parts. If they order a part that they do not receive “contract” pricing for, they may receive a percentage discount based on the product group. When they order a part that has both “contract” pricing and whose product group is included in their discount price list, Epicor’s default behavior seems to be that it will use the base price set on the price list and also assign a discount percentage from the discount price list. That’s not what we want. We want it to function so that if the part exists in the price list, we use that pricing with 0 discount. Epicor does not let you specify a discount if it is 0% or $0.00. Can someone help me understand the logic Epicor uses when applying Price Lists and Discount Price Lists on an order? I’ve tried using separate lists, combined lists, etc. I can’t seem to find a way (other than manually overriding things on the order) to get the pricing to work how we want. What does everyone else do?
Agreed, the system does not allow entry of a zero percentage discount on a “quantity break” row on the “Discounts” section of a price list. However, I think it uses a zero percent if you completely omit/delete all quantity break rows from the price list. I’m pretty new at this, so this might be wrong. But let me lay describe my theory as 3 scenarios:
1 – Standard price, with 20% discount
2 – Contract price, with 20% discount (undesired)
3 – Contract price, with zero discount (desired)
Scenario 1:
Suppose part number 1234 has a base price of $100 in the part master.
A price list named “StdDisc” has been created
Type = “Discount”
Part 1234 is on this price list. Its “Discounts” section has one quantity break row:
Quantity Break =1
Discount Type = “Discount %”
Discount Pct = 20
In this customer’s Customer Group, “Discount Price Lists” includes the “StdDisc” price list.
At this point, the customer gets a $100 base price minus a 20% discount, for a net price of $80
Scenario 2:
Another price list named “Contract” has been created
Type = “Unit Price”
Part 1234 is on this price list. Its “Discounts” section has one quantity break row:
Quantity Break = 1
Discount Type = “Unit Price”
Unit Price = $75
In this customer’s “Billing” section, “Price Lists” includes the “Contract” price list.
At this point, the customer gets a $75 base price minus a 20% discount, for a net price of $60.
Scenario 3:
Another price list named “ZeroDisc” has been created
Type = “Discount”
Part 1234 is on this price list. Its “Discounts” section has no quantity break rows.
In this customer’s “Billing” section, “Discount Price Lists” includes the “ZeroDisc” price list.
At this point, the customer gets a $75 price, with no discount. This is because when the system looks in “Discount Price Lists” it will prefer the ZeroDisc one from the customer’s own “Billing” section in place of one from the customer’s Customer Group.
The above approach requires that you keep the list of contracted parts updated on two separate price lists – one list to give them the contracted price, and one list give them the zero discount. To avoid having to remember to add part numbers to two separate price lists, you might be able to use one “both” price list for both purposes, entering the same price list into both “Price Lists” and “Discount Price Lists” for this customer.
I love the way you explained this and it makes a lot of sense. I don’t think I ever tried to add a part to a price list without specifying any discount break rows. I will try and let you know how it turned out.