Sourcing Requirements: Read Them Before You Price Them

A bidder pricing a pickup needs to know what the job has to prove. If the compliance picks live three clicks from the form, half the quotes come back priced for the wrong scope — and the ITAD that read carefully looks expensive next to the one that did not. So the requirements sit on the request itself, above the button that opens the bid.

What the request detail shows

/sourcing/inbox/[id] opens with the operational shape of the job: request number, approximate device count, pickup city and country, the bidding deadline or the time remaining, the current number of bids, and the manifest lines with category, manufacturer, model or spec summary, quantity and data-bearing flags. Then the requested pickup window, the vehicle preference and the priority.

After that, the requirements — in plain words rather than internal codes: the required certifications, the required services, whether data destruction is required and by which method, whether an ESG report is expected, and the disposition preference. Brand, transport and access constraints appear when the customer added them. One screen, everything the price depends on.

Where the bid form lives

Quote this opens /sourcing/inbox/[id]/bid, a separate page underneath the request rather than a box on it, because a structured bid is a form and not a “make us an offer” text field. If your tenant already has an active submitted bid, the request detail offers Edit bid while the window is open; once bidding closes the action is disabled rather than removed, since “you were too late” is more useful than a button that quietly vanished. /sourcing/bids is a different thing again: the history of what your tenant has quoted.

You only see what you can do

Coverage filtering decides whether a request reaches you at all. If its required certifications are not all present on your tenant’s coverage, it never appears in your inbox — so every requirement you can read is one you have already told the platform you cover. The requirements block is a checklist for pricing, not an eligibility test you might fail while reading it.

What stays hidden until award

The customer’s company name, the exact pickup address, the postal code, the floor and access details and the contact information are not on the page before award. They become operationally useful the moment a bid is won, and before that they mostly invite side channels. Nobody needs a marketplace where the sharpest pricing strategy is finding the phone number.