Scope, constraints and responsible roles
Asset tracking with Bluetooth beacons does not work the way marketing diagrams often suggest. A beacon does not report its own location. It simply broadcasts a radio packet at a set interval, containing identifiers such as a UUID, major and minor values. Something else—a fixed gateway, a handheld scanner, or a mobile device running an app—must detect that signal and interpret it. The tracking system is really the combination of the beacon, the receiver infrastructure, and the software that ties a beacon identifier to a specific asset record.
There are two broad operating models. In the first, fixed gateways mounted on walls or ceilings listen for beacon broadcasts and report which identifiers they can hear, along with an RSSI value. A backend system then estimates where each asset is based on which gateways detected it and at what signal strength. In the second model, staff carry a mobile device and walk past assets, scanning for beacons at close range to confirm that a tagged item is present in a particular bay, room or shelf. The first model gives you periodic, semi-automated location updates. The second gives you on-demand presence confirmation with far less infrastructure.
RSSI-based distance estimation is not the same as positioning. In a controlled open space with a calibrated beacon and a clear line of sight, you might distinguish between "within a metre" and "roughly five metres away." In a warehouse with metal racking, forklifts and stacked pallets, the same beacon will produce erratic readings. Any claim of sub-metre accuracy should be treated with scepticism unless the supplier can demonstrate it in an environment that closely matches yours, with measured data to back it up.
It is also important to separate asset tracking from indoor navigation. Both use beacons, but navigation requires continuous, smooth position updates as a person walks, and the user experience degrades quickly if updates lag or jump. Asset tracking can tolerate longer intervals and coarser granularity because you are locating a pallet or a piece of equipment, not guiding a visitor to a specific exhibit. The hardware may be similar, but the placement strategy, gateway density and calibration tolerances are different.
Build and test the working approach
Warehouses and logistics
The most common application is tracking rolling stock—pallets, cages, trolleys and fork-lift trucks—across a large indoor space. Beacons are attached to each asset, gateways are installed at key points such as loading bays, staging areas and aisle intersections, and the system logs which zone each asset was last seen in. This is zone-level tracking rather than pinpoint location, but for many operations that is sufficient: knowing that a specific cage is in Bay 14 rather than somewhere on the site is the information that actually changes workflow.
Museums and venues
Exhibits, AV equipment, display cases and movable seating can all be tagged. In a museum context, the priority is often knowing whether an item is in storage, on display, or in transit. A handheld scan at the start and end of a gallery rotation replaces manual checklist checks. For touring exhibitions, beacons attached to crates allow receiving venues to confirm that all components have arrived without opening every case.
Healthcare environments
Hospitals track infusion pumps, patient hoists, wheelchairs and portable monitoring equipment. The operational problem is not usually complex routing but simple availability: staff spend considerable time searching for equipment that has been left in a corridor or moved to a different ward. Zone-level beacon tracking, with gateways at ward entrances and key corridors, can reduce that search time significantly. However, healthcare environments introduce strict requirements around RF coexistence with medical devices, infection control for beacon housings, and patient privacy when beacons are attached to beds or trolleys that could identify individuals.
Form factor and attachment
Beacon selection for asset tracking is largely a physical problem. The beacon must survive the environment—dust, moisture, temperature swings, cleaning chemicals, impacts from handling or vehicles. It must attach securely: adhesive backing is adequate for a museum display case, but a forklift truck needs a bolted or riveted enclosure with a tamper-evident seal. The beacon should be positioned so that its antenna is not shielded by the asset itself or the surface it sits against. A beacon flat against a metal pallet will have a very different broadcast pattern from one mounted on a plastic bracket with an air gap.
Gateway infrastructure
Gateway placement determines what you can reliably detect. A single gateway in the centre of a 400-square-metre room will hear every beacon in that room, but it will not tell you which end of the room a beacon is in. Adding gateways at opposite ends creates overlapping detection zones and allows the system to infer rough position from relative signal strengths. Power and network connectivity for gateways are practical constraints: PoE is preferable to battery-powered gateways in fixed installations, and Wi-Fi backhaul must be reliable in areas where metal racking can cause dead spots.
Acceptance, records and review triggers
Assuming beacons give coordinates
The most frequent mistake is treating RSSI as a distance measurement and expecting the system to return x-y coordinates for each asset. BLE beacons do not provide coordinates. They provide a signal that a receiver can use to estimate proximity, and that estimate is affected by orientation, obstructions, interference and device-to-device variation. If your operational requirement is "which zone is this asset in," beacons can deliver that. If you need "this asset is at position 3.2 metres by 7.8 metres," you need a different technology or a much more complex multi-sensor setup.
Ignoring RF environment during planning
Metal racking, liquid storage, concrete walls and stacked goods all attenuate and reflect Bluetooth signals. A beacon that reads at -60 dBm in an empty room may read at -85 dBm when surrounded by stock. If you plan gateway placement and detection thresholds based on office testing, the system will miss assets or report them in the wrong zone once deployed. A site survey with test beacons placed on representative assets, in representative positions, is not optional—it is the minimum preparation before committing to hardware quantities.
Poor attachment and beacon loss
Beacons fall off. Adhesive fails in cold stores. Cables catch on beacons and snap them from brackets. Staff remove beacons to clean equipment and do not replace them. Over time, your asset register drifts from reality unless you have a process for physically verifying that beacons are still attached and still broadcasting. A periodic scan with a handheld device, cross-referenced against the asset register, is the practical safeguard.
Battery management gaps
Asset-tracking beacons often run at lower advertising intervals than proximity-marketing beacons, which extends battery life but does not eliminate the replacement problem. Batteries deplete at different rates depending on temperature, transmit power setting and manufacturing variation. If you have 500 beacons with an estimated two-year battery life, some will fail at 14 months and others will last 28 months. Without a monitoring system that flags beacons which have stopped broadcasting, or a scheduled replacement cycle with a comfortable margin, you will discover dead beacons only when an asset goes missing from the system.
Privacy when assets are associated with people
If a beacon is attached to a hospital bed, a wheelchair or a staff badge, the location data can reveal information about individuals. Under UK data protection law, if you can reasonably identify a person from the asset location—such as a patient in a specific bed space—that data is personal data and subject to the usual requirements for lawful basis, transparency, data minimisation and retention limits. The technical system does not change, but your governance, access controls and retention policies must account for this.
Key checks before committing
- Have you tested beacon detection in the actual environment, with assets in their normal positions, rather than in an empty space?
- Does your required granularity match what the technology can reliably deliver—zone-level presence rather than precise coordinates?
- Have you confirmed that gateway power and network connectivity are available at every planned mounting point?
- Is the beacon housing rated for the environmental conditions it will face?
- Is the attachment method appropriate for the asset type and the handling it will receive?
- Do you have a process for reconciling the beacon inventory with the asset register at regular intervals?
- Have you defined a battery replacement cycle and a method for detecting beacons that fail early?
- If asset locations could identify individuals, have you assessed the privacy implications and documented your lawful basis?
Beacons for asset tracking are a mature, workable technology when applied to the right problem with realistic expectations. The failures come not from the hardware but from treating RSSI as a precise measurement, skipping the site survey, or neglecting the ongoing operational tasks that keep the system accurate over time.
