Count of enabled SCC sites (country/locale storefronts under one realm).
At a glance
The number of enabled storefronts (siteId values) live in your Salesforce Commerce Cloud (SFCC, formerly Demandware) realm right now. SFCC’s defining feature is one realm hosting many storefronts, a US DTC site, a UK DTC site, a German site, a B2B trade portal, a headless PWA Kit sub-brand, and so on, each with its own locale, currency, catalogue assignment, and customer list. This card is the topology counter for your whole estate: it tells you, at a glance, how many storefronts Vortex IQ is watching and whether that count matches what you expect to be live.
Calculation
Calculated automatically from your Salesforce Commerce Cloud 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 Fortune-500 apparel retailer runs a single SFCC B2C realm. The connector enumerates the enabled sites and reports the topology as of 12 Jun 26.
Things to notice:
- The card reads 7, not 8. The Australia site (
RefArch-AU) is configured in the realm but disabled while a relaunch is prepared, so it does not count. The day it is re-enabled the card ticks to 8. If you expected 8 today, that gap is the conversation: is the AU relaunch on track, or did someone forget to flip it on? - The headless sub-brand is a full site.
Headless-Subbrandruns on PWA Kit and authenticates via SCAPI, but from a topology standpoint it is just anothersiteId. This is the correct model: the headless front end is a distinct brand from the legacy ISML sites and should be counted, measured, and reported separately. - The B2B portal counts as one site.
RefArch-B2Bcarries a tiny fraction of order volume but, on enterprise realms, often a large share of revenue. The site count treats it identically to a DTC site, that is right for topology, but a reminder that “one site” can mean very different revenue scales. - If this card suddenly read 6, that is an incident. A drop with no launch-calendar entry means a site went dark: a botched deployment, a disabled flag, an expired certificate on a custom domain, or a connector permission scope change. Because the time window is
RT, the card reflects it within one refresh. Pair it with Revenue at Risk (live), a silent site drop is exactly the kind of exposure that card is built to surface.
Sibling cards merchants should reference together
Reconciling against Salesforce Commerce Cloud
Where to look in Business Manager: SFCC’s admin tool is Business Manager, accessed at a per-realm URL likehttps://<realm>.business.demandware.net. Sandbox realms use a separate host (the realm-staging or realm-development pattern).
The authoritative list of sites is Administration, Sites, Manage Sites. This shows every site in the realm with its enabled / disabled state. The count of rows marked enabled should match this card. For a storefront-level confirmation, Merchant Tools is scoped to whichever single site you select in the Business Manager site picker; the picker dropdown itself is a quick way to see how many sites your role can reach.
Other Business Manager views that touch on sites but are not the same count:
- Administration, Sites, Manage Sites: the canonical list. Match this.
- Merchant Tools site picker: shows sites visible to your role, which may be narrower than the full realm if your permissions are scoped.
- Reports & Dashboards: scoped per-site; the number of sites you can switch between is indicative but role-dependent.
Known limitations / merchant FAQs
Does this count disabled or archived sites? No. The card counts enabled sites only. A site that is configured in the realm but switched off in Administration, Sites does not contribute. This is deliberate: a disabled site has no live storefront and no new orders, so counting it would overstate your live estate. Its historical orders still exist in SFCC and still appear in period revenue cards for the window in which they were placed. Is a headless PWA Kit storefront counted as a site? Yes. A headless storefront on PWA Kit authenticates through SCAPI but is still a distinctsiteId in the realm. It counts exactly like a legacy ISML storefront. This is the right model, the headless brand is operationally and commercially separate and should be measured on its own.
Why is the time window “RT” instead of a 30-day period?
Site count is a topology fact, not a flow metric. There is no “30-day site count”, there is only how many sites are enabled right now. The card takes a real-time snapshot on each connector refresh, so a site enabled or disabled today is reflected within one cycle rather than averaged over a window.
The count dropped and nobody launched or retired a site. What happened?
A silent drop almost always means one of: a site was disabled (intentionally or by a deployment that flipped the flag), the connector’s API credentials lost access to a site, or a custom domain or certificate issue took a storefront offline at the edge while the siteId technically remains enabled. Check Administration, Sites first, then the connector’s credential scope, then your CDN / domain status. Pair with Revenue at Risk (live) to gauge the financial exposure.
Can I get alerted when site count changes?
Yes. There is no threshold configured by default because the right behaviour is merchant-specific, but most enterprise customers add an alert rule that flags any change in this count. A site silently going dark is high-impact and easy to miss, so an any-change alert is a common and sensible choice. Configure it in the Alert Rules tab for this card.
Why might Vortex IQ show fewer sites than I see in Business Manager?
The most common reason is credential scope. Your human Business Manager login may see the whole realm, while the API credentials the connector uses are granted access to a subset of sites. Business Manager also lists disabled sites in the same table that this card excludes. Reconcile against Administration, Sites, Manage Sites and check the enabled column specifically.
Do sandbox sites show up here?
They should not, on a correctly configured workspace. Sandbox sites live in a separate realm. If you see unexpected sites with staging-style names, the connector is almost certainly pointed at a sandbox or staging realm rather than production. Fix the connector configuration; sandbox order and topology data must never mix into a production read.
Does the count include B2B portals and one-off campaign microsites?
Yes, if they are real enabled sites in the realm. SFCC B2B portals are full sites with their own siteId. Campaign microsites built as separate sites also count; campaign content built as pages within an existing site does not, because it is not a separate siteId.