Why roaming traces beat raw RSSI in busy aisles

Retail Wi-Fi teams inherit dashboards built for carpeted offices. Aisles, metal shelving, and seasonal displays move reflections weekly, which means a green RSSI tile can still feel broken on a scanner.

We start with roaming traces because they encode what the handheld actually did: which AP it left, how long reauthentication took, and whether retries clustered around checkout lanes. That story maps to shopper-visible symptoms faster than chasing decibel shifts.

When we onboard a chain, we align trace windows with transaction peaks—not averages—so analysts see the same minutes store managers complain about. The semantic layer matters: calling an event “sticky client” versus “AP overload” changes who gets paged.

Finally, we document known false positives, like promotional kiosks that reboot nightly. Without that appendix, good telemetry still trains teams to ignore alerts. The goal is fewer charts, each tied to a decision a store lead can recognize.