Rule zero: the devices choose the switch
Every failed PoE purchase shares a biography: the switch was chosen first, from a catalogue, by price or brand — and the devices were discovered later. The working method inverts it. Write down the powered devices (models, counts, worst-case watts), the places they live (cabinets, distances, temperatures), and who will operate the network. The switch is the answer to those three lists; this guide is their order of operations.
It is also the order of the sections below — and, not coincidentally, the order of this site's product pages, which are organised by port count, power class, management tier, distance and environment.
Ports and power: the arithmetic section
Port count = devices + uplinks + at least two spares, at the speed the segment needs (gigabit where anything aggregates or outruns 100 Mbps; 10/100M remains honest for fixed camera edges). Power = the budget method from our companion guide: worst-case watts summed, × 1.25, compared against the switch's total budget — with the per-port class (af/at/bt) covering the single hungriest device. Do not let a vendor quote you per-port watts as if they were the budget; the datasheet prints both, and only one of them keeps cameras on in winter.
While in the datasheet, check the switching capacity and forwarding rate against your aggregate bitrate, and the uplink speed against everything below it. A switch whose uplinks bottleneck its access ports is a queue, not a network.
Management, distance, environment: the operating sections
Management tier by operating model: nobody will ever log in → unmanaged/smart, ideally with watchdog recovery for the frozen-camera fault; an operator segments, monitors or maintains under contract → managed (L2+ mainstream, L3 where routing is needed). Easy managed is the legitimate middle for port-and-PoE basics. Distance: measure the three longest runs; over 100m each needs its fix chosen now — long-distance mode, extenders or fiber — not discovered at installation. Environment: indoor cabinet, outdoor pole and factory floor are three different product lines (commercial, long-distance/smart, industrial) with three different datasheets; match the line to the site and verify the chosen model's ratings in print.
Close with the unglamorous checks that decide total cost: built-in vs external power supply, mounting (desktop/rack/DIN rail) against the actual cabinet, warranty terms (ONV datasheets state 1 year with lifelong maintenance, for example), datasheet availability before purchase, and certificate files for your market — available upon request from any serious manufacturer, and worth requesting before the order, not after the audit.
The last check: what the purchase looks like in year three
A buying guide that ends at the purchase order has done half its job. Close the process with three year-three questions. Spares: is there a shelf unit (or a budgeted same-week replacement) for the switch whose failure would hurt most? Documentation: are the datasheet, the power schedule and the configuration backup filed where the maintenance team — possibly a different company by then — will find them? Growth: does the design have an honest answer to 'twenty more cameras' — spare ports and budget, or a planned second switch position with power and rack space reserved?
None of these questions favour a brand; all of them favour buyers who treat the switch as infrastructure rather than as a line item. The manufacturers who make that easy are recognisable by what they publish before you ask: full per-model datasheets, budgets printed beside port counts, certificate files on request. That transparency — not any single specification — is the most reliable buying signal in this guide.
Red flags: how to read a vendor page
The checklist inverts into a set of red flags that identify sellers to avoid. No total PoE budget printed anywhere near the port count. 'Up to' power figures without a standard named ('supports 90W PoE' — per port? per switch? under which standard?). Environmental adjectives without a datasheet table behind them. A product range with no downloadable specifications at all — the surest sign that the numbers cannot survive being read twice. And certification claims with logos but no willingness to produce the certificate file on request: the file is the claim; the logo is decoration.
The positive signals are equally legible, and this site's manufacturer clears them in the way any serious one should: datasheets with full technical tables per model (the featured tables quoted here are copied from them), budget versions stated as versions, limits stated as limits — including, on the 10G media conversion page, an explicit statement that the product a buyer searched for is not in the catalogue, with the working alternative specified instead. Buy from whoever talks to you like that, and hold this site to the same test.
The decision, compressed
Devices first, then arithmetic, then operating model, then environment — in that order, because each stage deletes most of the catalogue and leaves the few models that were always the answer. Port count from the device list plus spares; budget from worst-case watts times 1.25; management tier from who actually operates the network; distance fixes from measured runs; product line from the site's conditions. What remains is a shortlist you can defend line by line — to a manager, to an auditor, and to yourself at the first fault. Buying well is mostly refusing to skip stages.
One last practical note on quotations: when quotes come back, compare them against the checklist rather than against each other. A cheaper switch that dropped the management tier, halved the budget or substituted a shorter environmental rating has not beaten the other quote — it has answered a different specification, badly. Lay the quotes side by side on the five checklist axes and the substitution becomes visible in a minute. If a vendor cannot fill in an axis (no published budget, no datasheet temperature), that blank is the quote's most informative field. Buy the switch that fills every row; the price difference is the cost of the rows, not a markup.
If the budget forces a compromise, the checklist also tells you where compromise is survivable. Defer ports (a second switch can be added) before deferring budget headroom (a power supply cannot). Defer management tier before deferring it forever — a managed core can supervise unmanaged edges you already own. Never defer the distance fixes or the environmental match: those are physics, and physics does not negotiate at retrofit prices. Compromise in the order the network can forgive, and write down which compromises you chose, so the year-three questions have answers ready.