When an RFID rollout stalls and we get called in to rescue it, the post-mortem almost always lands on the same handful of root causes. None of them are exotic. Here are the ten we encounter most across Indian deployments, with the fix for each — worth a read before any money is committed, not after.
1. Piloting at three sites at once
An ambitious pan-India programme sounds great in the boardroom, but RFID involves tags, readers, antenna tuning, networks, middleware, integrations and people — far too many variables to debug across multiple cities in parallel. Fix: prove one zone inside one facility, run it cleanly for about a month, and only then clone the working blueprint to the next location.
2. Tags that ignore physics
Stick a standard inlay straight onto a steel asset and it will simply not respond; put a 13.56 MHz tag on a shipping carton and the reach is hopelessly short. Material drives tag choice. Fix: on-metal tags for steel and machinery, ordinary UHF label inlays for cartons and plastics, washable laundry tags for linen and uniforms, and HF or NFC for cards and wristbands. Sample on the actual material before committing.
3. Tagging only part of the stock
Coverage of seventy percent delivers roughly none of the benefit, because the untagged remainder corrupts every count and the floor quickly stops believing the numbers. Fix: go to full coverage before cutover — and if that is impractical in one push, complete whole categories at a time (every finished good, or every IT asset above ₹25,000) rather than tagging at random.
4. Keeping barcodes running forever
“Scan both, just in case” doubles the labour while delivering the old benefit, which wrecks the business case and demoralises operators. Fix: allow a brief overlap of a couple of weeks, then have management formally retire the barcode step. Left alone, the familiar process always outlives the new one.
5. Skipping the site survey
Steel racking, concrete, water tanks, charging bays and dense Wi-Fi all bend UHF behaviour, and a floor that looks clean on a drawing can hide a dead zone behind a stack of drums. Fix: before ordering anything, walk the space with a handheld reader, watch live read rates, and let the findings shape antenna positions and model choices.
6. Letting the electrician place the readers
If portals go wherever a socket happens to exist, you get off-angle reads, phantom triggers and missed tags. Fix: position readers where goods actually move, at the correct height, with clear sightlines — decided jointly with your RFID integrator during design, not on installation day.
7. Nobody owns the system after go-live
Launch week is exciting; week ten is when master data drifts, new stock arrives untagged and process changes bypass the software. A year on, an investment worth tens of lakhs is functioning as a fancy barcode substitute. Fix: name a single accountable programme owner — someone credible both on the floor and with systems — before signing anything.
8. Leaving integration for later
An RFID platform that only feeds its own dashboard is an island: ERP, WMS and e-commerce keep trading on stale counts. Fix: scope the integration on day one. With REST APIs and webhooks available, a typical ERP hookup is a two-to-three-week effort, and it is what converts reads into decisions.
9. Bulk-ordering unproven hardware
Discovering after delivery that the firmware rejects your chosen chip family, or that a handheld’s Android build refuses your corporate MDM, is an expensive lesson when lakhs of rupees of equipment are already on the dock. Fix: order single evaluation units first — India RFID Store ships individual readers and tag samples with GST invoice — validate against your exact software, network and tags, then place the volume order.
10. Treating training as optional
Operators who distrust the system avoid it; avoided systems produce no data; and without data the dashboards that justified the budget stay empty. Fix: schedule a few hours of hands-on practice per operator, return for floor walks in the following weeks, and let confident early users coach the rest.
The pattern behind all ten
Notice the theme: these are operational failures, not technology failures. RFID succeeds when operations leads and IT supports, when the pilot is small, the tagging is complete, the hardware matches the material, and one named person stays accountable. If the underlying technology is still new to you, our RFID basics primer explains tags, readers and EPC data in plain language.
Getting ready to roll out RFID and keen on an experienced review of your tag and reader choices first? Contact our team for a free consultation.