Choose a fixed UHF RFID reader’s software interface by the events your application must receive and the control it must exercise—not by the word “API” in a quotation. LLRP is a standardized low-level reader–client protocol; a vendor SDK or device interface may wrap it, extend it or expose a different contract. Neither choice by itself maps a tag observation to a shipment, lane or accepted inventory transaction. Ask for the exact reader, firmware, supported interface version, report fields and a witnessed end-to-end event.
The fixed-versus-handheld guide decides where observations should occur. The antenna-hub guide maps physical paths to zones. Here the distinct purchase decision is whether the proposed reader/client interface can control the required inventory operation and deliver enough trustworthy metadata to the business application.
Specify the interface by function and version
The GS1 Low Level Reader Protocol, Release 2.0, describes version negotiation, reader operation specifications, reports, event notifications and keepalives. It also defines extension points. That standard describes a protocol; it does not certify that a particular reader implements Release 2.0 or every optional operation. Procurement should list the negotiated or documented version, required standard commands, vendor extensions and client library separately.
For a bounded third-party example, Impinj’s R700 product information describes its own reader and developer ecosystem, while Impinj’s support article on KeepAlives and LinkMonitorMode with Octane SDK and LTK explains vendor-specific connection monitoring and recovery options. The support article is not a versioned implementation contract for every R700 firmware build. It demonstrates why a buyer must request the *current* reader/firmware and client-library documentation rather than assuming the latest GS1 LLRP release or a named SDK function is present. Neither source is evidence that AIDC GO supplies that reader or either interface.
A REST endpoint used for configuration is not automatically a tag-event stream. Likewise, an SDK being available does not prove your application’s language, operating system, licensing or deployment model is supported. Ask the supplier to demonstrate the actual tag-event path and to identify which software component owns the reader connection, filtering and business-event conversion.
Decide which layer owns each requirement
Write a short interface contract before selecting a library: reader identity, antenna reference, EPC or selected memory value, observation timestamp and clock source, report trigger, duplicate handling, connection-loss indication and restart behavior. Confirm whether each requested field is emitted by the reader, constructed by middleware or derived by the application. A raw EPC read is not a completed goods movement. If the workflow needs a business identifier rather than raw bits, use a documented decoding and database mapping step; the EPC-data guide covers that conversion.
LLRP may fit when a team needs defined low-level control and has the expertise to operate its client, version negotiation, reports and extensions. A documented vendor SDK or higher-level interface may shorten development for a supported reader and language, but may couple the application to that vendor’s version and event model. A custom extension that one reader needs for a desired field can narrow portability even when the baseline transport is LLRP. Evaluate the exact function and upgrade path, not a blanket “standard is portable” or “SDK is easier” claim.
Walk a tag observation through a controlled trial
Editorial test scenario, not a customer deployment or measured result: A fixed reader observes tagged carton C-17 moving through lane A while tagged carton C-18 waits close to lane B. The proposed client records reader ID, reported antenna ID, raw tag value, report time and any reader event. Middleware applies the documented lane and duplicate rules. The application then looks up the carton and records an accepted movement only when its business conditions are met. These labels are teaching identifiers; no protocol feature is inferred from their spelling.
First check the reader-side report: if C-17 is absent, inspect RF coverage and the configured inventory operation. If C-17 is present with the wrong antenna reference, verify the wiring and port map. If the report is correct but the application shows C-18 or no movement, trace decoding, filtering and database matching. If a connection drops after the reader observed C-17 but before the business acknowledgement, inspect the backend record before replaying a movement; a successful reconnect alone cannot tell whether the transaction was accepted. The multiple-reader guide addresses cross-reader overlap separately.
Make acceptance reproducible
- Record the reader SKU, firmware, region, client runtime, SDK or LLRP version, library build, enabled extensions, antenna map and exact configuration snapshot.
- Run a known-tag set through the intended lanes. Retain the lowest-level output accessible under the chosen interface and the final application records. Check required report fields, observed timing, omissions and duplicate behavior without treating a test population as a performance guarantee.
- Deliberately interrupt and restore the network and reader power in a safe test. Confirm detection, reconnection, configuration restoration and whether the business system can reconcile any uncertain event without silently double-counting it.
- Change one reader or client software version in a controlled environment and repeat the contract tests. If the quote relies on a vendor extension or a middleware mapping, require the supplier to document ownership and upgrade support for that component.
Reject a quote that supplies only a port list and a generic “LLRP supported” tick box when the project needs particular report fields or recovery behavior. Conversely, do not reject a higher-level interface solely because it is not LLRP if it demonstrably produces the required audited business event on the supported version. Bring the interface contract, tag samples and a sample event payload to AIDC GO Integration Support or contact AIDC GO. No AIDC GO fixed-reader model, LLRP implementation, SDK or middleware is asserted by this article.
Sources and scope
Checked 2026-09-24: GS1 LLRP Release 2.0, especially sections 5–8, 11 and 14; Impinj R700 product information; and Impinj support guidance on KeepAlives and LinkMonitorMode with Octane SDK and LTK. The standards document and manufacturer example have different scope. Obtain current firmware and interface documentation for the actual procurement SKU.