Choosing an independent RFID consultant: what to checkYour RFID consultant may be tied to a supplier.
What to demand from an RFID consultant before you hire one: the deliverables, a one-question independence test, and where passive RAIN (UHF) projects succeed or fail. For our own service, see RFID consulting.
Where RFID projects succeed or fail
With passive RAIN RFID, most of the success is in the unglamorous detail: choosing the right inlay for your product and packaging, surviving liquids and metal, engineering read zones at portals, and deduplicating reads before they hit your systems.
Brand of reader matters far less than tag-on-material testing.
What an RFID consultant does
- Use-case validation: where item-level identity actually pays back
- Tag/inlay selection and on-material read testing before you standardise
- Portal, handheld and fixed read-point design and site survey
- Middleware and integration into WMS/ERP so data is clean and usable
- independent hardware selection (readers, antennas, printers, labels)
Independent, not a reseller
We don't sell hardware, so our advice stays independent. That means we’ll tell you when cheap fixed infrastructure beats expensive equipment, and when handhelds are all you need.
What good RFID consulting looks like when locating and identity are the goal
An RFID consultant should reduce the chance you buy the wrong layer of locating technology, portals where you needed continuous RTLS, or dense active tags where a passive RFID gate event would have paid back faster. Independence matters: if the advisor earns a cut on readers and tags, their “recommendation” is structurally a catalogue.
Scope an RFID engagement around outcomes. Typical work includes process mapping of custody and identity events; RF and portal design; tag selection (commodity, on-metal, liquid, reusable); pilot design with read-rate and exception KPIs; WMS/ERP event integration; and a rollout plan that separates hardware, install labour and change management. The output should be a specification your procurement team can tender, not a single-supplier BOM presented as destiny.
Where projects succeed. Clear definition of which questions are gate events vs continuous location; tag trials on the real product mix; commissioning under peak inbound; exception processes for non-reads; and ownership inside operations, not only IT. Where they fail: datasheet antenna layouts, no shielding between docks, no baseline inventory accuracy, and dashboards nobody opens.
Ask consultants for evidence, not adjectives. Request anonymised before/after read rates, how they handle metal/liquid SKUs, how they design for adjacent-door isolation, and whether they will stand behind go/no-go criteria on a production-load pilot. Ask how they decide between passive RFID, BLE and UWB when the brief says “track everything”. A competent advisor will narrow the locating question before naming a radio.
Commercial hygiene. Prefer discovery and design phases priced in writing up front; keep advisory fees separate from any hardware supply; require open standards (EPC Gen2 / ISO 18000-63, GS1 event semantics) and exportable data. Bring the consultant in before the RFP is locked to a single architecture. After supplier selection, they can only decorate a decision already made.
RFP and pilot support an RFID consultant should own
Beyond design, a strong RFID consultant helps write RFP language: read-rate definitions, adjacent-door isolation, tag trial requirements, WMS event SLAs, and install acceptance under live load. They should moderate supplier BAFO rounds with a scored matrix.
During pilot, they observe operations at peak, not only commissioning day; they quantify exception rates; and they recommend SOP changes when non-reads are process issues rather than antenna issues. After go-live, a light assurance pass catches cross-reads and label-process drift before inventory KPIs slip.
If your brief mixes item-level passive RFID with RTLS, the consultant must be competent across both (or partner accordingly), so you do not get a portal specialist forcing every problem into a dock door.
Deliverables checklist for an RFID locating advisory
Expect: process maps of custody events; RF/portal design pack; tag matrix with trial results; pilot plan with read-rate and exception KPIs; integration sketch to WMS/ERP; tenderable BOM and install SoW; and a risk register covering metal/liquid SKUs and adjacent-door isolation. If a consultant cannot produce those artefacts, you are buying conversation, not locating design.
Use the same checklist when comparing consultancies. The firm that shows anonymised portal read-rate uplifts and hybrid RFID+RTLS decisions will usually outperform the firm that only lists reader brands they prefer.
Independence test in one question
Ask any RFID advisor: “When would you tell us not to buy passive RFID, and to use BLE or UWB instead?” An independent answer cites gate-versus-continuous decisions and TCO. A reseller answer steers every problem back to their catalogue. Use that question in the first meeting.
Field note
Bring the consultant in before the RFP freezes architecture, after award they can only remediate.
Frequently asked questions
Passive RFID or RTLS: which do I need?
RFID gives item-level identity at known read points (doors, conveyors). RTLS gives continuous position. Many operations use both. See our Passive RFID vs RTLS guide.
Why do RFID pilots fail at scale?
Usually tag selection and read-zone engineering that worked in a clean pilot corner but not in production. A site survey and tag-on-material testing before rollout prevents it.
Do you cover retail item-level RFID?
Yes, source-tagging, inventory accuracy, BOPIS and loss prevention from the DC to the shop floor.
What does it cost?
Tags are cents; the cost is in readers, antennas, install and integration. We size the full system plainly. See our RTLS/RFID cost guide.
Related: choosing a locating technology, the independent technology comparisons, and industrial RFID strategy.
Last updated:
Advisory note
This guide is written for operators selecting and deploying location technology, not for selling a radio. Use it to frame questions for suppliers and integrators. Bring TRACIO in when you want those answers scored independently against your site.