The complete guide to RFID asset tracking

RFID asset tracking can turn a register that people update from memory into one that updates itself. It can also become an expensive collection of readers that nobody trusts. The difference is almost never the technology — it is the design: which assets get tags, where readers go, how raw reads become business events, and how the system is tested and maintained.

This guide covers everything you need to plan, pilot and operate a passive UHF RFID asset-tracking deployment: fundamentals, tags, readers, zones, data standards, testing, rollout and day-to-day operations.

What RFID asset tracking is — and is not

RFID asset tracking uses RFID tags attached to assets and RFID readers to identify those assets without line of sight. In asset management it serves two main purposes:

1. Fast counting. A handheld reader reads many tags in a single sweep, making stock-takes and cycle counts far faster than one-at-a-time scanning.
2. Automatic movement detection. Fixed readers at doorways and gates record when tagged assets pass, keeping locations current and triggering alerts when something leaves an area it should not.

It is not continuous, pinpoint location tracking. Passive RFID tells you that an asset was read by a particular reader or antenna at a particular time. Between reads, you know its last known location. If you need continuous outdoor position, that is GPS telematics — a different technology with different costs, and not something Asetavo provides.

RFID fundamentals

Passive, semi-passive and active

• Passive tags have no battery. They harvest energy from the reader's field. Small, thin, inexpensive and long-lived — the standard for asset tracking.
• Battery-assisted passive (BAP) tags use a battery to power the chip but still reply by reflecting the reader's signal, giving longer range.
• Active tags have a battery and transmitter, broadcasting on their own. Much longer range and real-time location capabilities, at higher cost and with battery maintenance.

This guide focuses on passive UHF, which covers the large majority of asset-tracking deployments.

Frequency bands

UHF RFID operates between 860 and 960 MHz, with each region allocating a slice: roughly 902–928 MHz in the United States and 865–868 MHz in Europe, for example. Readers must be certified and configured for their region. Most modern tags are designed to respond across the whole band.

Lower frequencies exist — LF (125–134 kHz) and HF (13.56 MHz, including NFC) — but their short ranges make them better suited to access control, tap interactions and specific niches. See RFID vs NFC vs QR for the comparison.

The EPC Gen2 standard

Almost all passive UHF tags follow the EPC Gen2 air-interface standard, also published as ISO/IEC 18000-63. It defines how readers and tags communicate, including an anti-collision protocol that lets a reader inventory many tags in quick succession.

Tag memory banks

A Gen2 tag has four memory banks:

• Reserved — kill and access passwords.
• EPC — the writable identifier you normally link to the asset. See EPC.
• TID — a tag identifier programmed by the chip manufacturer; on most modern chips it includes a unique serial number that cannot be changed. See TID.
• User memory — optional extra storage on some chips.

Best practice is to record both the EPC and the TID when you commission a tag. If the same EPC later appears with a different TID, someone may have cloned or re-encoded a tag — a useful integrity check.

Choosing tags

Tag form factors

• Inlays and labels — a chip and antenna on a thin film, often printed as a label. Lowest cost; for non-metal surfaces.
• On-metal labels — thin, flexible labels designed to work on metal, some of which can be printed and encoded in suitable printers.
• Hard tags — antennas encased in plastic, ceramic or rubber for durability; available for metal and non-metal use.
• Specialty tags — high-temperature, laundry, autoclave, cable-tie, embedded and tamper-evident tags for particular environments.

Selection criteria

1. Mounting surface. Metal needs on-metal tags; liquids reduce performance; plastics and wood are usually straightforward.
2. Required read range for your use case — a few metres for handheld audits, more for portals.
3. Environment — temperature, UV, chemicals, washing, impact.
4. Size and attachment — what physically fits, and whether adhesive, rivets or ties will hold.
5. Printability — do you need a human-readable ID and a QR code on the tag face?
6. Cost relative to the asset's value.

Read on-metal RFID: what to know for the metal-specific details.

Readers and antennas

Handheld readers and sleds

A handheld reader is a self-contained device with a built-in antenna. A sled is a reader that attaches to a smartphone and connects to an app. Both are used for walking audits and for locating a specific tagged item using signal strength (RSSI) — the "hotter/colder" search.

Fixed readers

A fixed reader connects to one or more external antennas (commonly up to four or eight ports) and runs continuously. Fixed readers are used for:

• Portals — antennas on both sides of a doorway or gate to detect assets passing. See RFID portal.
• Zone coverage — antennas over a room, cage or set of shelves to report what is present.
• Choke points — dock doors, lift entrances, store counters.

Antennas

• Circularly polarized antennas read tags in varied orientations, at some cost to range. They are the usual choice when asset orientation is unpredictable.
• Linearly polarized antennas give longer range when tag orientation is known and consistent.
• Antenna gain and beam width determine how far and how wide the field extends. Wider is not always better — it increases stray reads.

From reads to business events

A fixed reader reports raw reads: tag EPC, antenna, timestamp, signal strength. It may see the same tag many times per second. Software has to turn that stream into meaningful events:

1. De-duplication. Many reads of the same tag in a short window become one observation.
2. Location assignment. Each antenna or reader maps to a location or zone.
3. Direction. With two antennas (or two readers) on a portal, the order in which they see a tag suggests whether it went in or out.
4. Dwell and presence. How long a tag must be seen, or missed, before the system decides it has arrived or left.
5. Rules. Is this asset allowed in this zone? Is it checked out? Should an alert fire?

Readers typically communicate using the LLRP (Low Level Reader Protocol) standard or vendor-specific APIs. An edge gateway often sits between the readers and the cloud, translating reader traffic into secure HTTP events.

Designing zones and portals

Start from the questions you need answered, not from the floor plan.

• "Has this asset left the building?" → a portal at each exit that assets can realistically pass through.
• "Is this asset in the tool crib or out?" → a portal at the crib door.
• "What is on these shelves right now?" → overhead or shelf antennas, or periodic handheld sweeps.
• "Which ward is this equipment in?" → portals at ward entrances, accepting that you will know the last door passed rather than the exact bed.

Guidelines:

• Cover choke points, not open space. A few well-placed portals beat many poorly placed antennas.
• Model zones on your location hierarchy so a zone means something to people — site, building, floor, room.
• Decide what "allowed" means for each asset or category, so zone-exit alerts fire only when it matters.
• Plan for stray reads: tags stored near a portal will be read even when they do not pass through. Shield, relocate storage, tune power, or use direction logic.

Encoding and numbering

You need a scheme that guarantees every tag's EPC is unique and maps to one asset.

• Simple approach: encode a unique serial or the asset ID (in hex) into the EPC, and store the mapping in the register.
• Standards-based approach: GS1 defines the Global Individual Asset Identifier (GIAI) for individual assets, which embeds your company prefix and a unique serial. It helps if tags must be interpreted across organizations.

Either way: record EPC, TID and asset ID at commissioning; never reuse an EPC for a different asset without retiring the old link; and consider buying tags pre-encoded to your scheme to save time.

Site survey and testing

RFID performance is highly site-specific. Before committing:

1. Survey each portal and zone location — construction materials, nearby metal, other radio sources, and how assets actually move.
2. Test candidate tags on real assets, mounted as they will be in production.
3. Test reads in the real place, with realistic speeds, orientations and groupings — a trolley of ten assets reads differently from one asset carried alone.
4. Measure read rate: of the tagged assets that passed, what share was read? Test enough passes to be confident.
5. Measure false reads: how often are tags read that did not pass through?
6. Tune and repeat — reader power, antenna angles, dwell settings.

A phased rollout

Phase 1: Foundation

Every asset gets an ID and a record, usually with a QR label. This is independent of RFID and valuable on its own.

Phase 2: Tag the right assets

Score categories for RFID suitability (see the framework in RFID vs NFC vs QR). Tag the high-value, mobile or numerous categories first.

Phase 3: Handheld audits

Use handheld readers or sleds to run audits on the RFID-tagged categories. This proves tag performance and delivers counting benefits with minimal infrastructure.

Phase 4: Portals at critical doors

Install fixed readers at the few doors where movement matters most. Run them in "observe only" mode for a few weeks to tune out false reads.

Phase 5: Rules and alerts

Turn on zone rules and alerts once reads are reliable. Route alerts to people who can act on them.

Phase 6: Expand

Add portals and categories based on measured value.

Integrating RFID with your systems

RFID events are most useful when they flow into the rest of your operations:

• Register — last known location and movement history on every asset.
• Check-outs — a portal read can flag an asset leaving without being checked out.
• Audits — handheld reads populate audit sessions directly.
• Alerts and webhooks — forward alert events to incident, security or messaging systems.
• Reporting — movement and utilization reports.

Operating RFID day to day

• Monitor reader health. A reader that has gone silent is worse than no reader — it creates false confidence. Alert on readers that stop reporting.
• Replace damaged tags promptly, linking the new tag to the existing asset record and retiring the old EPC.
• Tag new assets at receipt, before they enter service.
• Review alerts regularly. If most are false, fix the setup; alert fatigue kills trust.
• Re-test after changes to the physical layout — new shelving or relocated storage can change read patterns.

Measuring success

Useful measures:

• Portal read rate — share of tagged assets passing a portal that are detected.
• Audit duration for RFID-tagged categories, before and after.
• Missing assets per audit — should fall as movement is captured automatically.
• Alert precision — share of alerts that were genuine.
• Time to locate a requested item.

Record baselines before you start, so improvements are measured, not assumed.

Common pitfalls

• Tagging everything. RFID on low-value static assets adds cost without adding information.
• Skipping the site survey. Performance on the bench is not performance in the building.
• Standard labels on metal.
• Portals with no direction logic, producing ambiguous in/out events.
• No monitoring of readers, so outages go unnoticed.
• Treating reads as truth without tuning, then losing trust after false alerts.
• Unauthenticated reader events, which could allow spoofed movements.

RFID asset tracking in Asetavo

Asetavo keeps UHF RFID alongside QR, barcode and NFC in one asset register. The mobile app supports UHF sleds for bulk audit reads and signal-strength "find item" searches. Fixed readers and portals send HMAC-signed events with timestamp and nonce checks, and each device has its own revocable credentials; an edge gateway translates LLRP reader traffic to secure HTTP. Reader events drive zones mapped to your location tree and real-time zone-exit and overdue-checkout alerts, which can be forwarded to your systems through signed webhooks and the REST API. Tagging includes tag inventory and clone-suspected logging. You choose the reader hardware.

UHF RFID, readers, zones and the API are part of the Business plan — see pricing.