“RFID tag not reading” is how the fault always gets reported, and the tag is usually not the reason. In a live deployment the tag is the least common culprit — in our field experience, regional band configuration and reader settings cause far more misses than dead silicon, and neither shows up on a spec sheet. What helps is a fixed order of elimination, using tools the reader already has: a free-air bench test, a region and power check, RSSI on a handheld, and the reader’s own raw log.
Start here: is it one tag, one reader, or the whole site?
Before changing a setting, establish the shape of the failure.
| What you observe | Most likely layer | Configuration or hardware? |
|---|---|---|
| One tag fails, identical tags read fine | Never encoded, or damaged | Hardware — replace it |
| A whole new batch reads poorly everywhere | Region profile, or wrong tag for the surface | Configuration first |
| Reads at the bench, not at working distance | Antenna gain, angle, environment | Both |
| Reads on the handheld, not on the fixed portal | Session, target, dwell, geometry | Configuration |
| Reader log shows the EPC, your application does not | Filters, dedup window, middleware | Configuration |
| Reads fine, plus tags you did not want | Stray reads: power, aim, shielding | Both |
Step 1 — prove the tag is alive with a free-air bench test
Take the failing tag off the asset. Hold it in free air on a wooden or plastic bench, away from metal, liquid and your own hand, and read it at low power. You are not measuring range here, only whether the silicon answers.
- Valid EPC returned. The tag is alive; the problem is downstream in environment, geometry or settings. This is the usual outcome.
- It answers, but the EPC is blank, all zeros or a factory pattern. It was never encoded, or encoding failed at the printer — a process issue, and fixable. Reading the TID bank usually confirms the chip is healthy even when EPC memory is locked or empty.
- No response at all, even held against the reader antenna. Treat the tag as dead: cracked chip, broken strap, delamination, moisture ingress or crush damage. No setting recovers this.
Sample five or ten from the same reel. One failure is attrition; ten in a row points at the encoding step or the application method — the kind of avoidable error covered in ten common RFID implementation mistakes.
Step 2 — check the region: band, power limit and reader profile
More live failures hide here than in the tags. Passive UHF sits between roughly 860 and 960 MHz worldwide, but each regulator opens only a slice of it. In India, as of 2026, the WPC Wing of the Department of Telecommunications has allocated 865–867 MHz for delicensed UHF RFID, with a radiated-power ceiling set out in the relevant WPC notification. Notifications get amended, so confirm the current rule with WPC before you change any setting.
Then check four things: that the reader’s region profile matches the country it sits in, since a unit left on a US 902–928 MHz or wide global profile will typically read Indian-band inlays weakly and erratically — and is also transmitting outside the slice India permits; that the region survived the last firmware update, as some readers revert to a factory default after flashing; that the inlays are tuned for your band; and that power sits inside the legal ceiling once antenna gain and cable loss are counted, because what is regulated is radiated power, not the number on the reader dial.
Never raise transmit power above the permitted limit to chase a read. It is not lawful, and it tends to manufacture stray reads rather than solve the original miss. Our BIS and WPC compliance guide sets out what to ask a vendor for.
Step 3 — the environment: metal, liquid, moisture and bodies
Passive tags are tuned to radiate in free air. Metal reflects and detunes the tag’s antenna; water absorbs the energy. Human bodies are mostly water, so an operator standing between antenna and tag is a real attenuator, not an excuse.
The diagnostic is simple: if the tag reads in free air at your working distance but fails when mounted, the environment is the answer — not the batch, not the reader. Watch for labels applied directly to steel or aluminium, tags on liquid-filled containers, condensation after cold storage, wash-down moisture in soaked cartons, and racking that was empty during the pilot and full in production. Where the surface is the problem, the fix is a tag built for it — an on-metal construction, which typically uses a spacer and a ground plane, as explained in our guide to on-metal tags for tools and assets.
Step 4 — antenna geometry: distance, angle, polarisation and nulls
Read ranges quoted anywhere, datasheets included, are typical figures that depend on the tag, the surface, the antenna, the cable and the room. Bench-test your own combination and design to the distance you actually measure.
- Angle and polarisation. A linear antenna typically reads further but demands consistent tag orientation; rotate the tag ninety degrees and the read can collapse. Circular tolerates any angle at some cost in effective range.
- Gain and beam width. A high-gain antenna concentrates energy into a narrower beam, so it reads the centre of a wide doorway and misses the edges.
- Nulls. Reflections in metal-rich rooms create dead spots. The tell-tale symptom is a tag that reads while moving but not while stationary, or in one position and not ten centimetres away. Reposition the antenna or add a second at a different angle — do not answer a null with more power.
- Cabling. Damaged coax, a loose connector or a mis-mapped port looks exactly like a tag failure. Swap the suspect antenna onto a known-good port.
Our antenna guide on gain, polarisation and placement covers the trade-offs.
Step 5 — reader settings that quietly hide good reads
These raise no error. They simply make real tags absent — and most of what genuinely improves an RFID read rate happens here, not at the tag.
- Session. In S0 tags typically reply repeatedly while energised; in S2 and S3 an inventoried tag goes quiet for a persistence period. If a tag reads on the first pass and vanishes on the second, session is the suspect — not a bad tag.
- Target A/B. A reader locked to target A will not see tags already flipped to B until their state persists back.
- Q value. Set too high for a small tag population it wastes time on empty reply slots; too low for a large one it causes collisions and dropped tags.
- Dwell time and RF profile. With several antennas each gets a slice of the cycle, and too short a slice means the far antenna never completes an inventory round. Faster link profiles trade sensitivity for speed. Increase dwell before you touch power.
Hand-tuning this is slow and hard to repeat. Identium’s ReaderSense reader software approaches it by measurement rather than guesswork: its AISense routine applies candidate configurations to the live reader and compares the results — unique tags seen, read rate, RSSI and per-antenna performance — so you pick a setting on evidence. On a handheld, use RSSI as a hunting tool: walk the tag in and out and watch the value rise and fall to map the real coverage edge.
Step 6 — the software layer: filters, dedup windows and middleware
Some reads reach the reader and never reach your screen. Watch the reader’s raw log rather than your application: if the EPC is in the raw stream, the RF chain is fine and the problem is software. Usual suspects are deduplication windows that suppress repeats for a set number of seconds, so an asset going out and coming straight back looks unread; EPC masks left from an older numbering scheme that silently drop a new batch; reader-side select filters; RSSI thresholds that reject weak reads and take genuine distant ones with them; and business rules that decline to display a “retired” asset.
The opposite problem: stray reads and cross reads
Too many reads is the same physics running the other way, and the cure is physical first. Reduce power within the legal ceiling rather than adding more; re-aim antennas pointing past the zone or into a reflective wall; add downtilt, change height, introduce baffles; move staged stock away from the portal. Only then reach for software — an RSSI floor, direction logic from the antenna sequence, or a minimum read-count rule so a single stray glimpse does not register. Filtering can paper over a badly aimed antenna, but only by discarding genuine reads along with the strays.
When to stop tuning and change the tag
Tuning eventually stops paying. Change the tag when it reads reliably in free air at your working distance but never on the asset, even after antenna, session and dwell changes — the surface has detuned it, and only a different construction fixes that, which is what our on-metal tag range exists for. Change it when reads are position-critical, one orientation working and nothing else. Change it when performance degrades in service through moisture ingress, flexing, heat or adhesive failure — a housing problem, not a settings one. And change it when you had to push power to the regulatory ceiling for marginal reads: with no headroom, an ordinary bad day becomes an outage.
We will not promise a fix or a percentage. What a better-matched tag buys is margin. If you are re-specifying rather than repairing, our guide to scoping read range against the environment is where to restart.
Identium manufactures UHF tags and readers in New Delhi, does its own ultrasonic sealing, epoxy potting and encoding, and typically turns custom hard tags around in 5–10 days. Tell us how the tag is mounted, which reader you are using and how it is configured, and we will tell you which layer you are most likely stuck in — get in touch.