Where the budget is actually spent
When procurement teams evaluate proximity technology, the unit price of a beacon, NFC tag or QR code plaque is the most visible figure. It is also the least useful indicator of what the installation will actually cost to run. Total cost of ownership (TCO) captures every expense from initial deployment through to decommissioning, and for physical infrastructure embedded in real spaces, the ongoing costs almost always outweigh the upfront hardware spend.
Proximity systems differ from purely software purchases because they occupy physical locations. Beacons are mounted above head height, NFC tags are fixed to exhibits or shelves, and QR codes are printed on substrates that degrade. Each of these assets requires access, labour and coordination to install, maintain and eventually remove. A TCO framework forces you to account for these operational realities before committing to a technology choice.
The distinction between capital expenditure and operational expenditure matters for budgeting but can be misleading if taken in isolation. A beacon hardware purchase is capital; the twice-yearly battery replacement, the recalibration after a shop-fit, and the firmware update that requires out-of-hours access are operational. Over a three-year deployment, the operational line items typically represent the larger share of spend, yet they are the items most often omitted from initial business cases.
TCO also varies sharply by technology. A QR code printed on a laminated card has near-zero ongoing hardware cost but may require frequent physical replacement in high-traffic environments. An NFC tag is cheap to buy but costly to replace if it is embedded in a display case. A Bluetooth beacon carries a moderate hardware cost and a predictable but non-trivial battery replacement cycle. Understanding these profiles is essential before comparing supplier quotes.
Trade-offs that move cost or risk
Retail environments
In retail, store layouts change regularly. Promotional ends shift, fixture configurations are altered, and seasonal resets move product categories to different zones. Each change potentially affects beacon placement, NFC tag positions and the zone boundaries that trigger notifications. If the original deployment did not account for the labour cost of relocating and recalibrating devices after each reset, the operational budget will be understated.
High-traffic areas also accelerate physical wear. QR codes on floor stickers or low-level signage may need replacement every few months rather than annually. Beacons mounted in warehouse-style ceilings may require specialist access equipment each time a battery needs changing. These are not exceptional costs; they are structural features of the environment that should be built into the TCO model from the start.
Museums and heritage sites
Museum deployments tend to have longer planning horizons but introduce their own cost drivers. Exhibits rotate, temporary installations arrive and depart, and conservation requirements may restrict where devices can be mounted and how they are fixed. An NFC tag that must be attached with conservation-approved adhesive and removed without residue carries a higher per-unit installation cost than one stuck to a retail shelf.
Indoor navigation in museums also depends on accurate floor plans and zone definitions. When a gallery is rehung, the mapping data and zone triggers need updating. If this work requires the original integrator or a specialist, the cost per layout change is higher than if the in-house team can reconfigure zones through a management interface. Clarifying who performs updates and at what cost is a TCO question, not just a feature question.
Events and temporary venues
Event deployments invert the usual cost profile. Hardware procurement may be a rental charge rather than a purchase, but the labour intensity of installation and removal within tight turnaround windows is substantial. Beacons must be mounted, tested, monitored throughout the event and then collected, checked and re-packed. If the venue has limited power access or requires cable runs for gateways, the installation cost per beacon can exceed the hardware value.
Temporary infrastructure also has a higher risk of loss or damage. Devices attached to temporary staging, truss systems or pop-up structures are more likely to be mislaid during breakdown. A realistic TCO for events should include a depreciation or loss assumption, verified against the supplier's damage and replacement terms.
Battery replacement and firmware cycles
For beacon deployments, battery replacement is the most predictable recurring cost but one that is frequently underestimated. The advertised battery life assumes a fixed advertising interval and transmit power. If the deployment later requires a shorter interval for more responsive triggering, battery life decreases. If the operating temperature range in the actual installation is wider than the test conditions, battery life decreases again. A TCO model should use conservative assumptions based on the specific configuration, not the manufacturer's headline figure.
Firmware updates introduce a less visible cost. When a beacon firmware version is updated to address a security advisory or a Bluetooth specification change, each device must be updated. If the update requires physical proximity and the devices are distributed across a large site, the labour cost can be significant. Some beacon models support over-the-air firmware updates; others do not. This distinction has a direct impact on TCO but is easy to overlook during procurement.
A defensible estimate and review process
Treating hardware cost as project cost
The most common error in proximity technology procurement is equating the bill of materials with the total investment. A deployment of two hundred beacons might have a clear hardware line item, but the installation, calibration, integration testing, documentation, staff training, ongoing monitoring, battery replacements, zone recalibrations and eventual decommissioning collectively represent a larger and more sustained financial commitment. Business cases that present only the hardware figure risk under-resourcing the operational phase.
Ignoring access and logistics costs
Mounting a beacon on a ceiling tile at two metres is straightforward. Mounting one at eight metres in a venue with a steel roof deck, limited working hours and no permanent access equipment is a different proposition. The TCO impact of access requirements should be assessed during the site survey, not discovered during installation. Ask the integrator to include access methodology and equipment in their proposal, and verify whether out-of-hours working attracts premium labour rates.
Assuming zone definitions remain static
Proximity zones are defined against a specific physical layout. When that layout changes, the zones must be redefined and recalibrated. If the original contract does not specify who bears the cost of recalibration, or if the recalibration process requires specialist tools or access to the original integrator's platform, the ongoing cost may be higher than expected. Clarify the recalibration process, who can perform it and what it costs before signing.
Overlooking decommissioning
Every device that is installed must eventually be removed. In leased retail units, this may be a contractual obligation tied to the dilapidations schedule. In listed buildings, removal may need to satisfy conservation conditions. Decommissioning costs include labour, access equipment, disposal of batteries in accordance with waste regulations and restoration of surfaces. Including a decommissioning line item in the TCO model prevents an unexpected end-of-life cost.
Vendor lock-in on hardware or protocols
Some beacon ecosystems use proprietary packet formats or management platforms that only work with that manufacturer's hardware. If the supplier discontinues the product line, changes their pricing structure or fails to keep pace with Bluetooth specification updates, switching to an alternative requires replacing not just the hardware but potentially the management infrastructure as well. A TCO assessment should consider the cost of a hypothetical hardware migration and whether the chosen approach uses open standards that preserve flexibility.
Key questions for suppliers
- What is the expected battery life at the specific advertising interval and transmit power required by this deployment, rather than the maximum advertised figure?
- Does the firmware support over-the-air updates, and if so, what is the process and are there any per-device or per-update charges?
- What are the physical dimensions and mounting options, and do they impose any constraints on access equipment or installation method?
- What are the supplier's terms for hardware replacement under warranty, and what is the lead time for replacement units?
- Can zone definitions and trigger rules be modified by the in-house team, or does each change require a service call?
- What format does the asset data export use, and how easily could the configuration be migrated to an alternative platform if required?
- Are there ongoing platform licence fees, per-device fees or minimum commit levels beyond the initial contract period?
These questions do not replace a detailed cost breakdown, which is covered in the next guide in this series. They are, however, the checks that reveal whether a supplier's proposal accounts for the full lifecycle of the deployment or presents an incomplete picture that will generate unplanned costs later.
