Direct answer: Choose a fixed UHF RFID read point when a defined crossing or station must be observed without waiting for an operator to walk a route. Choose a handheld when the task is a bounded search, count or exception investigation that can be performed deliberately. Neither choice turns a tag read into an accepted receipt, shipment or complete inventory by itself. Buy the reader, antennas, tags, software and acceptance method as one configured system.
This is a selection question about where and when evidence is collected, not a claim that one form factor has a universally better read rate. The RFID mobile-computer category and RFID sled category are relevant handheld directions. They do not establish that AIDC GO supplies a fixed portal, its antennas or the event software.
Start with the business observation
Ask whether the business needs “these expected assets were present during the 16:00 operator sweep” or “this identified load crossed door 2 during the dispatch window.” The first is an inventory observation with a chosen route and an expected population. The second is a movement observation at a defined point. In both cases retain the raw tag identifier, observation source, time, task context and application decision separately.
A fixed reader can be installed at a door, station or other planned point. An antenna layout, mounting, power, network link and event application then become part of the purchase. A handheld moves the antenna with the operator; the route, trigger behavior, viewing of exceptions, battery and staff time become part of the purchase. Impinj’s fixed-versus-handheld discussion distinguishes unattended fixed observations from manual handheld counts. Its retail examples and performance claims are not AIDC GO results or a guarantee for another site.
The Impinj R700 Series is a specific fixed-reader example with antenna and network configurations. Its published portfolio and supported-region conditions illustrate why a fixed proposal must name the exact reader model, antennas, power source, firmware and region. They do not prove interchangeability with an AIDC GO handheld or suitability for a particular door.
Compare a crossing with a mobile count
Editorial example, not a customer deployment or measured test: A service depot has a cage containing 12 tagged instruments and a dispatch door. At shift end, the supervisor needs to reconcile the 12-item expected set; during dispatch, the system must record whether a particular authorized load crossed the door. A handheld sweep can compare observed unique tag identities against the cage list and send an exception to the supervisor. A fixed door point can collect timestamped observations during a crossing, but the application still needs the dispatch task, permitted direction, time window and load association before declaring that a shipment left.
| Decision | Handheld route | Fixed point |
|---|---|---|
| Observation | Handheld: an operator intentionally surveys the expected cage population. | Fixed: installed antennas observe tags in a defined crossing window. |
| Missing evidence | Handheld: an unseen tag requires route, mounting and asset-record investigation; it is not automatically lost. | Fixed: a read does not establish load, direction or approved dispatch without event rules. |
| Exception response | Handheld: the operator can move to a shelf or inspect a particular item. | Fixed: the system can flag a questionable crossing for a defined manual follow-up. |
The two paths can complement each other. A fixed observation can trigger an exception and a handheld can locate or recount the disputed instrument. Avoid counting one EPC twice merely because both sources observed it. The inventory-scope guide defines which tags qualify for a count; this article decides the collection topology. The multiple-reader guide treats RF coexistence and event duplication after more than one point has been proposed.
Ask for a configuration, not a reader label
For a fixed proposal, request a marked site drawing, intended crossing or station boundary, antenna count and placement, tag samples and mounting, reader and antenna models, permitted region, power and network arrangement, software interface, event rule and exception owner. For a handheld proposal, request the exact reader and host configuration, tag samples, route, trigger and reporting settings, charging plan, expected list and operator workflow. A region label, antenna-port count or maximum vendor read rate cannot replace a site acceptance run.
Test the same representative tags, difficult orientations, nearby inventory and normal movement speed. For the fixed point, compare source-labelled raw reads with the approved crossing events and deliberately pass a non-task load nearby. For the handheld, compare the expected set with unique raw reads and the accepted count after the complete route; repeat a missed-item investigation. Record false inclusions, misses and operator interventions without inventing a universal success threshold. Establish the project’s threshold before the trial.
Reader output, application acceptance and the resulting business transaction are separate checkpoints. If raw reads are missing, inspect the physical read zone and exact configuration; the read-range guide addresses missed and stray tags. If raw reads are complete but the wrong transaction is created, inspect mapping and event logic rather than changing transmit power blindly. If a fixed point and handheld both see the same tag, preserve source and task context before deduplicating.
Approve the complete operating model
Choose a handheld when a deliberate survey or mobile investigation answers the actual business question and staff can perform it repeatably. Choose a fixed point when the required event occurs at a stable physical boundary and the site can support installed coverage, network and maintained event rules. If both are required, state which observation each owns and who resolves a conflict. Do not promise continuous location from one door observation or a dispatch event from one handheld beep.
Send the task definition, region, tagged-item samples, site drawing and required raw/business outputs through Integration Support. Contact AIDC GO for an exact handheld configuration and the fixed-system integration boundary; no fixed-reader product, software feature or site result is asserted for AIDC GO here.
Sources and scope
Impinj’s fixed-reader discussion (published 2022), R700 Series product page and R700 Series product brief dated December 10, 2025 were checked on 2026-09-23. The vendor examples illustrate configuration boundaries only; regional availability and supported firmware must be confirmed for the actual proposed model. The depot example is editorial and contains no test result.