The three reader classes, with real numbers
These are published list prices from a large international RFID retailer (AtlasRFIDStore, September 2026) for Zebra, the most widely deployed tier-one brand. They are not our quote — they are the reference frame a buyer should walk in with. Rand figures use an indicative R16.20/USD and exclude shipping, duties and VAT; landed South African pricing runs higher.
| Class | Example (Zebra) | Intl. list | Indicative ZAR |
|---|---|---|---|
| Handheld sled (clips to a phone/scanner) | RFD40 Standard → Premium Plus | $989 – $1,717 | ~R16,000 – R28,000 |
| Integrated handheld (Android terminal, reader built in) | MC3330xR / long-range MC3390xR | $3,414 – $4,174 | ~R55,000 – R68,000 |
| Fixed reader, 2-port | FX7500-2 | $1,158 | ~R18,800 |
| Fixed reader, 4-port | FX9600-4 | $1,274 | ~R20,600 |
| Fixed reader, 8-port | FX9600-8 | $2,080 | ~R33,700 |
Two qualifications. First, a strong value tier exists — Chainway, Urovo and similar manufacturers ship EPC Gen2 readers with credible performance at a meaningful discount to the tier-one brands, and for many South African projects they are the sensible choice; their local pricing is quote-only everywhere, which is exactly the opacity this article exists to reduce. Second, the reader is not the read point. That is the next section, and it is where most budgets go wrong.
A fixed read point costs the reader — twice
A fixed reader ships as a box with antenna ports. To read anything it needs, per port in use: an antenna (indoor patch or IP-rated outdoor), low-loss coaxial cable — kept short, because every metre of coax eats transmit power — a mounting bracket or pole, and usually PoE or a power run to wherever the gate is. Then somebody has to configure transmit power, session and population settings so the lane reads trailers reliably at 5–8 m without also reading the truck parked in the next lane.
A worked example, because this is the configuration South African yards actually ask us for: a bidirectional vehicle gate — one lane, traffic both ways, and the system must know which way each vehicle went. That is typically a 4-port fixed reader driving four outdoor antennas (two per direction, staggered so read order gives you direction), rugged on-metal tags on the vehicles or trailers, cabling, mounting and weather protection. Price the reader alone and you have budgeted roughly half the hardware — before installation and before the software that turns raw tag reads into "trailer 214 left at 14:32".
Handheld or fixed is not a price question
The cheaper class is not the entry-level version of the dearer one; they answer different questions. A handheld answers "what is here right now?" — stocktakes, audits, finding a specific asset in a storeroom. A fixed read point answers "what passed this spot, and when?" — gates, dock doors, dispatch lanes, conveyor exits. A stocktake problem solved with fixed portals is over-engineered; a gate-automation problem solved with a handheld means an employee standing at the gate all day, which is the process you were trying to eliminate. Most real deployments start with one fixed choke point and one handheld, and that pairing covers a surprising share of the value.
The spec buyers forget: who owns the data path
Every serious reader exposes an SDK or a standard interface (LLRP, MQTT, REST on the newer generation). Whether you get to use it is a procurement decision, not a technical one. Some turnkey offers in the South African market couple the hardware to the vendor's own software platform, and the reader's event stream is only accessible through it. If you ever want the gate events inside your own rental, ERP or yard system, write it into the requirement now: unrestricted access to the reader's SDK/API and raw event data, in writing, before you sign. We take the opposite approach on principle — we integrate readers into the system you already run, hand over the API documentation, and treat the event stream as your property; an integrator who is confident in the engineering does not need a lock-in to keep the client.
What drives your total (in the order that surprises people)
- Read-point civils and installation. Outdoor gates need poles, conduit, weatherproofing and sometimes trenching for power. On a greenfield yard this is routine; retrofitting a busy gate without stopping traffic is engineering.
- Antennas and RF design. Four good outdoor antennas can rival the reader's own price. Lane isolation — reading your lane and not the next — is design work, not a checkbox.
- Tags, chosen by surface. Steel trailers need rugged on-metal tags, mechanically fixed. Our tag-selection guide covers why the wrong tag on metal simply does not read.
- Integration. Turning reads into business events in the software you already use. This is where a project earns its keep, and where a locked platform quietly converts your capital purchase into a subscription.
- The reader itself. Genuinely the easiest line to price — as the table above shows, the numbers are public everywhere except here.
How we quote it: readers, antennas and tags are inside our scope — we specify the class your problem needs, source tier-one or value-tier hardware to your budget, and quote the read point as a working whole: hardware, installation, configuration and integration into your existing system, with the SDK and event data documented and handed over. If a handheld solves it, we will say so and quote the smaller number.