Most RFID projects that disappoint were under-scoped, not under-engineered. The hardware is rarely the problem; the problem is that nobody pinned down how far tags had to read, what they would be stuck to, and how many there would be — before ordering. Get those three answers right and the rest of the project tends to follow. Get them wrong and you are buying twice. Here is how we scope an RFID deployment before quoting a single reader.
Start with the read range you actually need
“As far as possible” is not a specification. Range is a design constraint you set deliberately, because more range is not always better — sometimes you want a tag to read only when it is right in front of a counter, and a reader that throws a long beam will pick up the next aisle by mistake.
Work out, for each point where a read happens, how far the tag will be from the antenna:
- Centimetres — encoding benches, billing counters, single-item checks. Short-range desktop readers, deliberately limited.
- A metre or two — handheld audits, shelf scans, doorway taps.
- Several metres — dock portals, gate reads, conveyor lines.
- Tens of metres or more — yard and campus tracking, which is active RFID territory rather than passive UHF.
Defining the range per read point, not as one global number, is what lets us match the right reader and antenna to each location. Our RFID basics primer covers how range, frequency and tag type interact if you want the underlying logic.
Survey the environment honestly
The single most common cause of a failed pilot is metal and liquid. A plain UHF inlay stuck directly onto a steel rack or beside a water-filled container will read poorly or not at all — not because the hardware is faulty, but because the environment detunes the tag. This is entirely solvable, but only if you flag it during scoping.
Walk the site and note, for each tagged item:
- What is it made of, and what is it touching? Metal and liquid demand on-metal or speciality tags, not standard labels. Identium’s on-metal RFID tags are built for racking, machinery and tools.
- What are the conditions? Dust, humidity, washdowns, monsoon exposure and temperature all set the ingress protection and tag construction you need.
- What else is radiating nearby? Motors, other readers and dense metal can create reflections and dead spots that a site survey catches and a catalogue never will.
Treat this survey as non-negotiable. The cost of a half-day walkthrough is trivial against the cost of ordering thousands of the wrong tags.
Estimate quantities before you price anything
Volume drives both the bill of materials and the technology choice. A few hundred high-value assets and several hundred thousand cartons are entirely different projects even if the word “tracking” applies to both.
Pin down:
- How many items will carry a tag, and whether that number grows over time.
- How many read points — counters, doors, conveyors, audit zones — each needing reader and antenna hardware.
- Read frequency and volume — a portal seeing thousands of tags an hour has different reader and filtering needs than a desk doing a handful.
Quantity is also where the passive-versus-active decision gets made. Tagging hundreds of thousands of low-value items rules out battery-powered tags on cost alone; tagging a few high-value assets across a large area may justify them. Browse representative hardware and tags on our products hub to ground your estimate in real form factors and reader types.
Pilot in one zone, then scale
Even with range, environment and quantity defined, prove the design in a single representative zone before rolling out site-wide. A pilot surfaces the practical issues — tag placement, read reliability in real conditions, workflow fit — while the cost of changing course is still small. Scaling a proven zone is low-risk; scaling an unproven assumption across a whole site is how budgets get blown.
A scoping checklist
Before you ask anyone for a quote, have these in hand:
- Read range per read point, from centimetres to tens of metres.
- An environment survey noting metal, liquid, conditions and interference at each tagged item.
- Item and read-point counts, plus expected growth.
- The passive-versus-active call, driven by volume and value.
- A pilot zone chosen to be representative, not just convenient.
Bring those answers and a quotation can be precise rather than padded. Bring none of them and any quote is guesswork that you will pay to correct later.
Get a grounded recommendation
Scoping is exactly the conversation we like to have before recommending hardware — it is far cheaper for both sides than fixing a mis-specified order. Send us your read points, what you are tagging, the environment and rough quantities, and contact our team for a reader list, tag selection and quotation built around your actual site.