RFID in Logistics and Supply Chain in India: Gate, Dispatch and Transit Visibility

Inside the four walls, RFID is a settled argument — our warehouse inventory ROI guide works through the numbers for stock accuracy and cycle counting. This post covers the harder half: what happens once goods start moving. Gate and dock cycle time, dispatch errors that only surface at the consignee's premises, 3PL service levels neither party can prove, and the compliance layer — GST e-way bill and FASTag — that Indian logistics already runs on and almost nobody mines for visibility.

The framing matters, because most logistics RFID projects here fail the same way: they are sold as "track your shipment across the country", which RFID does not do. What RFID does extremely well is timestamp custody at fixed points, automatically, without a human deciding to scan. Get that distinction right and the business case is straightforward.

Goods in motion is a different problem from goods at rest

In a warehouse the question is what do I have and where is it. In transit it is who had it, when did custody change, and can I prove it. That shift changes which technology wins.

RFID is a choke-point technology, not a continuous-location technology. It tells you with certainty that carton 4,812 crossed dock door 7 at 14:03 and was loaded onto vehicle DL01AB1234. It tells you nothing about where that carton is at 19:00 on the Delhi–Jaipur highway. GPS tells you where the truck is but has no idea what is inside it. A working design uses both, and the RFID reads are what make the GPS trace mean anything at consignment level — which is what an RFID logistics and supply chain system exists to stitch together.

The gate: where Indian dispatch time actually disappears

Walk any mid-sized Indian distribution centre at 6 pm and the bottleneck is rarely picking. It is a queue of trucks outside the gate, a guard with a register, a driver hunting for the dispatch supervisor, and one weighbridge operator. Turnaround is a yard problem long before it is a warehouse problem. Timings below are indicative — measure your own before believing anyone's numbers, including these.

The detention clock is the line item most buyers undervalue. If your transporter contract allows free detention for a fixed window and charges after it, the whole dispute rests on two timestamps a guard writes by hand. Machine-generated gate-in and gate-out records turn a monthly argument into an invoice line. The vehicle-side half of this overlaps almost entirely with an RFID vehicle and parking management system, which is why the two are usually specified together.

The fine print on the constraint. RFID compresses identification and verification. It does not fix a gate whose real bottleneck is one weighbridge, one invoice printer, or a supervisor who must physically sign the challan. Time your gate first: if most of the delay sits in document printing and approval, buy a better dispatch workflow, not readers.

Dispatch verification: catching the mis-ship before the shutter comes down

A mis-ship is one of the most expensive ordinary errors in Indian distribution, because it is discovered three days and 900 km away. You pay return freight, a credit note, a fresh dispatch, the customer's goodwill, and a reconciliation headache when the credit note lands in a different GST return period from the invoice.

The mechanism is simple. A portal at the dock door reads every tagged carton as it loads, compares the read set against the pick list and invoice in real time, and alarms on three conditions: a carton on the truck but not on the invoice, a carton on the invoice that never crossed the portal, and a carton belonging to another order or route. The alarm must fire while the shutter is still open — an overnight exception report is an audit trail, not a control.

Two things decide whether this works. First, read reliability against your actual product. Dense stacks, liquids, foil-lined packaging and metal cages all attenuate UHF signals, and a portal that reads 96% of cartons is worse than useless: it generates false shortage alarms staff quickly learn to dismiss. Run a read-rate trial with your own pallets at your own stack height before ordering, the same discipline our RFID reader buying guide applies to hardware selection. Second, the transition must be complete. If loaders keep scanning barcodes alongside the portal "just to be safe", you have added cost and removed nothing.

Proving 3PL SLAs: the value is evidence, not speed

For a 3PL the argument for RFID is usually misstated as efficiency. The real argument is evidence. Logistics contracts are full of commitments neither side can prove, so disputes get settled by relationship and volume leverage rather than fact.

The returnables row is where unglamorous money sits. Plastic crates, roll cages, steel pallets, cylinders and kegs leak continuously in Indian networks, and the loss is written off as consumables because nobody can attribute it. A dedicated RFID pallet tracking system exists precisely to make that attribution possible — a dispatch and receive note per trip, per pallet. Tagging them with rugged on-metal UHF tags and reading at every gate produces a per-customer, per-route recovery report. That is closer to RFID asset management than shipment tracking, and it often pays back faster, because the tags are reusable for years.

Settle one contractual point before the pilot: who owns the tag and who pays for it. The shipper usually benefits most from item-level tagging while the 3PL bears the tagging labour. If that is not in the contract, the programme stalls exactly when it starts working.

The compliance layer nobody budgets for: e-way bill, FASTag and ULIP

This is the part missing from most RFID discussions in India, and it is free visibility you already generate.

GST e-way bill

An e-way bill is required for movement of goods above a threshold value — ₹50,000 for inter-state movement, with states free to set their own intra-state thresholds and exemptions, so check your state's notification rather than assuming. Part A carries invoice and goods detail; Part B carries the vehicle number and must be updated whenever the vehicle changes, including at a transshipment hub. Validity runs roughly one day per 200 km for regular cargo, one day per 20 km for over-dimensional cargo. Rules on back-dated generation and extensions have been tightened by recent NIC advisories and two-factor authentication is being enforced, so verify the current position before automating against the portal. Operationally, Part B is the join key between your consignment data and everything the government already sees about that vehicle.

FASTag — the RFID network you already pay for

FASTag is passive UHF RFID (ISO 18000-6C, 860–960 MHz) on a windscreen sticker, read at toll plazas under NPCI's National Electronic Toll Collection programme and mandatory for four-wheelers on national highways since February 2021. The e-way bill system is integrated with it: toll-plaza crossings for the vehicle in Part B are visible against the e-way bill, and the portal exposes vehicle-movement reports built on that data. Officers use it to spot mismatches — a vehicle that never crossed a plaza on its declared route, or a bill still open long after delivery.

You can use the same data commercially: reconciling declared routes against actual toll crossings surfaces diversions, ghost trips and inflated freight claims without buying a device. The limits are real — coverage is national-highway plazas only, so state highways, city runs and last-mile legs are dark; pings are sparse and event-driven; and a stale Part B breaks the chain entirely.

E-seals and ULIP

For exports, CBIC's self-sealing procedure uses tamper-evident RFID e-seals on containers, readable at ports and ICDs, with the seal number tied to the shipping bill — check current circulars, as scope and deadlines have been revised more than once. Separately, the Unified Logistics Interface Platform (ULIP), built under the National Logistics Policy and PM Gati Shakti, offers API access to government logistics data including FASTag, VAHAN and e-way bill. Indian Railways has also tagged rolling stock with UHF RFID read by trackside readers, which matters if your inbound moves by rake.

Sequencing point: mine the compliance data you already generate before buying hardware. It costs nothing, establishes a real baseline, and tells you whether your visibility gap is at your gates — where RFID helps — or on the road, where it does not.

Hardware and tag choices for Indian conditions

Two India-specific constraints get skipped in imported specifications. The delicensed UHF RFID band here is 865–867 MHz under WPC rules, not the 902–928 MHz band used in North America, so readers must be procured or configured for it. And yard environments mean 45 °C summers, monsoon ingress, heavy dust and grid interruptions — specify IP-rated enclosures, surge protection, UPS backing, and edge buffering so reads are stored and forwarded when the network drops. A gate reader that loses events during a power flicker destroys the audit trail you bought it for.

Indicative for planning only; prices move with volume, specification and supplier. Passive UHF covers almost every logistics use case here — active tags earn their cost only in large yards needing zone-level presence rather than gate events, a trade-off covered in our active vs passive RFID comparison.

Where RFID is the wrong tool

• You need continuous in-transit location. That is GPS. No amount of RFID gives you road position between choke points.
• Volumes are low. A site handling 15 trucks a day across two docks will not recover gate hardware from cycle time. Barcode plus a disciplined checklist is the honest answer, and our RFID vs barcode cost and ROI breakdown shows where the crossover sits.
• Consignments are open-loop and thin-margin. If tags never return and per-unit contribution is a few rupees, tag the pallet or the returnable container, not the unit.
• Your master data is broken. Duplicated SKU masters and free-text locations mean RFID produces wrong information faster. Fix that first — it is the most common failure in our list of RFID implementation mistakes.
• You need condition, not custody. Temperature, shock and humidity need sensor tags or loggers.

A rollout sequence that survives an Indian yard

1. Baseline from data you already have. Three months of e-way bill and FASTag movement data gives you real transit times, route compliance and gate dwell before you spend anything.
2. Instrument one gate. Vehicle tags, one lane, automatic barrier, timestamps posted to your system of record. Smallest scope with a measurable number attached.
3. Add one dock-door dispatch portal. One high-volume door, real-time invoice matching, alarm while the shutter is open. Run parallel for a defined period, then switch the manual check off.
4. Close the returnables loop. Tag cages and pallets, report recovery by customer and route. Often the fastest payback in the programme.
5. Extend across sites and to 3PL partners, tied into your RFID warehouse management system and ERP so events post to the system of record, not just a dashboard.
6. Layer analytics last. Once event data is clean, anomaly detection on dwell and route patterns earns its keep — the approach in our guide to RFID and AI integration. Not before.

What to measure

• Gate-in to gate-out, median and 90th percentile, by shift and vehicle type
• Dock-door read accuracy — expected cartons actually read, per portal, daily
• Mis-ship rate per thousand consignments, and rupee cost per incident
• Detention hours billed versus written off
• Returnable asset recovery rate by customer and route
• E-way bills open past validity, and route-versus-toll-crossing mismatches

Every one of these needs a documented pre-RFID baseline. Without it you will argue about the benefit for the life of the system.

Where to start

Start at the gate: cheapest place to prove the mechanism, and the timestamps are contractually useful from week one. Extend to dispatch verification once read rates are proven against your real product mix. And treat e-way bill and FASTag as a free, government-maintained visibility feed to join to your own reads, not as compliance overhead. To scope this for a site or 3PL network, our shipment visibility platform covers gate, dispatch and multi-site custody, and pairs with an RFID inventory management system on the stock side. Talk to the Identium team with your gate volumes and dispatch error rate and we will tell you honestly whether the numbers work.

Cold chain and condition monitoring

Identity is only half the custody story for pharma and perishables — the other half is condition. Battery-assisted (semi-passive) sensor tags log temperature on a schedule and release the log at the next read point, which fits the choke-point model exactly: you cannot see the excursion live on the highway, but you know at the receiving dock, before goods are accepted. Scheduled logging needs a power source, so treat any “fully passive” temperature-logging claim with suspicion. The Identium logistics and supply chain system supports these tags alongside standard EPC Gen2 identity tags on the same reader estate.

Frequently asked questions

Can RFID track my shipment across India in real time?

No. RFID is a choke-point technology — it records custody with certainty at fixed read points like gates, dock doors and portals, but gives you nothing between them. Continuous in-transit position requires GPS or telematics. The practical design combines both: GPS tells you where the truck is, and RFID reads tell you exactly what is on it.

How does RFID reduce truck turnaround time at an Indian distribution centre?

A UHF windscreen tag read at the boom barrier replaces manual register entry, phone calls to the dispatch supervisor and verbal dock assignment, cutting identification and appointment validation from several minutes to seconds. Gate-in and gate-out become system timestamps rather than handwritten entries. It will not help if your actual bottleneck is a single weighbridge or invoice approval, so time your gate before you buy anything.

What is the link between the GST e-way bill and FASTag?

The e-way bill system is integrated with FASTag, which is itself passive UHF RFID read at national highway toll plazas. Toll-plaza crossings for the vehicle recorded in Part B of the e-way bill are visible against that bill, and the portal exposes vehicle-movement reports built on the data. Businesses can reconcile declared routes against actual toll crossings to spot diversions and inflated freight claims without buying any hardware.

What RFID frequency is legal for logistics use in India?

The delicensed UHF RFID band in India is 865–867 MHz under WPC rules, which differs from the 902–928 MHz band used in North America. Readers must be procured or configured for the Indian band, so imported specifications should always be checked. Yard hardware should also carry appropriate IP-rated enclosures, surge protection and UPS backing for Indian conditions.

How does RFID help prove 3PL service levels?

The value for a 3PL is evidence rather than speed. RFID can evidence dock-to-dispatch turnaround, dispatch accuracy, detention and demurrage hours, and returnable asset recovery using machine-generated timestamps instead of a guard's register. It cannot evidence delivery time at the consignee or in-transit temperature unless the consignee has readers or you add sensor tags.

When is RFID the wrong choice for logistics?

Skip RFID when you need continuous road position (use GPS), when volumes are low — a site running 15 trucks a day across two docks will not recover gate hardware costs — or when consignments are open-loop and thin-margin, where tagging the pallet beats tagging the unit. Also fix broken master data first, because RFID simply produces wrong information faster. Temperature and shock monitoring need sensor tags, not standard passive UHF.