We actually read these.
Ideas submitted here go to the product team, not into a void. Add yours, vote on others, and comment on what matters to your business.
Talk to our Product Managers live: every other Monday, 1:00–2:00 PM ET → https://www.d-tools.com/cloud-product-office-hours
We price items based on highest cost from our selected suppliers, as we never know who has the items available for procurement.
Procurement should default to our preferred supplier, which has the lowest cost.
In order to utilize auto pricing updates, you would need to set the supplier to the non-preferred supplier.
Limiting the catalog to one supplier either breaks pricing or procurement.
Hi @Guest thank you for laying this out so clearly; the pricing-vs-procurement tension you describe is real, and this was a thoughtful writeup.
After reviewing it, we're not going to pursue multi-supplier pricing on catalog items. Being direct about why: our partnerships with suppliers and distributors require us to stay neutral, features that compare supplier costs side-by-side or steer pricing/purchasing toward one supplier over another (highest cost, lowest cost, "preferred" rankings) aren't something we're able to build into the platform.
What we don't want to lose is the underlying workflow problem: keeping sell prices stable while your actual procurement source varies. If there's a version of that need that doesn't involve supplier price comparison — for example, better control over how supplier price updates affect your sell price, that's territory we can explore, and I'd welcome a separate idea framed that way.
Thanks again for taking the time to submit this — even the ideas we can't build help us understand how you work.