Corporate IT teams know the awkward gap between removing gear from a rack and getting value out of it. A switch that ran payroll traffic for years becomes, in the space of a maintenance window, a heavy box with missing ears and an unknown power supply. Routers, firewalls, UPS units, PDUs and rack hardware follow the same path. The equipment is pulled from service, moved to a storage room, and then someone asks for an offer with nothing more than a family name and a rough count. That is when good gear gets undervalued or, worse, rejected because the description and the freight do not line up.
The fix is documentation. Before a corporate IT department asks for a no-obligation offer, it should build a manifest that reflects what is actually sitting on the pallet. This is not a procurement exercise or an audit; it is a practical handoff document. The clearer the record, the easier it is for a buyer to price the load and for the IT team to defend the number internally. It also reduces the chance that a late discovery at pickup—an overlooked power supply, a box of transceivers, a UPS with no batteries—forces the offer to be reworked.
Begin With a Rack-Level Inventory, Not a Wish List
Start where the equipment lived. A rack-by-rack inventory catches items that a high-level asset list often misses: line cards, supervisors, transceivers, power supplies, rail kits, cable management, patch panels, media converters and loose telecom hardware. These are not clutter. In networking equipment, components can carry more value per unit than the chassis they came from, so leaving them out of the count weakens the offer before the first email is sent.
The inventory should also identify the equipment family and role. Switches include Cisco Catalyst and Nexus, along with Juniper, HPE, Aruba, Dell and Netgear units. Managed and unmanaged, PoE and non-PoE, access and core gear all belong on the list. Routers and firewalls should be separated from switching, with edge and perimeter firewalls, VPN concentrators and load balancers called out where they exist. For corporate IT departments, this step is usually a matter of walking the decommissioned rows with a clipboard or tablet and refusing to summarize. “One pallet of Cisco” is not a manifest. It is a guess.
Record the Details That Drive the Quote
Once the equipment is counted, the manifest needs the details that change how an item is priced. Manufacturer part numbers matter more here than in many other categories. A switch with a specific uplink module and a specific power supply is a different item from the base chassis. Model numbers, quantities and condition belong on every line, along with whether the units were pulled working, whether power supplies and rail kits are included, and whether anything is still covered by support. Units under an active support contract are worth flagging because that status affects what they are worth. Serial numbers are not needed at the quote stage, which keeps the first pass simple.
Condition should be described as the team actually sees it. New in box is easiest to price, but it is a small part of what gets bought. Pulled-from-service, open-box, customer-return, untested and partially faulty stock all have a place in a transparent manifest. The only real problem is a description that does not match what arrives. If a router has a dented faceplate, a switch is missing a power supply, or a UPS has dead batteries, write it down. The offer can then be priced for the real load, and it is more likely to hold from evaluation through pickup. When the time comes to sell used networking equipment, that honesty is not a disadvantage; it is what makes the process fast.
Give Power Gear Its Own Section
UPS systems, PDUs and power protection are often treated as an afterthought in a network decommission, yet they deserve their own section in the manifest. APC and Tripp Lite units, rack-mount and tower models, battery backup, surge protectors and PDUs should be listed separately from the switching and routing gear. Two details matter immediately: whether batteries are included and roughly how old they are. A UPS with dead batteries still has value, but it is priced differently from a unit with batteries included, so guessing helps no one.
The same discipline applies to racks and enclosures, rail kits, mounting hardware, cable management, patch panels, media converters and telecom equipment. Bulk cabling and accessories are worth including rather than leaving behind. They may not be the headline items, but they complete the picture of a decommission. A buyer who sees the whole load can make a more accurate offer than one who is asked to price a chassis and then discovers a pallet of power gear and cabling at pickup.
Make the Manifest Match the Freight
A strong manifest is organized enough to price and simple enough to send. Group equipment by category, give each line a manufacturer part number, quantity and condition, and note whether units were pulled working. Include power supplies and rail kits where they exist, flag active support coverage, and separate switches, routers, firewalls, UPS systems, PDUs and rack hardware. Add a short note on battery status for power gear and on any untested or partially faulty items. The goal is a document that a pricing team can read without calling three times for missing details.
Corporate IT departments do not need to polish the gear or test every port before asking for a number. They do need to describe the load accurately. With a complete manifest, the next step is straightforward: send the list and request a no-obligation offer. The buyer can price it against what that equipment is currently moving for and respond, usually within one to two business days, with a firm number. If the offer is accepted, payment and freight pickup can be arranged, typically inside 72 hours, from wherever the stock is sitting. That is the practical payoff of documentation: fewer surprises, a cleaner handoff, and a better chance that retired network gear leaves the loading dock with a fair value attached.


