Won, Lost & Analytics: Sourcing Feedback Without Spying on Competitors
How won pickups, lost outcomes and performance KPIs 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 and the operational records created from them. A won bid is not a trophy; it is a handoff. The linked collection and inbound order show where Core takes over.
Lost work
/sourcing/lost gives broad outcome insight when there is enough safe data: price band, SLA fit, certification match, incomplete bid data or response timing. 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
/sourcing/analytics tracks submitted bids, wins, win-rate, response P75, active bids, lifetime won value and trends. 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, the problem is probably not the color of the bid button.