Budget boundaries and commercial assumptions
When procurement discussions focus on hardware unit prices and initial installation, the recurring cost of keeping a proximity system running often receives only a passing mention. Yet for most deployments, the cumulative spend on support and maintenance over three to five years will exceed the original hardware outlay. Understanding what those costs actually cover—and what they deliberately exclude—is the first practical step towards a realistic budget.
Ongoing costs in this context refer to the labour, logistics and contracted services required to keep physical proximity infrastructure functioning as intended after go-live. This includes battery replacement cycles, firmware management, recalibration after environmental changes, physical repair or replacement of damaged units, and the operational overhead of monitoring system health. It does not cover software licensing, CMS fees or analytics platform charges, which sit in a separate cost category.
Support contracts from integrators or manufacturers typically fall into tiers. A basic tier may cover firmware updates and remote monitoring alerts. A mid-tier often adds scheduled on-site visits for battery swaps and recalibration. A comprehensive tier might include same-day hardware replacement, environmental re-surveys when floor plans change and dedicated contact for troubleshooting. The gap between what a tier promises on paper and what it delivers in practice is where most budget surprises originate.
It is also worth distinguishing between contracted support and internal operational costs. Even with a full-service maintenance agreement, your own staff will spend time coordinating access, checking that replaced units are correctly configured, reviewing monitoring dashboards and escalating issues. That internal effort has a real cost, even if it never appears on an invoice.
Compare options on a common cost basis
Retail environments
High-footfall retail spaces impose predictable wear on proximity hardware. Beacons mounted at low height on shelving or fixture ends will be bumped, knocked or occasionally removed by customers. NFC tags on product displays may be peeled off or scratched to the point of unreadability. QR codes printed on signage will fade under shop lighting or suffer from wear. A maintenance plan for retail needs to account for a steady attrition rate rather than assuming hardware remains intact. Battery replacement in retail is comparatively straightforward if beacons are accessible, but coordinating swaps during trading hours without disrupting customers adds logistical cost that pure per-unit battery pricing does not capture.
Museums and heritage venues
Museum deployments often involve beacons mounted in ceiling voids, behind display cases or in architectural features where access requires step ladders, specialist equipment or coordination with conservation staff. A battery swap that takes two minutes in a retail aisle can take twenty minutes in a gallery, and that time multiplier directly affects maintenance cost. Museums also frequently reconfigure exhibitions, which means beacons may need to be physically relocated, re-registered in the asset inventory and recalibrated for new positions. If the maintenance contract prices by the site visit rather than by the unit, exhibition changeovers can become unexpectedly expensive.
Events and temporary installations
For events, the ongoing support model looks fundamentally different. There is no multi-year maintenance cycle; instead, costs concentrate in the pre-event testing phase, on-site standby support during the event and post-event decommissioning. The relevant question is not what annual support costs but what level of on-site technical presence is required to handle beacon failures, interference from other event equipment or last-minute zone reconfiguration. Contracts that assume a static environment will not serve events well.
Indoor navigation systems
Navigation deployments carry a specific maintenance burden: the floor plan and zone data must stay synchronised with the physical space. When a venue adds a partition, closes a corridor or renumbers rooms, the navigation map and the underlying beacon or Wi-Fi positioning data need updating. This is not a hardware maintenance task in the traditional sense, but it is an ongoing operational cost that must be budgeted for. If this work falls outside the support contract, it will either be charged per change request or absorbed by internal staff who may lack the technical familiarity to complete it reliably.
Evidence required before scaling
Assuming battery life claims translate directly to replacement intervals
Manufacturer battery life figures are typically stated at a specific advertising interval and transmit power, measured at room temperature. In practice, beacons deployed in cold storage areas, near heat sources or at higher transmit power to overcome interference will drain faster. A claimed two-year battery life might become fourteen months in a demanding environment. The maintenance budget should be built around measured drain rates from your own pilot, not the datasheet maximum.
Not defining response times in the contract
A support agreement that promises "hardware replacement" without specifying a response window is of limited operational value. If a beacon in a critical navigation zone fails on a Saturday morning and replacement arrives the following Thursday, the system has been degraded for five days. Check whether response times differ by severity level, whether they apply during weekends and event periods, and whether there are geographic or travel surcharges for on-site visits to your location.
Overlooking firmware update logistics
Firmware updates for beacons generally require physical proximity or a gateway device, depending on the manufacturer's approach. If your deployment uses several hundred beacons and firmware updates are issued twice a year, the labour cost of applying those updates across the estate is material. Some platforms support over-the-air firmware updates via gateways; others require a technician with a mobile app walking the site. Clarify the update mechanism before assuming it is trivial.
Failing to account for inventory drift
Over time, beacons are swapped, relocated or replaced without consistent documentation. The asset register gradually diverges from the physical reality on site, making troubleshooting slower and battery replacement less efficient. A useful support arrangement should include periodic inventory reconciliation—physically verifying that the registered location, firmware version and battery status of each unit match the record. If this is not included, budget internal time for it.
Key questions to put to a support provider
- What exactly is included in each support tier, and what is explicitly excluded?
- Are battery replacements priced per unit, per site visit or as a fixed annual allowance?
- How are firmware updates applied, and who is responsible for scheduling and verifying them?
- What are the defined response times for different severity levels, and do they cover your operating hours?
- Does the contract cover recalibration if the physical environment changes?
- Is inventory reconciliation included, and if so, how frequently?
- What happens to the support terms if the hardware manufacturer discontinues your beacon model?
- Are there caps on the number of change requests or on-site visits per year?
The practical test of a support proposal is not whether it looks comprehensive on a comparison table, but whether you can trace a realistic failure scenario through it and arrive at a clear, costed resolution path. If you cannot, the gaps will become apparent once the system is live and the initial project team has moved on.
