Run these checks in order

1. Confirm your aircraft broadcast Remote ID

Most consumer and commercial drones from the major brands sold since 2023 broadcast Remote ID, because the law requires it. Retrofit broadcast modules exist, but add cost, weight and a battery to manage — and some stripped-down FPV builds never transmit. If your threat model includes modified aircraft, no RID receiver will see them, and you should be planning an RF-spectrum layer instead of comparing RID units.

2. Demand the test conditions behind every range figure

“5 km range” means nothing without four facts: which aircraft was transmitting, which band (2.4 GHz BLE versus Wi-Fi NAN behave differently), what RF interference was present, and what decode success rate counted as “received”. Ask the vendor for those four items in writing. If the answer is a datasheet screenshot, treat the number as marketing.

3. Get one real output sample before the demo

A single anonymised JSON detection message tells you more than a brochure: the field names, the timestamp format, whether the pilot location is included, and how the unit handles multiple aircraft at once. Vendors who cannot produce one sample have a demo, not a product.

4. Check what still works offline

Local logging, local alerting, data export without a cloud account — these are the functions that keep working when the vendor’s platform does not. Cloud-only logging is a dependency you are agreeing to, and it outlives any subscription dispute.

5. Verify the integration interface, not the integration promise

“API available” and “webhooks supported” appear on every datasheet. Ask for the endpoint documentation and one example payload for the exact fields your control room consumes. Ten minutes with the real documentation prevents the most common post-purchase disappointment.

6. Confirm which standards the unit decodes

ASTM F3411 covers most Western-market aircraft. GB 42590 covers Chinese-market aircraft — including grey-import units common in some regions — and few Western receivers decode it. If your airspace includes such aircraft, multi-standard decoding is the specification that matters most.

7. Agree the warranty path in writing

Who pays return shipping, what the replacement turnaround is, and how long firmware updates continue. On imported hardware the answers vary from excellent to nothing — and the difference shows up exactly when you need support.

The three questions every evaluation visit should answer

If a vendor demo is part of your evaluation, resist the temptation to watch the screen. Walk the perimeter instead, and check three things. First, where is the receiver relative to the flight path — was the demo flown on the vendor’s terms or yours? Second, what happens to the log when the demo ends — can you export it, or does the evidence leave with the salesperson? Third, which alerts arrived late — ask the unit itself, by checking timestamps against the flight you watched. A vendor comfortable with these questions has been tested before. One that steers you back to the datasheet has told you something too.

Budget note: procurement files we review often compare an RID receiver’s purchase price against nothing. The fair comparison is against the cost of one incident without detection — a lost case, an unresolved complaint, a regulator asking what you knew. The right layer is the cheapest one that answers your threat; the wrong layer at any price is expensive.