Buying proximity technology is not a simple matter of selecting a beacon model and placing an order. The hardware is only one element in a system that also demands installation, calibration, software, ongoing maintenance and a clear understanding of how the devices will behave in your specific environment. This guide covers what operational managers, venue teams and IoT leads need to consider when procuring beacons, NFC tags, QR infrastructure and the supporting components of a proximity deployment.
Proximity Technology Procurement Checklist
Before approaching suppliers, work through the following points internally. Skipping any of these tends to cause delays or mismatched expectations later in the project.
- Defined use case: State precisely what the technology must do — trigger a notification, track a zone entry, provide wayfinding, or deliver exhibit information. Different use cases place different demands on accuracy, battery life and update frequency.
- Environment mapped: Document the physical space, including wall materials, ceiling heights, metal fixtures, footfall density and temperature ranges. These factors directly affect signal behaviour and hardware selection.
- Receiver requirements clarified: Determine whether visitors will use a native app, a web app, or a mix. This dictates which beacon protocols and standards you can rely on.
- Power and mounting constraints: Identify where devices can physically be placed, whether mains power is available for gateways, and what mounting methods your building or lease permits.
- Privacy obligations reviewed: Confirm what consent mechanisms you need, what data you will collect, and how long you will retain it, in line with current UK GDPR guidance.
- Budget split agreed: Separate the budget into hardware, installation, software, first-year running costs and a contingency for rework.
- Success criteria documented: Write down what a successful deployment looks like in measurable terms before you buy anything.
Evaluating Beacon Hardware Suppliers
Hardware suppliers vary considerably in what they provide beyond the physical device. When comparing options, focus on the factors that affect day-to-day operations rather than just the advertised transmit range.
Firmware and update mechanisms. Check whether the beacon firmware can be updated over-the-air, what tools are required, and whether updates can be applied to devices already installed at height. Beacons that require physical collection for every firmware update become expensive to maintain at scale.
Configuration options. Determine whether you can adjust advertising interval, transmit power and UUID structure per device or per batch. Some locked-down devices are cheaper but prevent the fine-tuning needed for accurate zone definitions.
Documentation quality. Request the technical datasheet and integration guide before purchasing. Poor documentation is a reliable early warning of broader support problems.
Manufacturing consistency. Ask whether the supplier publishes measured RSSI values at one metre for each batch, or whether you are expected to calibrate every unit individually. Batch consistency directly affects how much calibration work your installation team will face.
Replacement availability. Check whether the exact model will remain available for at least the expected battery life of your deployment. If a supplier discontinues a model, you may face mixed inventories with different signal characteristics.
Questions worth putting to a supplier:
- What is the measured variance in transmit power across a production batch?
- Can firmware be updated without removing the beacon from its mounted position?
- What happens to the warranty if the device is opened for battery replacement?
- Do you provide a sample batch for on-site RSSI testing before we commit to a full order?
- Which Bluetooth specifications and profiles does this model support?
Request for Proposal: What to Include
A well-structured RFP reduces the risk of receiving proposals that look comparable on price but differ fundamentally in what they actually deliver. Include the following elements:
Site description. Provide floor plans, photographs of representative areas, ceiling types, and a summary of construction materials. Suppliers cannot estimate installation difficulty or signal behaviour without this.
Environmental conditions. State temperature ranges, humidity levels, and any exposure to dust, water or cleaning chemicals. These determine the required ingress protection rating.
Accuracy requirements. Describe the zones you need to define and the minimum acceptable accuracy in each — but ground this in what your use case actually demands. Requesting sub-metre accuracy in a space full of metal racking, for example, needs to be flagged as a constraint the proposer must address honestly.
Receiver environment. Specify the operating systems and Bluetooth versions of the devices your visitors or staff will carry. This determines which protocols the beacons must support.
Integration points. List the existing systems the proximity platform must connect to, and what data needs to flow in each direction. Keep this at the interface level rather than specifying internal architecture.
Deliverables and acceptance criteria. State what the supplier must hand over: installed hardware, calibration records, as-fitted drawings, asset register, and evidence that defined zones meet the agreed accuracy thresholds.
Support and maintenance terms. Define the response times, hardware replacement process, and what constitutes billable work versus included support during the warranty period.
Total Cost of Ownership Considerations
The purchase price of the hardware is typically a minority of the total cost over a three-to-five-year operating period. A procurement decision based solely on unit price almost always underestimates the real expenditure.
The main cost drivers beyond the initial purchase are installation labour, calibration, battery replacement cycles, content updates, software licensing, and the staff time required to monitor and maintain the system. Each of these varies with the complexity of the environment and the demands of the use case.
When comparing two proposals, map out the expected costs year by year. Include at least one battery replacement cycle, an allowance for hardware failure, and a realistic estimate of the staff hours needed for ongoing content and configuration management. This comparison often changes the ranking of apparently similar options.
How Much Does a Beacon System Cost?
There is no meaningful single figure because the total depends on the number of devices, the complexity of the environment, the accuracy required, the software layer, and the length of the operational commitment. Any headline number that does not state these assumptions is not useful for budgeting.
As an illustrative example only — not a market average — consider a hypothetical deployment of 50 beacons in a single-storey retail space with straightforward ceiling mounting, a native app already in place, and a requirement for zone-level rather than metre-level accuracy. The hardware might represent roughly a third of the first-year cost, with installation, calibration, software licensing and initial content setup making up the remainder. Over three years, ongoing costs for battery replacements, monitoring, content updates and support would likely exceed the original hardware spend.
The only reliable way to estimate cost for your situation is to define the use case, map the environment, and request itemised proposals that break down each cost category separately.
Hardware Costs
Beacon unit prices vary with the battery capacity, enclosure rating, antenna design and whether the device supports additional sensors such as accelerometers or temperature probes. Higher transmit power and shorter advertising intervals drain batteries faster, which may push you towards larger enclosures and more expensive cells.
NFC tags are typically cheaper per unit than beacons but carry their own cost considerations. The tag itself may be inexpensive, but the backing material, printing, and lamination required for durability in a public environment add to the unit cost. Anti-metal tags, needed when NFC is placed on metallic surfaces, cost more than standard tags.
QR code infrastructure involves print or digital display costs, which vary with the material, size, placement method and whether the codes need to withstand outdoor conditions or frequent cleaning.
Volume pricing is common across all three technologies, but be cautious about ordering large quantities before completing a pilot. Environmental testing during a pilot may reveal that a different enclosure rating or battery size is needed, rendering a bulk order of the original specification wasteful.
Installation and Integration Costs
Installation costs depend primarily on ceiling height, mounting method, and whether the work can be done during normal hours or requires out-of-hours access. Devices mounted at three metres on standard ceilings take less time to install than those at eight metres in a venue with restricted access.
Calibration is a significant and frequently underestimated labour cost. Each beacon must be placed, powered on, and measured at multiple points to confirm that its RSSI values produce the expected zone boundaries in that specific location. In environments with variable interference — retail spaces with changing stock, for example — calibration may need to be repeated after initial fitting.
Integration costs cover the work to connect the beacon management platform to your existing systems. The scope of this work depends on what data needs to flow and in which direction. A simple deployment that triggers static content from a CMS involves less integration than one that passes real-time location data into an analytics platform.
Software, CMS and Analytics Costs
The software layer for a proximity deployment typically includes a device management platform for configuring and monitoring beacons, a content management system for defining what happens when a device enters a zone, and an analytics component for measuring interactions.
Device management platforms are often priced per beacon or per site, with tiered feature sets. Check whether the pricing includes firmware update capabilities, alerting for low batteries or offline devices, and the ability to segment devices into groups for bulk configuration changes.
Content management costs depend on whether you need to manage campaigns across multiple sites, support multiple languages, or schedule content changes by time of day. More complex content requirements mean more expensive software tiers or more staff time on manual updates.
Analytics components range from basic interaction counts to heatmaps and dwell-time analysis. More granular analytics require more data processing, which may carry higher licensing costs and, importantly, greater privacy compliance obligations. Broader CRM and marketing automation integration sits outside the scope of the proximity platform itself and should be evaluated as a separate system decision.
Ongoing Support and Maintenance Costs
Battery replacement is the most visible ongoing cost. The interval between replacements depends on the advertising interval, transmit power, and temperature — all of which should be documented during procurement so that replacement schedules can be planned rather than reactive. Some organisations negotiate battery replacement as a included service; others manage it internally with a stock of spares.
Hardware failure will occur. Typical failure modes include battery contact degradation, enclosure damage from cleaning or public contact, and water ingress in environments where the ingress protection rating was marginal. Budget for a failure rate and maintain a buffer stock so that a single failed beacon does not leave a zone unmonitored.
Firmware updates may be required to address Bluetooth specification changes, security patches, or compatibility with updated mobile operating systems. Check whether the supplier charges for firmware releases and whether updates can be applied remotely.
Content updates are an operational cost that scales with the ambition of the deployment. A museum changing exhibit information quarterly faces different content management demands than a retail site running weekly promotional notifications.
Hidden Costs in Proximity Deployments
Several cost categories are routinely omitted from initial budgets, often because they do not appear on the supplier's quotation.
Re-calibration after environmental changes. Retail spaces that reconfigure floor layouts, venues that change seating arrangements, and museums that move exhibits all alter the RF environment. Each change may require partial or full re-calibration, which is labour-intensive if not planned for.
Content creation. The technology delivers content, but someone must write, design, approve and localise that content. For museums and venues with large numbers of trigger points, content production can easily exceed the hardware budget.
Staff training. Front-of-house staff need to understand what the system does, how to troubleshoot basic visitor questions, and how to report hardware issues. Operations staff need training on the management platform. Training costs are often assumed to be negligible but accumulate across roles and staff turnover.
Privacy compliance overhead. Implementing consent mechanisms, maintaining data processing records, responding to subject access requests, and conducting privacy impact assessments all require staff time and, in some cases, legal review.
Decommissioning. When the deployment reaches end of life — whether because the technology is replaced, the venue is refurbished, or the use case is retired — removing hardware, deleting collected data, and updating privacy notices all carry costs that are rarely considered at the procurement stage.
Seasonal or event-driven adjustments. Venues that host temporary events may need to install, calibrate, operate and then remove proximity infrastructure for each event. The per-event cost of this cycle can be substantial if not factored into the original business case.
