Active Locations for the selected period.
At a glance
A real-time count of how many of your Square locations are live and transacting. Square pins one currency and one tax setup per location, so this number is the backbone for every per-location breakdown in the Nerve Centre, and a sudden drop usually means a store closed, a register went offline, or a location was archived in Square Dashboard.
| What it counts | The number of distinct location_id values that Square reports as active for your merchant account in the window. Sourced from the Square Locations resource, where each location carries a status of ACTIVE or INACTIVE. |
| Channel / source treatment | Location-level, not channel-level. A single location can serve Square POS in-store sales, Square Online web orders, and Square Invoices at once. This card counts the location, not the channels running through it. To split revenue by channel use Revenue by Channel. |
| Currency / unit | Whole number (count of locations). Note that each location is single-currency, so a multi-location international merchant has several currencies represented in this one count. |
| Time window | RT (real time, current snapshot) |
| Alert trigger | No alert configured on this card. It is a context and navigation anchor rather than a watch metric. Pair it with the drift and oversell alert cards for operational warnings. |
| Roles | owner, operations |
| Active vs inactive | Square keeps archived locations with status = INACTIVE. This card counts active locations only, so archiving a closed store removes it here. |
| Online presence | A location can be active for POS but never sell online. Active Locations does not tell you which locations have a Square Online presence, only that the location transacts. |
Calculation
Calculated automatically from your Square Online data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A UK homeware retailer running on Square. Four physical shops plus a Square Online storefront, with one shop currently being refitted. The snapshot is taken on 14 Mar 26.| Location | location_id | Status | Transacting this period |
|---|---|---|---|
| Bath flagship | LOC_001 | ACTIVE | Yes (POS + Online) |
| Bristol | LOC_002 | ACTIVE | Yes (POS) |
| Exeter | LOC_003 | ACTIVE | Yes (POS) |
| Cardiff (refit, closed) | LOC_004 | INACTIVE | No |
| Square Online (web fulfilment, mapped to Bath) | LOC_001 | (shared) | Yes |
| Active Locations (this card) | 3 |
- The web storefront is not a separate location. Square Online fulfils against a physical location’s inventory and tax setup. Bath flagship carries both its in-store POS sales and the web channel, so it counts once. This is why Active Locations can be lower than the number of sales channels a merchant feels they are running.
- The refitted shop dropped the count from 4 to 3. When Cardiff was set to
INACTIVEin Square Dashboard, it stopped counting here. If a merchant expected 4 and sees 3, the first check is whether a location was archived deliberately or by mistake. - Each active location can carry its own currency. If Bath sold in GBP and a hypothetical Dublin location sold in EUR, the headline revenue cards would mix currencies. Active Locations is the prompt to use the per-location filter on revenue cards rather than trusting a single blended figure.
Sibling cards merchants should reference together
| Card | Why pair it with Active Locations |
|---|---|
| Revenue by Location (in-store) | Active Locations tells you how many stores are live; this card tells you what each one earned. A location that is active but earning nothing is the signal worth investigating. |
| Revenue by Channel (POS / Online / Invoices) | A location can run several channels. Pair these two to see whether a quiet location is quiet everywhere or only on one channel. |
| POS to Online Inventory Drift Alert | Inventory parity is tracked per location. Knowing your active location count frames how many parity surfaces the drift alert is watching. |
| Total Revenue | Active Locations explains a step change in Total Revenue. Adding or closing a location moves the headline; this card is the context for why. |
| Total Orders | Order volume scales with the number of live locations. A location going inactive shows up here as a volume dip with no demand-side cause. |
Reconciling against Square
Where to look in the Square Dashboard: Square Dashboard, Account & Settings, Business information, Locations. The list shows every location with its status. Count the locations marked active and the figure should match this card exactly, since both read the same Square Locations resource. Other Square Dashboard views that look like the same number but aren’t:- Locations list, active filter: this DOES match. It is the same source.
- Locations list, all (including inactive): higher than this card, because archived and closed locations are included.
- Reports, Sales by location: only shows locations that actually had sales in the window, which can be lower than active locations if a location was open but quiet.
- Devices / registers list: counts hardware, not locations. One location can have many registers.
| Reason | Direction of divergence |
|---|---|
| Just archived or just created. A location archived or added in Square Dashboard takes a short sync cycle to reflect here. | Self-resolves within minutes |
| Sales-based vs status-based. The Sales by location report only lists locations with sales; this card counts all active locations regardless of whether they sold. | Vortex IQ higher when a location is open but had no sales |
| Inactive but recently active. A location set inactive mid-period still appears in historical sales reports but not in this real-time count. | Vortex IQ lower than a historical sales report |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
| Revenue by Location (in-store) | Locations with revenue should be a subset of active locations | A location can be active with zero sales (newly opened, seasonal, or refit). Active Locations counts it; the revenue card does not. |
google_analytics.active-users | No direct relationship | GA4 measures web sessions, not physical stores. Square POS locations never appear in GA4. Treat Square as the source of truth for location count. |
Known limitations / merchant FAQs
Does my Square Online web store count as a location? No, not as a separate one. Square Online fulfils against a physical location’s inventory, tax, and currency. The web channel runs through whichever location it is mapped to, so it does not add to the count. If you run web only with one physical location, you will see a count of 1. I closed a shop but the count didn’t drop. Why? The location is probably still set toACTIVE in Square Dashboard. Closing the doors is not the same as archiving the location. Set its status to inactive in Account & Settings, Business information, Locations, and the count will update on the next sync.
Why is this number lower than my Sales by location report?
It usually isn’t, but it can be higher. The Sales by location report only lists locations that actually sold in the window. This card counts every active location, including one that was open but had no sales. If you opened a seasonal pop-up that had a quiet day, it counts here but may be missing from the sales report.
Does an inactive location lose its historical data?
No. Archiving a location only removes it from this real-time count. Its past orders, payments, and inventory history remain in Square and in your Nerve Centre history. You can still filter older periods by that location_id.
Why is there no alert on this card?
Active Locations is a context anchor, not a watch metric. The operationally urgent signals live on the alert cards: POS to Online Inventory Drift Alert and Oversell Risk. If you want to be told when a location goes inactive, that can be configured as a custom watch in your Vortex IQ workspace.
Can two locations share inventory?
Square tracks inventory per location by default, with an option to mark catalog items as present at all locations (present_at_all_locations). Two locations can stock the same item, but on-hand counts are tracked separately per location, which is exactly why the drift and parity cards matter for multi-location merchants.