What Is a Hardware Lot Manifest?

Take a mixed pallet of drives quoted at a single price per drive. That figure is meaningless on its own, because it says nothing about what is on the pallet.

If most of the pallet is small legacy capacity and a handful of high capacity nearline drives are carrying the value, the average is flattering the lot. If it is mostly current generation high capacity drives with a few small ones making up the count, the same average is understating it. From the outside the two pallets are indistinguishable, and they are worth very different amounts.

The same applies everywhere. A quote for a rack of servers means nothing until you know the processor and memory configuration in each node. A quote for a memory lot means nothing until you know how it splits by part number, because a mixed lot has to be sorted into identical types before any of it is useful.

With the manifest in front of you, you can work out your own resale or deployment value line by line and decide whether the number works. Without it you are pricing an average of things you cannot see.

The columns matter more than the format. A manifest can arrive as a spreadsheet, an export from an asset system or a table in a document, and none of that changes whether it is any good. What makes it useful is whether each line identifies the item precisely enough to price and check.

The table below sets out the columns an enterprise hardware manifest normally carries and what each one is for. It is an illustration of the structure, not a reproduction of any lot: no quantities, part numbers or values appear in it, because a made up example is a fiction and a fiction on this page would defeat the point of the page.

Not every column applies to every category. Drives need capacity, interface and form factor. Memory needs module type, speed and rank. Servers need the processor and memory configuration per node. Switches need port count and speed. The principle holds across all of them: a line should identify one thing well enough that two people reading it independently would order the same item.

They get used interchangeably and they do different jobs, which causes real confusion once a shipment is in transit.

A manifest describes what is in a lot, item by item, with specification and condition. It exists so a buyer can price the lot and check it on arrival. It is a commercial document.

A packing list describes how a shipment is packed: how many pallets, boxes or cartons, what is in each, and what everything weighs. It exists so a shipment can be moved and received. A packing list will happily say twelve boxes of drives without telling you a single capacity.

An asset register is the seller's internal record of what they own: asset tags, serial numbers, locations, cost centres and often nothing about specification at all. It exists for finance and IT administration.

All three are useful and none substitutes for another. When you are selling, an asset register is a perfectly good starting point and you do not need to convert it into a manifest first. When you are buying, ask for the manifest specifically, because a packing list is not one.

A manifest is a description, not a guarantee, and treating it as more than it is causes disappointment on both sides.

It is not a warranty. A manifest states what an item is and what condition it was recorded in, not that it will work for a given length of time. Warranty and return terms are separate and should be agreed separately.

It is not a grading standard. A grade written on a line is only as meaningful as the definition behind it, and grading across this industry is not standardised, so ask for the standard alongside the manifest.

It is not a substitute for testing on arrival. It tells you what to check against, which is exactly its value: if what arrives does not match the manifest, that is a clear and checkable failure rather than a disagreement about what was implied.

And it is not an inventory of everything the supplier holds. A manifest belongs to a lot. Asking for one before a lot has been assembled is asking for a document that does not exist yet.

Five checks, in this order, and they take about ten minutes on most lots.

First, add the quantities up and compare the total against what you were told the lot contains. Mismatches between the headline count and the line total are common and always worth resolving before anything else.

Second, find the lines carrying most of the value and price those specifically. On almost every mixed lot a small number of lines account for most of what you are paying, and the rest is making up the count.

Third, check the condition column varies. A manifest where every line reads the same grade is often a description applied wholesale rather than a record of what was found.

Fourth, look for the completeness notes: caddies, rails, brackets, sealed packaging. These change what an item is worth more than most buyers expect.

Fifth, check the specification detail is sufficient to order the same item again. If a line does not let you do that, it will not let you check a delivery against it either.

The most common reason a seller delays contacting a buyer is the belief that a proper manifest has to exist before anybody will look at the lot. It does not, and building one first usually costs a fortnight for no benefit.

Send whatever you already have. An asset register, a rack elevation, a spreadsheet somebody started, or photographs with rough quantities are all enough to work from. What speeds up a valuation is detail on the items carrying most of the value rather than completeness across everything: server model with the processor and memory configuration, drives by capacity and interface, switches by model and port count.

Group by configuration rather than listing every asset separately. Twelve of one build, twenty of another and eight oddments is far more useful than a hundred individually typed rows.

Where something is unknown, write unknown. An honest gap is easy to price around. A wrong specification found at collection is what forces a valuation to be revised, which is a worse outcome for both sides.