Rich Per-PC Intake: Why “340 Laptops” Is Not A Manifest
How the trade-in intake captures device-level detail at request time — category, manufacturer, model, specs, serials, data classification — 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 item lines, and the bid form on the other side is built to price exactly those lines.
What the form captures per line
Each item line carries a category (laptop, desktop, server, monitor, phone, networking, printer or other), manufacturer, model, CPU, RAM, storage, display size and a quantity. It also carries a data classification - public, internal, confidential or regulated - which is what turns a line into a data-bearing line downstream. Serial numbers and the customer’s own asset tags can be added per line, plus free-text notes. There is no condition grade on the customer side: grading is the ITAD’s job, and every bid assumes A-grade until receiving says otherwise.
Bulk entry
Typing 340 rows by hand isn’t happening. The items step has a paste-from-spreadsheet dialog with fixed column headers - manufacturer, model, category, cpu, ram_gb, storage_gb, display_size, qty, serial, asset_tag, data_classification - that parses the pasted rows into item lines. Identical devices stay on one line with a quantity; a lot of 50 Latitudes and 50 ThinkPads is two lines, not a hundred.
Why per line, not a bulk count
Three reasons. Bid accuracy: the bid form requires every requested line to be fully covered, and lets the ITAD split a line into variants at different unit prices as long as the quantities add up - a tighter price than “a couple hundred mixed” can ever get. Coverage matching: a request with regulated-data servers needs different partners than one with public-data monitors; the platform routes correctly only when it knows what is in the lot. Operational predictability: the awarded ITAD plans receiving, testing and erasure capacity from the manifest. Showing up with 340 unknowns is how a five-day SLA becomes twelve days.
Site photos
Half of these requests get filed from a phone next to the kit. The wizard accepts location photos - the room, the pallets, the loading dock - so the bidder can see what a “third floor, no lift” pickup actually looks like before proposing a vehicle.
What the bidder sees
On the Sourcing request detail the manifest lines appear with category, manufacturer, model or spec summary, quantity and the data-bearing flag, next to the approximate device count and the pickup city. The company name, exact address and contact stay hidden until award. The ITAD prices the manifest, not the relationship. After award, receiving still grades the real devices; the manifest is the promise, the scan is the truth.