Assigning a unit to a store connects it to everything else: who is alerted, whose territory it falls in, and which store's compliance record it contributes to.
You can do it from the unit's own page, or from Stores & locations — where every sensor without a store is gathered at the top of the page, above the rest of the estate. That second route is the faster one when you're working through a delivery: the list shrinks as you go, and what's left is what's left to do.
Below that, the same page shows your whole fleet the way you think about it — region, then market, then store, then the sensors in each. A store with no sensor yet is called out rather than simply absent, because during a rollout that is the thing you are looking for.
- A sensor that has never reported is marked differently from one that reports but isn't counted yet — those are different problems with different fixes.
- Closed stores are listed separately, dimmed. They stop alerting and stop being billed, and keep their readings and compliance history.
Assignment lives in two places on purpose: the fleet view on Stores & locations (best for working through many units), and the Store & alerting card on each unit's own page (best when you are already looking at one). Both run the same underlying change, so it does not matter which you use. The unit page's card also shows who is contacted for this unit and what happens if nobody acknowledges — the escalation chain that actually applies, resolved the same way an alert would resolve it.