“Supports RFID” is not a sufficient specification for a library handheld. A library may already have tagged items, a catalogue, a circulation system and established shelf locations. The buyer needs to know which existing tags can be read, which identifier the software resolves to one physical copy, and how a shelf observation becomes an actionable exception without silently changing a loan record.
This guide uses an editorial shelf example, not a library customer case or an AIDC GO interoperability test. A handheld can assist stocktaking and searching; it does not, by detecting a tag, perform the library system's circulation transaction.
Begin with the tags and records already in service
Collect representative existing tags from books, media and any special collections. Identify their frequency, protocol, chip or tag type, encoding and any access or security configuration. A library may use different technologies across collections; “library RFID” alone does not select one. The HF/NFC compatibility guide explains why band, protocol, data access and application operation must be checked separately. An AIDC GO UHF product page is not evidence of HF support.
Keep the record fields distinct. A tag UID is an observed chip identifier; a library item or accession number identifies a particular circulating copy under the library's data rules; a bibliographic record describes a title or edition; a location is where the system expects that copy; and loan status says whether it should currently be on a shelf. The existing system may encode the item number in tag memory, map a UID to a copy in a database, or use another approved method. The buyer must discover which method the current collection uses before comparing readers. The UID-to-asset-record guide covers identifier formatting and replacement, not the library's shelf workflow.
FEIG's library solution overview describes separate handheld inventory/search, self-checkout, security gates and smart shelves in its own portfolio. Its ID PRH200-BW page identifies a 13.56 MHz handheld with ISO 15693 transponder support and ISO 18000-3M3 as an optional capability. These are claims about that named FEIG product and option, not all library tags, all FEIG readers, or any AIDC GO model. A different tag population requires its own matching test.
Turn a shelf pass into three different exceptions
In an editorial example, a shelf list expects physical copies B-101, B-102 and B-103 in Bay 4. The handheld reports tags resolving to B-101, B-103 and B-208. B-102 is expected but not observed. B-208 is observed but its approved location is Bay 7. The circulation system still marks B-103 as on loan, although a copy labelled B-103 appears in Bay 4. The identifiers and observations are invented; no detection rate is implied.
For B-102, first inspect the actual shelf and adjacent positions, then check the tag, book and expected-list freshness. A non-read does not establish loss. For B-208, confirm the physical copy and current location record before recording a shelving exception; a reader's detection area is not a precise shelf coordinate. For B-103, hold the discrepancy for circulation staff to reconcile the loan record and the physical copy. The inventory app should not silently check in a book merely because its tag appeared. A title-level bibliographic match would also be insufficient: two copies of one title may have different item records and loan states.
A hand-held pass does not guarantee the order in which books are physically arranged. Neighboring books, antenna orientation and repeated reads can alter observation order. The application can compare the deduplicated observed set with an expected shelf set; a fine-grained physical sequence requires a separately validated method. The RFID locate-versus-inventory guide explains why a search for one known item and a population check have different completion rules.
Keep circulation and security actions separate
Stocktaking asks which item identities were observed in a defined pass. Locating asks the operator to search for a selected item under the reader and application's supported feedback. Self-checkout, staffed return and security-gate detection are different transactions and hardware arrangements. A shelf observation must not be converted into a loan or return event without the library system's actual authorization and workflow.
FEIG describes automatic checking and rewriting of an AFI byte for its named handheld/library context. Even where such an operation is supported by the exact tag, reader option and software, an AFI state change is not proof that the circulation database recorded a checkout, return or patron identity. The library's item and patron records remain authoritative. Do not infer security configuration or gate behavior for another installation from an AFI label alone.
For an offline shelf list, record when the list was generated and which location and loan states it represented. If an item changes status elsewhere while the handheld is offline, the uploaded observation may conflict with a newer circulation record. The application needs an explicit review or reconciliation path; a later upload must not simply overwrite the newer state. This is an application and library-system requirement, not a generic reader function.
Prove the actual tag–reader–software path
Use a small sample of the collection's real tag variants and item states. Demonstrate a correct item match, an unknown tag, two copies of one title, a location mismatch, an item marked on loan and a tag that is physically present but not read on the first pass. Preserve the raw reader value and the normalized library item key so a format mismatch can be diagnosed. Check that the target software receives the intended field, can load the correct expected list and records exceptions without making an unauthorized circulation change.
For the reader configuration, record the exact model and enabled protocol option, firmware, host connection, application version and library-system interface. For the tag, record the chip or label part, encoding and mounting in the book. Compare the test on normal shelves, with representative stacks and operator movement. The result should say which samples and operations passed, which were excluded and why; a frequency label or successful UID read does not prove the whole workflow.
Use Integration Support to document the reader/software boundary and contact AIDC GO with the existing tag and item-record samples. The current AIDC GO product catalogue must not be treated as a confirmed library HF handheld configuration without model-specific evidence. The selection question is whether the named assembly resolves the library's existing physical copies and exception states correctly—not whether a product category says RFID.