Warehouse RFID Scanner App UI in React Native

A warehouse RFID scanner app sounds simple until you hit the hardware truth: the iPhone cannot read the long-range tags warehouses use. Build the app correctly and it becomes a fast, offline-first front end for an external reader, with barcodes handled natively as a fallback. VP0 is the free, AI-readable iOS design library builders start from for the scan screens, so the bulk-read UI is ready while you wire the reader.

Who this is for

You are building a warehouse or logistics app in React Native, maybe with Cursor or Claude Code, for receiving, cycle counts, or picking, and you want a scanner UI that matches how the hardware actually works. This is the pattern, told honestly.

The honest truth about iPhone and RFID

The most important thing to get right is also the most misunderstood. The iPhone’s built-in NFC, covered by Core NFC, reads short-range 13.56 MHz tags at a few centimeters. Warehouse inventory uses UHF RFID, read from meters away, and the iPhone cannot read it at all. To support UHF in an iOS app you pair an external Bluetooth RFID reader, a sled or handheld, and use its SDK; your React Native app is the UI and the logic on top. Designing around that fact from the start, as the React Native architecture encourages, saves a painful rewrite later.

Design for bulk reads

A UHF reader returns many tags per second, so the UI is nothing like a single-item camera scan. Put a large running count front and center, stream unique tags into a list as they arrive, and give clear start and stop controls. De-duplicate as you go so a tag read fifty times counts once. For the barcode cases, use the camera with the system DataScannerViewController rather than a custom detector, and follow the GS1 barcode standards so your codes mean the same thing across systems. This mixed approach mirrors a warehouse inventory scanner: the two share a spine, a confident running count and a list you can audit at a glance.

Offline-first or it loses data

Concern	Approach	Why
Connectivity	Store reads locally first	Warehouses have dead zones
Bulk reads	Stream and de-duplicate	A reader returns many per second
Barcodes	System camera scanner	No custom detector to maintain
Sync	Reconcile when online	The local store is the truth

Every read is written to a local store before anything else, the worker sees a confirmed count immediately, and the app reconciles with the back end when a connection returns, the same resilience a gloved-hands tool like an employee geofence clock-in needs.

A worked example: a receiving dock

A worker receives a pallet. They pair the Bluetooth UHF reader once, pull the trigger, and sweep it past the pallet. Tags stream in and the running count climbs past 60% of the expected items within a second, then settles as the reader finds the rest; duplicates are collapsed so the number is honest. A few items have damaged tags, so the worker switches to the camera and scans those barcodes one by one with the system scanner. The dock has no signal, but every read landed in the local store, and the screen shows a confirmed local total against the expected count, flagging two missing items. Back in range, the app syncs the whole receipt at once. The worker never waited on a network, and the discrepancy was caught at the dock instead of in an audit weeks later. Crucially, the worker trusted the count because it matched what they could see on the pallet, which is the real test of a scanner UI: not how clever it is, but whether the person holding it believes the number and can act on it without a second guess.

Common mistakes and fixes

• Assuming iPhone reads UHF RFID. It does not; plan for an external reader.
• A single-item UI for bulk reads. Show a running count and a streaming list.
• No de-duplication. Collapse repeated reads of the same tag.
• Requiring a connection. Store locally first and sync later.
• A custom barcode detector. Use the system scanner.

Routing a driver to the next dock is its own problem, handled by a Google Places autocomplete UI for the address entry.

Key takeaways

• iPhone NFC cannot read warehouse UHF RFID; design for an external reader.
• Build a bulk-read UI: running count, streaming list, de-duplication.
• Use the system camera scanner for barcodes.
• Store every read offline-first and sync later, from a free VP0 design.

Frequently asked questions

The FAQ above covers whether iPhone can read warehouse RFID, building the UI, why offline-first matters, and RFID versus barcodes.