Rich Per-PC Intake: Why “340 Laptops” Is Not A Manifest
How the trade-in intake captures device-level detail at request time — manufacturer, model, condition, serials, data-on-board — and what that does for bid accuracy and operational predictability.
“340 mixed laptops” isn’t a manifest. It’s a guess. ITADs bidding on a guess price for the worst plausible mix; customers who priced for the best plausible mix are surprised on settlement. Rich per-PC intake at the trade-in form replaces the guess with structured per-device rows.
What the form captures per device
For each device the customer wants picked up: manufacturer, model, age band, condition grade (a non-expert customer-facing scale, not the ITAD A–R), serial number (optional but valuable), whether the drive is still installed, whether the drive carries data, on-site vs. facility wipe preference, any special handling notes. The form auto-suggests as the user types — manufacturer “Dell” opens the model picker filtered to Dell products.
Bulk entry options
Typing 340 rows by hand isn’t happening. The form supports CSV upload (with a downloadable template that documents the column headers), copy-paste from a spreadsheet, and a “same as the row above” button that lets the user fill bulk identical rows fast. For mixed lots with patterns (50 Latitude 5430s + 50 ThinkPads), the CSV upload is the realistic path.
Why per-device, not bulk-counts
Three reasons. Bid accuracy: an ITAD bidding on per-device data gives a tighter price than one bidding on “a couple hundred mixed.” Coverage matching: a request involving servers needs different ITADs than one involving phones; the platform routes correctly only when it knows what’s in the lot. Operational predictability: the awarded ITAD plans receiving, testing, and erasure capacity from the device list. Showing up with 340 unknowns is how a 5-day SLA becomes 12 days.
Camera capture for warehouse-floor requests
Half of these requests get filed from a phone next to the kit. The intake form supports camera upload for location photos (the room the devices are in), and the per-device row’s “add photo” captures the device through the same flow that the operator scanner uses. So a customer documenting their pile by phone doesn’t have to switch tools.
What the operator sees
The awarded ITAD’s receiving session pre-populates from the request’s device list: each device gets a placeholder row with the customer-supplied data, ready for the operator to scan in actuals on arrival. The pre-population isn’t treated as truth — the operator’s scan is what creates the asset row — but having the placeholders means receiving is a comparison, not a re-creation.