UHF passive RFID tags, readers, antennas and reconciliation software — engineered as one system that cuts counting time by up to 90% and keeps your register live.
RFID asset tracking replaces the annual clipboard hunt with radio. Each asset carries a UHF RFID tag with a unique identifier; fixed or handheld readers capture hundreds of tags per minute, without line of sight; and reconciliation software turns those reads into register movements — found, missing, moved — automatically. The result is not just a faster count but a different operating model: one in which the register stays accurate continuously rather than being rebuilt once a year.
CPCON is unusual in owning the whole stack. We have developed and refined our own RFID hardware configurations and reconciliation platform across thousands of inventory and asset projects worldwide over more than three decades, delivered by our own teams. That means your system is designed around your estate and your ERP — not around a single vendor’s product catalogue — and that we can be honest about where RFID earns its keep and where a simpler approach wins.
The technology is simpler than it sounds. A passive UHF tag has no battery. When it enters the field of a reader’s antenna, it harvests a little of the transmitted radio energy, powers up its tiny chip, and reflects a signal back carrying its unique identifier — a technique called backscatter. The reader decodes many of these replies every second and applies anti-collision so that hundreds of tags in the same field are read without talking over one another. Because the link is radio, not light, it needs no line of sight: tags are read inside cabinets, through packaging and several metres away.
Three things determine whether a system performs: the tag (and how it is matched to the asset surface), the antenna and reader power, and the environment (metal and liquids absorb and reflect UHF). Get those right and read rates are excellent; get the tag wrong on a metal asset and the same system fails. That is why tag engineering per asset class is the heart of our design work, not an afterthought.
| Component | Role |
|---|---|
| Passive UHF tags | Battery-free labels or on-metal tags carrying a unique EPC identifier, specified per asset class |
| Handheld readers | Mobile readers for audit and cycle-count teams — sweep a zone and capture every tag in range |
| Fixed readers & antennas | Portals at doorways and despatch bays for automatic, event-level movement tracking |
| Reconciliation software | Matches reads to register lines, resolves found / missing / moved, and exchanges clean data with the ERP |
We deploy passive UHF to the global EPC Gen2 / ISO 18000-63 standard, on the UHF band allocated for RFID in the UK and Europe (the 865–868 MHz range), using hardware certified for that band so the system is both legal to operate and interoperable across tags and readers. Each tag carries an EPC (Electronic Product Code) in its memory — the unique identifier that the reconciliation platform matches to a line in your register. Most tags also expose a small block of user memory in which we can encode an asset class or site code, useful as a cross-check when a tag is read in isolation.
“RFID” is often used loosely, so it is worth being precise about what we deploy for asset tracking and why. The workhorse for counting and verifying assets is passive UHF, because it is cheap per tag, battery-free and fast in bulk. Other radio technologies exist for different problems, and we use the comparison below to set expectations honestly rather than let a buzzword drive the design.
| Technology | Power & range | Best at |
|---|---|---|
| Passive UHF RFID | Battery-free; up to several metres | Bulk counting, verification and cycle counts of large asset and stock populations — our default |
| Active RFID | Battery-powered; tens of metres | A small number of very high-value assets needing continuous location; higher tag cost and maintenance |
| BLE beacons | Battery-powered; zone-level | Approximate real-time location within a building, where exact reads are not required |
| Barcode / QR | No radio; line of sight | Small, low-movement estates and human-readable identification |
| GPS | Battery-powered; outdoor | Vehicles and mobile plant moving between sites, not items within a building |
For the overwhelming majority of fixed-asset and stock estates, the right answer is passive UHF, sometimes combined with a handful of active tags or beacons for the few assets that genuinely need live location. Designing for the asset population — not the most impressive technology — is how the system stays affordable and actually gets used.
RFID is not one frequency but a family of them, and the band dictates range, read speed and what the technology is good for. The reason UHF dominates asset tracking is simple: it is the only band that combines metres of range with bulk, many-at-once reading. The table below places the bands in context.
| Band / frequency | Typical range | Read speed | Typical use |
|---|---|---|---|
| LF — 125–134 kHz | A few centimetres | Slow, one at a time | Animal ID, access fobs, immersed or very metallic items; not for bulk asset counting |
| HF / NFC — 13.56 MHz | Up to ~10 cm | One at a time | Smartphone tap, document and library tracking, single-item verification |
| UHF — 865–868 MHz (UK/EU) | Up to several metres | Hundreds per minute | Bulk asset and stock counting, cycle counts, portal movement — our default |
| Active / battery-assisted | Tens of metres | Continuous | A handful of very high-value assets needing live location; higher cost and maintenance |
Two practical points follow. First, the UHF band differs by region — the UK and Europe use 865–868 MHz, while North America uses a higher slice of spectrum — so hardware must be certified for the band it operates in; the equipment we deploy on UK estates is rated for 865–868 MHz, which is what keeps the system legal and interoperable. Second, the “typical range” figures are properties of the whole system, not the tag alone: the same tag reads farther with a higher-gain antenna and more reader power, and shorter against metal or liquid. That is precisely why we prove range and read rate in a site pilot rather than promising a single headline distance.
One of the first design decisions on any RFID programme is how much reading should be done by people carrying handhelds and how much by permanent infrastructure mounted in the building. The two are not rivals; they answer different questions, and the skill is in the blend.
Carried by audit and cycle-count teams, a handheld answers “what is in this zone right now?”. It is cheap to deploy, needs no installation, and goes wherever the assets are — ideal for periodic counts, verification sweeps and locating a specific tag with a directional “Geiger-counter” search mode. The trade-off is that it only reads when someone is pointing it.
Antennas mounted permanently at doorways, despatch bays, lift lobbies and store entrances read automatically, around the clock, with no operator. They answer “when did this asset move, and which way?”, capturing an event the moment a tag passes. They cost more to install and cable, so they are reserved for the thresholds where movement itself is the thing worth knowing.
In practice almost every estate uses both: handhelds for the broad, periodic counting of the whole population, and a small number of fixed portals at the choke points that matter — the goods-out door through which nothing should leave unrecorded, the boundary between a secure store and the floor, the despatch bay where returnable assets are shipped. Fixed readers can also drive simple physical controls — a light or alarm if a high-value tagged asset approaches an exit it should not — turning the portal from a passive logger into an active loss-prevention measure. We size the number and placement of fixed readers against your actual movement, loss and audit pressures, rather than wiring every doorway by default.
RFID is increasingly a component of a wider Internet-of-Things picture rather than a standalone counting tool. The connection works in two directions, and both rest on the same foundation — the tag is the asset’s identity, and the register is the system of record.
We deliberately keep this layered. The RFID and sensor infrastructure captures and attributes events; the reconciliation platform turns them into clean movements and exceptions; and your asset system remains the single record everyone reports from. That discipline is what stops an IoT deployment fragmenting into a dozen disconnected dashboards.
Because RFID is read by radio, at a distance and without line of sight, organisations reasonably ask what that means for security and privacy. For fixed-asset tracking the exposure is modest, but it is worth designing for deliberately rather than assuming it away.
The efficiency case is easiest to grasp as a before-and-after. Picture a distribution operation that had always counted its fixed assets and high-value stock wall-to-wall once a year. The exercise tied up several staff for the best part of a working week: aisles and mezzanines walked methodically, asset numbers read off labels and typed into a spreadsheet, racking and cabinets opened to find hidden items, and then days more spent reconciling the count against the register and chasing the discrepancies the manual process inevitably introduced. The whole thing was disruptive enough that it could only be faced annually — which meant the register was demonstrably accurate on exactly one day a year and drifted for the other 364.
With the estate RFID-tagged and the reconciliation platform in place, the same count changed shape entirely. One auditor walked each zone with a handheld held at a steady sweep, the screen filling with a live tally as hundreds of tags answered through boxes, racking and cabinet doors that previously had to be opened by hand. Areas that had taken a day were read in under an hour; the full site, once a multi-day operation, came down to a single shift. The reconciliation that used to take further days was near-instant, because the platform matched the captured EPCs to register lines automatically and presented only the genuine exceptions — found, missing and moved — for a person to judge.
The deeper change was not the one-off speed-up but what it made possible. Because a count now cost hours rather than days, the annual ordeal could be replaced with a rolling cycle count: high-value and mobile classes swept weekly or monthly, the rest on a sensible rotation, so the register was never more than a short cycle away from the truth. The year-end position stopped being a scramble and became a report — and the labour that used to be consumed by counting was freed for work that actually needed a person.
Barcodes are not obsolete — for small, stable estates they are often the right answer. The decision turns on volume, movement and how often you need to count. The table below is the comparison we walk clients through in the design phase.
| Factor | Barcode | UHF RFID |
|---|---|---|
| Line of sight | Required — each code must be seen | Not required — reads through cabinets, boxes, racking |
| Read speed | One item at a time | Hundreds of tags per minute |
| Read range | Centimetres, aimed at the code | Up to several metres, omnidirectional |
| Bulk counting | Manual, item by item | Whole zone in one sweep |
| Continuous / cycle counts | Rarely viable on labour cost | Routine and economical |
| Movement tracking | Manual scan events only | Automatic via fixed portals |
| Data on the tag | Limited (number / small payload) | Unique ID plus user memory |
| Cost per item | Lowest | Higher (tag + reader infrastructure) |
| Best for | Small, stable, low-movement estates | Large, high-volume or high-movement estates |
The headline advantages of RFID — no line of sight and bulk, many-at-once reading — are exactly what collapse counting time and make continuous counting affordable. Both technologies share the same foundation, though: durable tagging and a disciplined asset number. RFID is barcode tagging done with radio.
Walk-through inventories of whole floors in minutes; cycle counts become routine instead of an annual disruption.
Tag engineering per asset class — on-metal, label, rugged — is what separates working estates from failed pilots.
Reads reconciled to SAP, Oracle, Dynamics, Sage or your fixed asset system via API or file exchange.
The same infrastructure can drive stocktaking, WIP tracking, returnable-container and tool control.
Server, laptop and equipment fleets tracked through racks and stores; reconciled to the IT inventory and CMDB.
High-value mobile equipment located on demand and counted continuously across wards, theatres and departments.
Tooling, jigs, moulds and work-in-progress tracked across the plant, with portals controlling movement off site.
Returnable containers, plant hire and despatch tracked through fixed portals as they move.
The same tags support two operating models, and most estates blend them:
The art is proportion: handhelds everywhere, fixed portals only where the value of real-time movement data outweighs the cost. We size that balance in the design phase against your actual loss, movement and audit pressures.
It helps to picture the day-to-day reality rather than the technology. Take a floor of an office or a bay of a warehouse that previously took a two-person team most of a day to count by reading and typing asset numbers from a clipboard. With a tagged estate and a handheld reader, one person walks the zone holding the reader at a comfortable sweep, the screen filling with a live tally as tags answer. A floor that took a day is read in well under an hour.
When the sweep is done, the handheld holds a list of every EPC it saw. The reconciliation platform compares that list to the register lines expected in that location and resolves three outcomes automatically:
Because the cost of a count has collapsed, the once-a-year event becomes a routine. High-value and mobile classes can be swept weekly or monthly as a rolling cycle count, so the register is never more than a short cycle away from the truth, and the year-end position is a report rather than a scramble.
The thing that turns RFID from a gadget into an asset-control system is the software layer that sits between the readers and your ERP. Raw reads are noisy — the same tag is seen dozens of times in a sweep, tags from the next zone occasionally intrude, and a fixed portal sees an asset every time anyone walks it through a doorway. Our reconciliation platform turns that noise into clean, attributed events.
| Stage | What the software does |
|---|---|
| Capture | Readers stream EPCs with timestamp, location and signal strength |
| De-duplicate & filter | Collapse repeated reads of the same tag; drop weak stray reads from adjacent zones |
| Resolve | Match each EPC to a register line and classify it found / missing / moved |
| Reconcile | Produce exception schedules finance and operations can act on, with the evidence behind each |
| Exchange | Send clean movements and verification updates to SAP, Oracle, Dynamics, Sage or the asset system via API or file |
Crucially, your ERP stays the system of record. The RFID layer does not become a second, competing database of asset truth; it feeds the one you already run, which is what keeps finance, audit and operations working from a single set of numbers.
Well-designed UHF estates routinely read 99%+ of the tags that are present. The gap that stops an estate reaching 100% is almost never the radio — it is governance. New assets arrive and are put into use before anyone tags them; assets are disposed of without the paperwork; items move between sites with no transfer record. RFID reads what is tagged and recorded; it cannot read an addition nobody tagged or know about a disposal nobody logged.
That is why we never sell RFID hardware in isolation. A rollout is paired with a baseline verification and register clean-up so the system starts from truth, and with simple operating procedures — tag-on-receipt, log-on-disposal, record-on-transfer — so it stays there. The technology removes the cost of counting; the governance removes the cause of error. You need both.
A surprising number of RFID projects stall at the pilot, and the reasons are consistent. We design around them deliberately:
We would rather you knew the constraints than discovered them after rollout:
The dominant return is labour. A wall-to-wall count that consumed team-days or team-weeks becomes a walk-through of hours, repeatable as often as you need it — which is what makes continuous accuracy affordable. On top of that sit reduced loss and shrinkage, fewer duplicate purchases of assets that were simply lost on paper, lower over-insurance once values are based on what genuinely exists, and faster, cheaper external audits because every figure is backed by a recent, scan-based count. The investment is the tags, readers and rollout; the payback is the gap between an annual disruption and a register that stays right.
“Better visibility” is not measurable; read accuracy and count time are. Whether you run the system in-house or take it as a managed service, we hold the programme to figures you can see:
As a managed service, those measures sit behind an SLA, so accuracy is a commitment with evidence, not a hope.
The same readers, tags and software that track fixed assets also count stock, work-in-progress, tools and returnable containers — the radio does not care whether an item is capitalised or held for sale. That means a single RFID investment can serve both finance and operations: a fixed asset verification one week, a wall-to-wall stock count the next, tool control in the workshop in between. Designing the system with both jobs in mind from the start is usually cheaper than buying twice, and it concentrates the counting skill and the data in one place.
RFID is a means, not the end: the end is a fixed asset register and stock records that stay accurate between audits — supporting FRS 102 reporting, statutory stocktaking records, the IT asset inventory your security assessments sample, and insurance values you can defend in a fixed asset verification. If a simpler barcode regime fits your estate better, we will tell you so in the design phase rather than sell you radio you do not need.
Organisations weighing an RFID programme usually ask the same practical questions. The honest answers shape a realistic plan:
The common thread is proportion. RFID is powerful where volume, movement and count frequency make it pay, and unnecessary where they do not — and a good design is the one that draws that line correctly for your estate.
Our own hardware configurations and reconciliation platform, refined across thousands of projects worldwide for more than 30 years.
Read accuracy is won or lost on tag choice and placement — the part most pilots get wrong, and the part we prove before rollout.
Reads are reconciled to register lines so your system of record receives movements, not raw tag noise.
We recommend barcode over RFID where it genuinely fits better — the system has to earn its cost on your estate.
A barcode must be found, exposed and scanned one item at a time with line of sight. UHF RFID tags are read by radio — hundreds per minute, through cabinets and packaging, several metres from the reader. In practice that turns a two-week wall-to-wall count into a walk-through of a few hours, and makes continuous (cycle) counting economically viable.
A passive UHF tag has no battery. The reader’s antenna transmits radio energy in the UHF band; the tag harvests a little of that energy, powers up its chip and reflects back a signal carrying its unique identifier (a technique called backscatter). The reader decodes many such replies per second, applying anti-collision so that hundreds of tags in the field are read without interfering with each other. Range is typically a few metres and needs no line of sight.
We use passive UHF RFID to the global EPC Gen2 / ISO 18000-63 air-interface standard, on the UHF band allocated for RFID in the UK and Europe (the 865–868 MHz range). Hardware certified for this band is what we deploy for UK estates, so the system is legal to operate and interoperable across readers and tags.
Yes, with the right hardware. Standard RFID labels detune on metal surfaces, so plant, racking and servers use specialised on-metal tags with a spacer or foam backing. Tag selection per asset class is part of our design phase — it is the single biggest factor in read accuracy.
Passive UHF typically reads from tens of centimetres up to several metres depending on tag, antenna, reader power and environment, with hundreds of tags read per minute by a handheld and far more through a fixed portal. Range and rate are properties of the whole system — tag, antenna, power and surroundings — which is why we prove them in a site pilot rather than quoting a single headline number.
Both models run on the same tags. Handheld readers give fast periodic and cycle counts for the bulk of an estate. Fixed portals at doorways, despatch bays and key thresholds give event-level, near-real-time movement tracking for high-value or high-risk assets. Most estates use a blend: handhelds everywhere, fixed readers where knowing the moment an asset moves justifies the cost.
Yes. CPCON’s reconciliation platform exchanges data with SAP, Oracle, Microsoft Dynamics, Sage and most fixed asset systems via file or API. Reads are matched to register lines so your ERP remains the system of record and receives clean movements, not raw tag noise.
Well-designed UHF RFID estates routinely achieve 99%+ read accuracy on tagged assets. The remaining gap is governance, not radio: untagged additions and undocumented disposals — which is why we pair RFID rollouts with verification and a register clean-up.
RFID is not magic. Metal and liquids absorb and reflect UHF, so tag choice and placement matter; very dense stacks can shadow inner tags; and stray reads from an adjacent zone must be managed with antenna design and read filtering. It also costs more per tag and per reader than barcodes, so for small, low-movement estates a barcode regime can be the better economic choice. We will say so in the design phase rather than over-specifying.
The main return is labour: counts that took teams days or weeks become a walk-through of hours, repeatable as often as you like. Add reduced loss and shrinkage, fewer duplicate purchases, lower over-insurance from accurate values, and faster, cheaper audits. The investment is in tags, readers and the rollout; the payback is the difference between an annual disruption and a register that simply stays accurate.
Most estates use both, for different jobs. Handheld readers are portable and cheap to deploy: an auditor sweeps a zone and captures every tag in range, which is ideal for periodic and cycle counts across the bulk of an estate. Fixed readers and antennas are mounted permanently at doorways, despatch bays and other thresholds and read automatically, without anyone present — which is what you need for event-level movement tracking of high-value or high-risk assets, where knowing the moment something passes a portal justifies the infrastructure. The usual design is handhelds everywhere plus fixed portals only at the few choke points where real-time movement data earns its cost.
Yes. The RFID identity is often the anchor that other data attaches to. A fixed-reader event (asset X passed portal Y at time Z) is itself an IoT event stream that can drive dashboards, alerts and analytics. Beyond identity, sensor-enabled and battery-assisted tags can carry temperature, shock or tamper data, and the RFID read links a sensor reading to a specific, register-matched asset. We keep the asset register as the system of record and let the RFID and sensor layer feed it clean, attributed events, rather than creating a second competing database.
For fixed-asset tracking the risk is low but worth managing deliberately. A passive UHF tag normally holds only an opaque identifier — not asset descriptions, values or personal data — so a stray read reveals little. Where it matters, EPC Gen2 supports access and kill passwords, and memory can be locked or permanently disabled, so tags cannot be trivially rewritten or cloned, and tags on assets leaving your control can be killed. We also recommend not encoding sensitive meaning into the tag itself: the identifier means nothing without your register, which stays behind your own access controls. The privacy questions that attach to tagging people or consumer goods generally do not apply to plant, IT and equipment, but we design to the principle of least data on the tag regardless.
Tell us your asset classes, sites and how often you need to count. CPCON proves read rates in a pilot before any rollout — and responds within one business day.
Request a Proposal