Sourcing Bids, Defaults & Bid History: Quote Once, Reuse the Boring Bits
How structured bids, tenant defaults, validity windows and bid history keep pickup quoting fast without making it sloppy.
A sourcing bid is not just a number. It is a promise about pickup timing, services, payment terms, validity and any notes the customer needs before choosing. ReVend OS treats that promise as structured data, because "see attached" has caused enough archaeology for one industry.
The bid form
From a request detail, the ITAD submits a bid with amount, service coverage, SLA, validity window and customer-facing notes. The page keeps compliance and security requirements visible while the bid is being written, so nobody quotes a normal pickup for a request that quietly asked for certified destruction.
Defaults
/settings/sourcing/defaults stores tenant-wide defaults for common bid terms: validity, pickup lead time, payment terms and standard note. New bids prefill from those defaults, then snapshot the actual submitted values. Changing the default later does not rewrite history. Contracts appreciate that.
Bid history
/sourcing/bids keeps submitted bids visible with status, request context and outcome. It is the place to answer "what did we quote?" before someone invents a memory with suspicious confidence.
Why structure wins
Structured bids make comparison fair for the customer and review useful for the ITAD. They also feed analytics: win-rate, response time, active bids and won value. A clean quote today becomes better bidding tomorrow.