Per-site / per-locale revenue mix. Enterprise SCC realms run 5-20 country sites typically - shapes localisation + market investment.
At a glance
How revenue splits across the storefronts in your Salesforce Commerce Cloud (SFCC, formerly Demandware) realm, one slice per siteId / locale. This is the card that turns SFCC’s defining feature, one realm hosting many country and brand storefronts, into a market-investment view. Enterprise realms commonly run 5 to 20 sites (US, UK, DE, FR, JP, a B2B portal, a headless sub-brand, and so on), and the shape of this donut tells you where your money actually comes from and where localisation and marketing spend should follow.
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 fashion retailer runs one SFCC B2C realm with four DTC sites, a B2B portal, and a headless sub-brand. The 30-day window covers 14 May 26 to 12 Jun 26. To make the mix readable, the team views it converted to a single base currency (USD) using month-end rates.
Things to notice:
- One site is over half the realm. US DTC at 56.2% is the engine and the single point of failure. If
RefArch-UShas a bad day, the realm-wide revenue card moves hard while four other sites sit untouched. This is why a per-site view matters: the headline can hide a healthy estate with one sick site, or a sick estate masked by one strong one. - The slices are only comparable because they were converted to a base currency first. In native currency the raw donut would mix USD, GBP, EUR, and JPY, slices whose sizes mean nothing relative to each other. Always read this card in a single currency. SFCC sites each carry their own currency by design, so the base-currency view (or a single-site filter) is the only honest comparison.
- The headless sub-brand is tiny but strategically separate. At 0.5% (
Headless-Subbrand) it barely registers, but it is a distinct brand on PWA Kit / SCAPI and should be judged on its own growth curve, not buried in the realm total. A new headless site often starts as a sliver here and is exactly where you watch for early traction. - Germany at 12.7% may be under-indexing its traffic. If
RefArch-DEcarries, say, 18% of sessions but 12.7% of revenue, that gap is a localisation, payment-method, or conversion problem specific to that market. Pair this card with Conversion by Locale to confirm whether a low revenue share is a traffic problem or a conversion problem.
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. The per-site revenue figures live in Merchant Tools, Site, Reports & Dashboards, Sales, scoped to whichever single site you select in the Business Manager site picker. To reproduce this card you read each site’s Sales report in turn and place them side by side; SFCC does not always present a single cross-site donut in the standard reports.
For a cross-site rollup, Reports & Dashboards, Sales at the realm level (if your role has multi-site read) reports in the realm’s configured base currency. That base-currency rollup is the right thing to compare this card against when you are viewing it in base currency.
Other Business Manager views to be careful with:
- Reports & Dashboards, Sales (per-site): matches one slice of this card for that site, in that site’s currency.
- Reports & Dashboards, Sales (realm rollup): matches the whole card only when both are in base currency.
- Order Search filtered by site and date: lets you sum
order_totalper site via export for a manual cross-check.
Known limitations / merchant FAQs
Why do the slices look wrong when I view the realm in native currencies? Because each SFCC site reports in its own currency and the donut is comparing different units. A USD slice and a JPY slice are not on the same scale, so the visual proportions mislead. Always read this card in a single currency: use the base-currency view or filter to one site at a time. SFCC’s multi-currency design makes a mixed-currency donut technically possible but operationally meaningless. Is this per-site or per-locale? It depends on configuration. OnesiteId can serve several locales, so the card can group by site (one slice per storefront) or by locale (one slice per language/region within a site). The card label and tooltip indicate which grouping is active. If a multi-locale site appears as several slices, the card is in locale mode.
Why is our tiny-volume B2B portal such a large revenue slice?
Because B2B AOV is typically 30 to 50 times DTC AOV on enterprise SFCC realms. A B2B portal can carry a small percentage of orders and still hold a large revenue share. This is expected, not a data error. Pair with Average Order Value to see the per-site AOV that explains the gap.
A site shows zero or near-zero revenue. Is it broken?
Possibly, or it may be a newly launched, low-traffic, or pre-launch site. Check first against Active Sites / Storefronts to confirm it is enabled, then against Conversion by Locale to see whether it has traffic that is not converting. A live, trafficked site with zero revenue is an incident; a new or disabled site reading zero is expected.
Does this include refunds?
No. Each slice is gross order_total. SFCC tracks refunds via separate Return / Credit objects that do not change the original order. For net revenue per site, read this card alongside Refund Rate and apply the refund layer per site.
How does a headless PWA Kit site appear here?
As its own slice, with its own siteId. A headless storefront on PWA Kit / SCAPI is a distinct site, so its revenue is tracked separately from the legacy ISML sites. This is intentional, a headless sub-brand should be measured on its own, and this card is where you watch its share grow.
Can I alert on a site’s share dropping?
There is no threshold by default, but mix-shift alerts are commonly configured per profile, for example flagging when a site’s revenue share moves sharply versus the prior period. Set this in the Alert Rules tab. Because the card spans many sites, most merchants alert on the one or two sites that matter most rather than on every slice.