Requirements before supplier selection
Once a contract is signed, the dynamic with an IoT integrator shifts from evaluation to operational coordination. For proximity technology deployments—whether installing Bluetooth beacons in a retail flagship or mapping NFC touchpoints across a museum—the integrator is handling physical infrastructure inside a live or soon-to-be-live environment. This is fundamentally different from commissioning a purely software project.
The core of managing this relationship is establishing a shared understanding of where your responsibilities end and theirs begin. An integrator typically handles hardware procurement, physical placement, signal calibration, and initial system commissioning. The venue provides site access, outlines operational constraints (such as restrictions on drilling into heritage walls), and ultimately owns the day-to-day environment where the hardware sits.
A productive relationship depends on treating the integrator as a specialist contractor rather than a turnkey solution provider. They can configure advertising intervals and transmit power, and they can measure Received Signal Strength Indicator (RSSI) values on the day of installation. However, they cannot control the subsequent movement of stock displays, the addition of metal racking, or the fluctuation of visitor density—all of which will alter signal propagation. Both parties need to acknowledge these physical realities upfront to prevent disputes over accuracy or system performance later.
Compatibility and installation evidence
Retail refits and shopfitting coordination
In a retail environment, a beacon deployment rarely happens in isolation. It usually coincides with a shopfit or a visual merchandising update. The integrator needs clear sightlines for beacon placement before heavy shelving and promotional gondolas are installed. If the integrator arrives after the fit-out team has finished, mounting heights and line-of-sight may be compromised by new lighting rigs or overhead signage. Managing the relationship here means insisting on a coordinated timeline where the integrator conducts a post-fit-out walk-through to adjust calibration before the system goes live.
Museum gallery changeovers
Museums present a distinct operational rhythm. Exhibitions change regularly, meaning the physical environment the beacons are calibrated for is temporary. When an exhibition is deinstalled, the integrator—or trained internal staff—must relocate hardware and recalibrate zones for the new layout. The relationship must account for this cyclical work. Agreeing on a standardised process for minor relocations, rather than treating every gallery change as a new project, keeps costs predictable and ensures the indoor navigation system remains accurate.
Temporary events and rapid deployment
For event organisers, the integrator relationship is compressed into days rather than weeks. The priority is rapid deployment, clear demarcation of who removes the hardware post-event, and verification of battery levels immediately before doors open. A battery tested a week prior might deplete during idle transit. In these scenarios, managing the relationship means defining a strict handback protocol that accounts for every unit of hardware, preventing losses when temporary infrastructure is struck.
Communication and escalation
Regardless of the venue type, scattered email threads are inadequate for managing physical deployments. If a beacon with a specific identifier needs to be moved from Zone 4 to Zone 5, that change must be logged in a shared system visible to both the venue’s operations team and the integrator’s engineers. Agreeing on a single source of truth for configuration changes prevents discrepancies between the physical hardware and the software management platform.
Roadmap, obsolescence and fallback
Abdicating the asset register
The most frequent mistake is allowing the integrator’s internal spreadsheet to serve as the sole record of your hardware inventory. If the contract ends or the integrator becomes unavailable, the venue is left with mounted hardware it cannot identify or manage. The venue must own the asset register from day one, requiring the integrator to populate it with the exact hardware IDs, firmware versions, and physical mounting locations as part of the commissioning process.
Accepting vague handover criteria
Signing off a deployment because "the system works" invites future problems. Handover criteria must be defined in measurable terms specific to your environment. For example, a valid criterion might state that a location-based notification triggers reliably when a test device crosses the designated zone boundary, rather than three metres inside it. Without these benchmarks, you have no objective way to verify the integrator has met their obligations.
Ignoring configuration locks and firmware control
Some integrators lock beacon configurations to prevent accidental changes. While this protects the installation, it creates a dependency. If you need to adjust a transmit power setting for a seasonal retail display, a locked beacon requires a paid call-out. Clarify who holds the administrative rights to the hardware, how firmware updates are applied, and what the process is for making minor parameter changes without requiring an engineer on site.
Expecting integrators to defy physics
An integrator can mitigate interference through careful placement and calibration, but they cannot eliminate the physical properties of your building. Heavy structural steel, reflective glass, or dense materials will attenuate Bluetooth signals regardless of the hardware chosen. Holding an integrator to a guarantee of metre-perfect indoor accuracy in a highly reflective environment is a recipe for conflict. Accuracy expectations must be grounded in a measured pilot of your specific site, not manufacturer marketing materials.
Key checks during the project
- Label verification: Are the physical labels affixed to the beacons accurately matching the identifiers in the software asset register?
- Device diversity testing: Has the integrator demonstrated the system functioning with the actual mix of devices your visitors carry, recognising that iOS and Android devices handle Bluetooth scanning differently?
- Environment-specific calibration: Has the integrator provided RSSI measurements taken in your actual space, rather than relying on factory-default calibration values?
- Documentation handover: Have you received the mounting diagrams, zone maps, and configuration logs necessary to manage the system independently?
When the installation is complete and these checks are satisfied, the relationship transitions from active deployment to ongoing maintenance. At that stage, the focus shifts inward, requiring the venue to formalise how these physical systems are recorded and managed by its own operations team.
