How to Use RFID to Verify Warehouse Receiving and Shipping?
Oct 03, 2026
Leave a message

At a warehouse dock, RFID replaces one-by-one barcode scanning with bulk identification: passive UHF tags on cases or pallets are read by fixed readers at the dock door or by handheld readers, and the warehouse software compares those reads with what was expected - the advance ship notice (ASN) at receiving, or the order and load plan at shipping. The value comes from that comparison, not from the read itself. It holds up only when tags carry consistent identifiers, the read zone is controlled so it does not pick up neighbouring doors, and every mismatch has a defined next step.
This guide covers how RFID fits into inbound and outbound flows, what must be in place before a dock read can be trusted, how to set up the read zone, how to handle exceptions, and which regional radio rules apply. For choosing tag types and specifications, see what UHF tag spec sheets leave out for warehouse logistics.
How RFID fits into inbound and outbound warehouse flows
| Process step | What is read | Checked against | Typical exception |
| Receiving at the dock | Pallet tag, plus case tags if goods were tagged at source | ASN or purchase order | Short, over or wrong item |
| Tagging untagged goods | New tag, encoded and verified at receiving | Item master and receiving record | Encoding error or duplicate identifier |
| Putaway | Pallet tag and storage location tag | Location assigned in the WMS | Pallet stored in the wrong location |
| Picking and packing | Case or item tags in the packed unit | Pick list | Missing or substituted item |
| Loading at the dock | Pallet and case tags passing the door | Order and load plan assigned to that door | Right pallet on the wrong trailer |
| Cycle counting | All tags in an aisle or zone, usually with a handheld | System inventory | Unrecorded moves or shrinkage |
Receiving and loading are where errors become expensive: an unnoticed receiving discrepancy turns into an inventory error, and a loading error turns into a customer claim. GS1 US describes both sides of this: shippers can catch packing or shipping mistakes before goods leave, and receiving facilities can confirm packing accuracy automatically.
What must be in place before a dock read means anything
Consistent identifiers on every tag
A read is only useful if the software can resolve the tag to a known unit. The GS1 EPC Tag Data Standard defines how Electronic Product Codes correspond to GS1 keys. In that standard, the SSCC scheme identifies a logistics unit such as a pallet load, and the SGTIN scheme identifies trade items. Using these schemes instead of arbitrary serial numbers lets trading partners decode each other's tags.
If suppliers ship untagged goods, tags can be encoded one at a time with a handheld reader or in batches with an RFID label printer at the receiving station. Either way, encode and verify the tag before the goods go into storage; a pallet that enters racking with a bad tag becomes an exception at every later step.
Aggregation: which cases are on which pallet
Pallet-level verification only works if the system knows what the pallet contains. Record the case-to-pallet relationship when the pallet is built, whether by the supplier or at your own receiving station. GS1's EPCIS standard provides a common event format for this: it records the what, when, where and why of events such as packing cases onto pallets, receiving and shipping, and version 2.0 adds JSON/JSON-LD syntax and a REST API for capturing and querying event data.
An expected list to compare against
Receiving needs the ASN or purchase order in the WMS before the truck arrives. Shipping needs the order and load plan assigned to a specific door. Without an expected list, a dock reader produces a list of tags, not a verification result.
Choosing how to capture reads at the dock
| Capture method | Best fit | Limitations | What to validate on site |
| Fixed dock-door portal (reader with antennas at several angles around the door) | High-volume doors where pallets move by forklift | Can pick up tags from adjacent doors or staged pallets; needs power and network at the door | Read completeness on the densest, worst-oriented pallet; reads from neighbouring doors |
| Handheld UHF reader | Low-volume doors, exception checks, cycle counts and tagging at receiving | Results depend on operator technique; slower for full trailers | Whether operators cover every face of the pallet |
| Portal for flow, handheld for exceptions | Most mixed operations | Two workflows to train and support | A clear rule for when a handheld re-check is required |
Controlling the read zone
At dock doors, reading the wrong tags is as much of a problem as missing tags: a pallet staged beside the door, or a load passing the next portal, can appear in the wrong transaction. Practical controls include:
Set reader power to cover the door opening rather than the maximum the reader supports. Extra power extends reads into staging lanes and neighbouring doors.
Aim antennas into the doorway and test height, angle and spacing with real loaded pallets. The trade-offs between gain, beamwidth and polarization are covered in how to choose a UHF RFID reader antenna.
Read only while a load is passing, for example by triggering the reader from a motion or presence sensor, and tie every read to a door and an open ASN or order.
Where direction matters, place antennas so the software can see the order in which they read a tag, instead of inferring direction from the door alone.
Treat a tag that is read but not expected as something to check, not as automatic proof that the wrong goods are on the pallet.
Materials that affect UHF reads
Metal reflects UHF energy and liquids absorb it, and densely packed pallets can shield inner cases from the antennas. Tags mounted directly on metal need an on-metal design such as ABS anti-metal UHF tags. For products in liquid or foil packaging, test tag position before fixing a label layout. Where inner cases cannot be read reliably at the door, verify at pallet level (the pallet tag plus the recorded aggregation) and keep case-level checks for the handheld.
Handling exceptions at receiving and shipping
| Exception | Possible causes | Recommended action |
| Expected tag not read | Item missing; tag damaged, shielded or badly placed | Re-read the pallet with a handheld before recording a shortage |
| Unexpected tag read | Wrong item on the pallet; stray read from an adjacent door or staging lane | Check which antenna and door produced the read, and confirm physically before rejecting |
| Same tag read many times | Normal repeated reads while the pallet passes | Filter duplicates in middleware by tag identifier and time window |
| Tags read with no matching ASN or order | ASN not sent or not yet loaded; unplanned delivery | Hold the goods in a receiving exception location until the data is reconciled |
| Tagged goods leaving without an open order | Unauthorized movement, or an order not yet released in the WMS | Alert a supervisor and confirm order status before treating it as a loss |
Note: An exit alert only covers goods that still carry a readable tag and pass through a monitored read zone. It supports loss prevention, but it does not replace physical security and access control.
Regional frequency and power rules
Passive UHF RFID in supply chains uses the GS1 EPC Gen2 air interface protocol, which covers the 860–960 MHz band. Within that band, each region permits different frequencies and power levels, so readers must be configured and certified for the country where they are installed.
| Region | Rule | Band | Power limit (summary) |
| United States | FCC 47 CFR §15.247 | 902–928 MHz | 1 W peak conducted output for frequency-hopping systems using at least 50 channels; output must be reduced when antenna gain exceeds 6 dBi |
| Europe | ETSI EN 302 208 V3.4.1 (2023-12) | 865–868 MHz and 915–921 MHz | Up to 2 W and up to 4 W respectively; availability of the upper band depends on national implementation |
Other countries set their own allocations, so check the national regulator before specifying readers. Many passive tags are designed to respond across 860–960 MHz, but performance can differ from one band to another; test tags at the frequency your readers will actually use. If you are sourcing hardware, compare the frequency listed for each UHF RFID reader or UHF handheld reader with your region's band before ordering.
What published evidence says about accuracy
A study by the Auburn University RFID Lab and GS1 US, announced in October 2018, followed more than one million items from five retailers and eight brand owners between June 2017 and June 2018. It reported that 69% of orders shipped and received between brands and retailers contained data errors, and that item-level RFID supported 99.9% order accuracy.
Scope of these figures: the results come from retail supply chains using item-level tagging. Operations that tag only pallets, or that handle metal and liquid products, should measure their own baseline and pilot results rather than assume the same figures.
Pilot checklist before rolling out to every door
Measure current receiving and shipping error rates and time per load, so the pilot has a baseline.
Choose one inbound and one outbound door with representative products, including your hardest-to-read items.
Confirm tag data: identifier scheme, encoding, aggregation records, and who applies tags (supplier or your own team).
Confirm the WMS can accept reads and return a verified or exception result for each ASN or load.
Test the read zone with real loaded pallets: read completeness, reads from adjacent doors, and direction.
Write the exception procedure and train the operators who will carry out handheld re-checks.
Confirm readers and antennas meet the radio rules of the installation country.
Compare pilot results against the baseline before adding more doors.
Send Inquiry

