A pallet arrives with a manifest that says “Latitude 5520” and nothing else. Device Spec Lookup turns a column of makes and models into hardware specifications you can list from — and, just as importantly, tells you which rows it could not resolve rather than inventing plausible-looking values for them. There is no single item mode: this tool works from a file.
Before you start
Device Spec Lookup opens inside the ITAD Tools dashboard and needs a free account; it is part of the starter toolset every new account receives. Because it only runs from an uploaded file, each run draws on the same allowance of three bulk lookups shared across all five bulk tools — once that allowance is spent the tool shows an upgrade page instead of the upload zone, and a $20/month subscription removes the cap. Build your workbook first: a Manufacturer column, a Model column, optionally a Device Type column, and wherever you have them, a column of serial numbers or service tags. That last column is what separates a guess-free exact answer from a generic one.
Looking up a device list step by step
- Prepare an Excel workbook with Manufacturer and Model columns. Device Type is optional and defaults to laptop; add a serial or service tag column wherever you have one.
- Open Device Spec Lookup and drop the workbook into the upload zone, or use Browse Files.
- Check the preview table. It lists what the tool read out of your file — if the manufacturer and model columns landed in the wrong places, fix the workbook now rather than after the run.
- Click Look Up Specifications and let the progress bar finish. A long list takes a while; the tool resolves each device in turn.
- Read the results as cards, one per device. Use Expand All Details to see every field at once rather than opening them individually.
- Click Export to Excel to take the whole result set away, then work the low-confidence rows by hand.
Reading the results
Every card carries a confidence level, and reading it is not optional — two cards that look equally complete can mean very different things.
- High confidence — resolved from a unit identifier such as a serial number or service tag. These specifications describe the individual machine, including whatever memory and storage it actually shipped with.
- Medium confidence — resolved from the model name alone. It describes a documented configuration for that model, which is a real, sourced answer but not necessarily the machine in front of you. Models ship in several configurations.
- Low confidence — not resolved. The row is flagged for manual entry rather than populated, which is the tool refusing to guess.
- Source — where the answer came from, shown on the card so a resolved row can be traced rather than taken on trust.
- Processor fields — model, clock speed, core count, and socket count on multi-socket hardware.
- Memory fields — installed capacity, memory type, and how many slots the board carries, which is what tells you whether an upgrade is even possible.
- Storage fields — capacity, whether it is solid state or spinning, drive-bay count, and RAID controller on servers.
- Chassis and display fields — form factor, screen size, resolution and panel type, graphics and video memory, battery, weight and dimensions.
- Connectivity fields — ports, networking, wireless, and out-of-band management where the platform has it.
Not every field is populated for every device. A desktop has no battery, a server has no screen, and an absent value on a resolved row means the source did not document it, not that the machine lacks it.
Making the call
The trade convention worth adopting is simple: list from an exact result, estimate from a documented one, and never list from an unresolved one. A high-confidence row can go straight into a listing because it describes that unit. A medium-confidence row is safe for planning — sorting a pallet, estimating value, deciding what to test — but writing its memory and storage figures into a listing is how a return happens, because the model name never promised those particular parts.
Where a row matters and came back medium, the fix is not a better guess but a better input. Pull the serial number or service tag off the asset label and re-run that row; a unit identifier is the only thing that resolves to the configuration actually in the chassis.
Treat an unresolved row as an instruction rather than a failure. The tool is deterministic and will not fabricate a specification to fill a gap, so an empty row means nobody has published an answer it can reach. Open the machine, read the label, or check the manufacturer's own support site — and enter what you find, rather than what seems likely.
When something looks wrong
- Most of my Dell rows came back unresolved. Known and expected. Dell model names have no automated route at all, and Dell service-tag lookups are best-effort and can be unavailable entirely. The same file will often resolve its HP and Lenovo rows cleanly in the same run.
- The specifications are not the machine I am holding. Check the confidence badge. A medium-confidence result describes a documented configuration for the model, not your unit — supply a serial number or service tag and re-run to get the exact one.
- The preview table put my data in the wrong columns. The workbook needs a header row naming Manufacturer and Model. Fix the headers and re-upload rather than proceeding, because the preview is showing you exactly what the lookup will use.
- I got an upgrade page instead of the upload zone. The bulk allowance shared across all five bulk tools is spent. It is account-wide rather than per tool, so uploads to the serial-number tools draw on the same pool.
- The file was rejected. Uploads accept .xlsx and .xls workbooks up to the size limit printed under the drop zone. Exports from other systems sometimes carry a spreadsheet extension while actually being CSV or HTML; re-save as a genuine Excel workbook.
Frequently asked questions
Does this use AI to fill in the specifications?
No. The lookup is deterministic: it resolves each device against real manufacturer data and reports honestly when it cannot. Nothing is generated, inferred, or filled in to make a row look complete, which is why some rows come back marked for manual entry instead of populated.
What do the High, Medium and Low confidence levels mean?
High means the row was resolved from a unit identifier such as a serial number or service tag, so the specs are that exact machine's. Medium means it was resolved from the model name alone, so it describes a documented configuration for that model rather than the unit in front of you. Low means it was not resolved at all and needs checking or entering by hand.
Why do so many Dell rows come back unresolved?
Dell model names have no automated route, and Dell service-tag lookups are best-effort and can be unavailable. A Dell row may therefore come back empty even when the same file resolves its HP and Lenovo rows cleanly. That is the tool declining to guess, not a failed upload.
How do I get exact specs instead of a typical config?
Add a column holding the serial number or service tag for each machine and include it in the upload. A unit identifier is the only thing that resolves to the configuration actually shipped in that chassis; a model name can only ever return a documented configuration for the model.
Do I need an account, and does an upload cost anything?
A free ITAD Tools account is required, and Device Spec Lookup is part of the starter toolset. Because the tool only works from a file, every run draws on the same allowance of three bulk lookups shared across all five bulk tools; once that is spent the tool shows an upgrade page instead, and a $20/month subscription unlocks unlimited uploads.
Try it
Start with a short list that includes at least one serial number, so you can see the difference between an exact result and a documented one before you commit a whole pallet to it.