Won, Lost & Analytics: Sourcing Feedback Without Spying on Competitors
How won pickups, lost outcomes and a dashboard preset help bidders improve without leaking another ITAD’s playbook.
Sourcing only improves when the bidder can learn from outcomes. But a marketplace should not hand over a competitor’s exact price, margin logic or private notes just because a bid lost. ReVend OS keeps the feedback useful and boringly safe, which is the right kind of boring.
Won work
/sourcing/won shows accepted bids with request number, bid number, pickup city and country, proposed pickup date, net payout and a link to the Core collection the award created. A won bid is not a trophy; it is a handoff. If the collection link is missing, the page says so explicitly - that is a follow-up signal, not an invitation to create a second collection by hand. /sourcing/calendar shows the same won pickups grouped by proposed pickup date for forward planning.
Lost work
/sourcing/lost lists bids that ended lost or rejected, with the net amount you offered, anonymised feedback categories and any optional feedback text the customer left. Where enough comparable bids exist, the page adds broad outcome insight: price band, region, certification match, SLA fit, response timing, incomplete bid data, requirements you did not cover, or simply too little data to say. It avoids exact competitor details. “You were too slow” is useful; “Competitor X bid EUR 4,200 with this note” is how platforms lose trust.
Analytics
There is no separate analytics page. The sourcing KPIs live on the dashboard as the Sourcing Manager preset: submitted bids, won bids, bid win rate, active bids awaiting decision, response P75 in hours, lifetime won value and a bid volume chart, next to the inbound and testing queues the won work will land in. The widgets are individually addable to any layout, so a commercial lead who also runs the warehouse can keep both on one screen. The point is to help the tenant choose better work and write better bids, not to gamify the team into bidding on pickups they cannot service.
How to use it
Review lost reasons weekly, compare them with coverage and defaults, then adjust the operating habit. If the same request type keeps losing on response time, the fix is the inbox routine, not the coverage settings. If it keeps losing on certifications, widening coverage without holding the certificate only produces prettier losses. The problem is almost never the color of the bid button.