Which of the 3 options would you expect PO Suggestions to select from Supplier Price List:
And if not what, I think, is the obvious one, then what is affecting it?
None of them i expect as they need to be an approved supplier for the part for anything to work
If you have the same part number on MULTIPLE price lists from the same supplier, my guess is that a PO Suggestion (or a manually entered PO), would select the price that was entered first. There is no mention of any hierarchy in any documentation I have for Supplier Price Lists (like there is for Customer Price Lists), so its likely that it will default to the OLDEST record.
I make no claim to omniscienceā¦ but thatās how computers and databases typically work when not programmed otherwise.
Then there is no logic in Supplier Price List? We have to manage the Supplier/LT/Price we want directly?
Hey Ernie,
Those 3 are not all from the same Supplier BTW (2 & 1).
Itās not defaulted to the oldestā¦
But, what would you EXPECT it to do?
There are a few moving parts to how it makes the selection.
- Dates - it should take the latest effective date relative to the date of the PO/Suggestion. So multiples like you show there with no expiry date would be ranked in date order.
- Approved Supplier - Ben referred to this. My understanding is that if you have a part with no approved suppliers, then it can be purchase from any supplier and therefore all those 3 records rank equally. If you have at least one supplier marked as approved, then any that you wish to purchase from must also be approved.
- Default for purchasing - there is a flag on the price list record for ādefault for purchasingā that can influence the decision making.
In your scenario above if PO suggestions were generated today (11/06/2026) then Iād say it should have picked the 01/06/2026 price list, but if suggestions were ran prior to 01/06/2026 (or indeed when the date that you actually created that price list) then it would have used an earlier price list.
Hey Mark,
Thanks-ish 
In all 3 of those case I am having to directly manage the Supplier Price Listā¦It really applies NO useful logic of itās own?
What would you EXPECT it to do? Or, maybe more correctly, what would you hope that it would do?
You are correct that it picked the one from 01/06/2026, but that is actually the least favourable to the Businessā¦Itās the longest LT and highest Priceā¦
Cheers,
Kev.
Let me ask what are you expecting it to do?
Epicorās usage of Supplier Price List for use in PO Suggestions is that the part number PartPlant record have a default Supplier, and that Supplier has a price list that includes that part number. Epicor does NOT search your supplier price lists for the best lead-time/price combination. In that PartPlant record there is also an āUrgent Planningā section where you can add a second Supplier, this one will be used by MRP (or Generate Suggestions) if the lead time is LESS than the lead time of the ādefaultā Supplier (and is generally higher cost).
With the Purchase Contracts module (additional cost) you can divvy up through multiple suppliers, but that is more focused on delivery than it is on pricing.
@Kev-G , I get that you are frustrated, but all we are trying to do is help. If you donāt provide us with what you want the system to do and more information about how your parts are configured, we canāt provide you with useful suggestions. Clearly everyone would expect the lowest cost and lead time supplier to be selected.
Ernie has brought up some valid areas to look at. There is also a little know flag on parts that skips the last supplier the part was bought from. 
Apologies, not frustratedā¦Just Scottish!! We come across just slightly less aggressive than the Dutchā¦ 
I have to be honest that we have very little set-up on the Parts & thought that Generate Suggestions would do the same everyone else would consider the ābestā option.
I raised a Support Ticket and got the response āAlthough xxx001 offers a lower unit price, it is likely excluded due to approval or configuration gaps, leading MRP to choose yyy001ā
Which I thought it was a bit airy fairyā¦
Ernie, your latest response if much more usefulā¦It now just seems that we need to manage the Supply Chain much more than I would have expectedā¦
Had no idea it was considered Scottish behavior!!!
Epicor is built with as few predetermined outcomes as possible. One would think that they would program it to take the cheapest and shortest lead time, except for that company who says that the supplier does not make as good quality as a more expensive one. So they give you the tools to set it up how you need to use it and not force you in one direction.
Itās the accent. SlĆ”inte!
BTW I look at that as emphasis rather than shoutingā¦ALL FULL CAPITALS IS SHOUTINGā¦
I could be wrong!!
I didnāt take it as shouting. I agree with your emphasis/shouting.
I think @jkane hit the nail on the head here. There are too many factors for Epicor get in the business of choosing for you. Cost is only one of many factors in play here.
Iāve done some work for our customers in amending the results from PO Suggestions. For one customer they use the same internal part number across 40+ sites, but wanted a different Supplier Part Number to be used for each site (with some crossover). I was able to allow PO Suggestions to run and then further process the rows to update the Supplier / Unit Cost / Lead Time as per their desired logic. I put a couple of fields on the PartPlant record (VendorNum and VendorPartNum) and used this as part of the code.
In answer to your earlier question that you posed to me - itās doing what I expect it to do based upon the logic flow, but get that logically as a human you would choose the least cost shortest lead time option. That could quite easily be built into the post processing logic that I describe.
Since there was no primary supplier, and no approved supplier, are you sure it referenced the supplier price list at all? Did it take the information from the most recent PO that was written for that part?