> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# The RFID reader

> Pairing a handheld RFID gun, reading tags, and writing a new tag against an asset.

Support for a handheld RFID reader — a Zebra, TSL or Chainway sled — paired to the handset, for sites
that tag assets rather than only barcode them.

## Pairing

**More → Tag reader** is where a gun is paired, deliberately separate from any one scan box: it's a
decision about the handset, not about the field being answered, and once paired every scan box in the
app knows about it.

Pairing a gun needs the native app with the vendor's own library available — a browser has no plugin
for it, an iOS build has no adapter yet, and an Android build still needs the vendor's library present
before any adapter can claim the hardware. Where none of that is true, this screen says so plainly
rather than showing a control that does nothing.

## Sweeping for tags

With a gun paired, pull the trigger to listen for tags nearby — useful for finding which asset in a
rack answers to which tag, or confirming a tag is readable at all.

## Writing a tag to an asset

**Encode tag**, reached from an asset's own screen, writes that asset's code onto a physical tag.

The code itself is never typed here — it's whatever your [label template](/config/labels) already
generated for that asset, fetched fresh rather than invented on the spot. This screen only offers to
put it on a tag; if nothing has ever been generated for the asset, it says so rather than making one
up.

<Note>
  Writing a tag changes nothing on the server — there's no queued operation behind it. It either
  landed on the tag or it didn't, and the screen says which; encoding a hundred assets from a gun in
  hand needs no signal at all.
</Note>

<Card title="Labels" icon="tag" href="/config/labels">
  Designing the template a tag's code comes from.
</Card>