Hardware Agnostic

Buy the reader that fits your business. Not the one our software forces on you.

Most RFID platforms quietly lock you into one hardware vendor. Ours doesn’t, and here’s the actual engineering reason why.

What this actually means

Every use case has a different ideal device. We support all of them.

Being hardware agnostic means more than accepting more reader brands. A stockroom cycle count, a fitting room read, and a DC audit station all call for genuinely different hardware, and Clarity is built to work with whichever one the job actually calls for.

Use caseHardware type
General store operations, long-range scan
RFID handhelds
Targeted, short-range reads
RFID handhelds, pocket-size mobile devices
Continuous reading & item locationing
Overhead fixed readers
Loss prevention & transition points
Exit readers (overhead / underfloor)
Automatic read at point of sale
POS / self-checkout readers
Supply chain throughput & audit
DC tunnels, packing & audit stations
The mechanism

Two integration paths. One consistent language either way.

Clarity meets hardware where it already lives, rather than forcing everything through the same pipe. There are two distinct paths, and the platform speaks one consistent language regardless of which one a given device uses.

Majority of deployed readers

Mobile & handheld devices

The Clarity app runs directly on the device and communicates straight to the Clarity platform. No gateway sits in between. Today, most of our deployed readers operate this way.

Fixed infrastructure only

Fixed & infrastructure readers

These connect through Clarity Edge, our on-site edge computing gateway, which sits between the readers and the platform. This is specifically what makes fixed-reader hardware interchangeable.

What Clarity Edge does, for fixed infrastructure specifically

Translates every reader into one language. LLRP and vendor-specific protocols become a single, consistent data stream, so the platform never has to know what brand or model is on the wall.
Filters and de-duplicates reads at the source, so only clean, meaningful tag data travels upstream.
Keeps running through network interruptions, buffering reads locally and syncing once the connection returns.
Orchestrates multiple readers at a site from one place.
Why that matters

No lock-in on fixed hardware

Mix or swap reader brands without touching the platform. Edge absorbs the difference.

New hardware, no re-platforming

Supporting a new fixed reader means adding a translation in Edge, not rebuilding your system.

Resilient by design

Store and DC operations don’t stall just because the network hiccups.

Cleaner data, lighter load

The platform receives normalized, de-noised reads instead of raw, duplicate-heavy signal.

Either way, the data looks the same. Whether a read comes from a handheld talking directly to Clarity or a fixed reader passing through Edge, the platform receives standardized data. The device you pick never dictates how your data looks.

Certified today

What’s actually running in production right now.

This is real, currently deployed hardware, in stores and in the distribution center, not a partner-logo wall.

In stores

Handhelds & mobile computers

Zebra TC21 / TC22 / TC27 / TC51 / TC52 / TC15 / TC53e (RFID) Zebra RFID sleds: RFD40 / RFD90 / RFD8500 BlueBird EF400 sled / 901 sled Urovo DT610 (Lite) / RFG91 sled Other Android devices (Samsung A52-54, Honeywell EDA51-52, etc.)

Fixed readers

Zebra FX7500 / FX9500 Impinj Speedway / E-series Keonn PervasID Any LLRP-compliant fixed reader
At the DC & supply chain

Audit stations & tunnels

Clustag manual audit stations Clustag automated audit stations & MOT tunnels
In certification

In active validation now, not certified yet.

Certification is an ongoing process, not a one-time badge. These devices are currently in validation and will move to the certified list once they clear it.

Mobile devices

Urovo DT610 Urovo RFG91 sled Urovo DT610 Lite Zebra TC501 Zebra TC22R

Fixed readers

Transition readers
If you’re evaluating one of these devices now, ask us directly for a current status update.
Why certification exists at all

Being hardware agnostic doesn’t mean hardware quality doesn’t matter.

Being open to any LLRP reader is different from recommending any LLRP reader. Bad hardware still produces bad reads, and a bad read looks like a ClarityRFID problem even when it isn’t. So every certified partner actually gets tested, not just added to a list.

1

Real-environment testing

Hardware gets tested against actual store and DC conditions, not just a lab bench.

2

Protocol compliance verification

We confirm the reader’s LLRP implementation actually behaves the way the standard says it should.

3

Field validation with a real deployment

Before a reader earns certification, it runs in a live environment, not just a demo.

For hardware providers

Building RFID hardware? Get it certified with ClarityRFID.

If you make readers, handhelds, or DC audit hardware and want them certified for the retailers already running on ClarityRFID, we’d like to hear from you. Tell us about your hardware and we’ll walk you through what certification actually involves.

Start a hardware certification conversation