Sum of completed orders. The morning question every Salesforce Commerce Cloud merchant opens with.
At a glance
Headline gross revenue across every Salesforce Commerce Cloud (SFCC, formerly Demandware) order in the period, summed across every site and locale in the realm. The arithmetic sum of order_total from SCAPI / Open Commerce API order responses, regardless of order status, locale, or currency.
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 running on Salesforce Commerce Cloud B2C, four DTC sites (US, UK, DE, JP), one B2B portal, and a headless React storefront on SCAPI for a sub-brand. The 30-day window covers 14 Mar 26 to 12 Apr 26.
Three things to notice:
- The mixed-currency total is operationally meaningless on its own. SFCC’s strength is multi-site, multi-locale, multi-currency. Summing
order_totalacross them without FX produces a number with four units of measure stitched together. Enterprise SFCC merchants always report per-site or in a single base currency. A realm-wide rollup card in base currency is on the connector roadmap; for now treat this card as a navigation surface and pin per-site panels for operational reads. - **B2B revenue (4,850) is 38x DTC US AOV ($128). On enterprise SFCC realms B2B portals are commonly larger than DTC sites by gross revenue. A single missing B2B order can move the headline; pair this card with Total Orders and per-site filtering.
- The headless sub-brand on SCAPI is a separate
siteIdeven though it ships from the same warehouse. SFCC’s React Storefront (PWA Kit) and any custom headless storefront authenticate via SCAPI but are still asiteIdfrom a reporting standpoint. This is the right model, the headless front end is a different brand from the legacy ISML sites and should be measured separately. - The 30-day prior US revenue was $24,140,000. US DTC is down 2.3% vsP, well below the
drop >15% WoWalert threshold. Vortex IQ Nerve Centre stays quiet, but pinning per-site panels reveals UK is up 4% while DE is down 7% (a country-specific pattern that the realm-wide headline hides).
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Business Manager: SFCC’s admin tool is Business Manager, accessed at a per-realm URL likehttps://business.demandware.net/on/demandware.store/Sites-Site/default/ViewApplication-DisplayWelcomePage or the modern https://<realm>.business.demandware.net. Sandbox realms use a different host (the realm-staging or realm-development pattern).
The closest report is Merchant Tools, Site, Reports & Dashboards, Sales for any single site, or the cross-site Reports & Dashboards, Sales view if your role has multi-site read. Set the same date range, ensure the Status filter is set to “All” (not just COMPLETED), and look at Total Sales.
Other Business Manager views that look like the same number but aren’t:
- Reports & Dashboards, Sales (per-site): matches this card for that site only.
- Reports & Dashboards, Returns: returns / refunds total, not revenue.
- Order Search, filtered by date: counts orders, also lets you sum
order_totalvia export. - Pricing & Promotion reports: revenue attributed to specific promotions, narrower than this card.
Cross-connector reconciliation (when the merchant has connected payment processors and analytics):
These connectors see the same transactions through different lenses. Divergence is a data-quality signal worth investigating.
Net of all processors: if you sum CyberSource + Adyen + PayPal + Worldpay + any other payment connectors, the total should sit very close to this card. A persistent gap > 2% means either a payment processor is missing from your Vortex IQ workspace, or one of them is double-counting refunds.
Known limitations / merchant FAQs
Why does this card show a single mixed-currency number when our realm runs five sites in five currencies? SFCC’s strength is multi-site, multi-locale, multi-currency, and the archetype-default view sumsorder_total blindly. The number is operationally meaningless on its own at the realm level. Two practical workarounds today: (1) pin per-site panels in the Nerve Centre so each site reads in its native currency, and (2) export the per-site rows and roll them up in your finance system using your own spot or month-end FX rates. A base-currency rollup card is on the connector roadmap for this reason.
Which SFCC API does Vortex IQ read from, SCAPI or OCAPI?
Both, depending on what’s available in the realm. SCAPI (Salesforce Commerce API) is the modern REST surface that Salesforce now positions as the long-term path; OCAPI (Open Commerce API) is the legacy surface, still widely used on older realms. The card reads order data via whichever is configured during the connector setup. Field shapes are essentially equivalent for the headline order_total.
Why are there so many order statuses in SFCC and which ones count as revenue?
SFCC’s order lifecycle is rich because enterprise merchants use it for B2B, subscriptions, replacements, and managed-checkout flows. Statuses include CREATED, NEW, OPEN, COMPLETED, CANCELLED, FAILED, REPLACED, REPLACEMENT. The card sums all of them. For “realised cash” (i.e. orders the merchant will actually invoice for), filter to confirmation_status = CONFIRMED and status IN [OPEN, COMPLETED] and exclude REPLACED (the original of a replacement pair). Vortex IQ exposes this filter in the per-card config.
My BI team’s number from the SFCC data warehouse is different. Who is right?
SFCC’s data warehouse (Reports & Dashboards) has a 5 to 30 minute lag from real-time API and applies its own status filters. Treat SCAPI / OCAPI as the source of truth for “what the customer paid right now” and the data warehouse as the right tool for governed historical reporting. They will reconcile within 1% for windows older than 24 hours.
Does this include B2B trade-portal revenue at account-priced contract rates?
Yes. SFCC B2B sites use the same Order object as B2C, just with customerType = registered_b2b and account-priced line items. Trade-portal revenue is included by default, and on enterprise realms it is often the dominant revenue stream by basket size (typical B2B AOV is 30 to 50 times DTC AOV). Pair with Total Orders to detect mix shifts.
The Salesforce account team showed us a number from “Reports & Dashboards” that doesn’t match. Why?
Reports & Dashboards is a per-site report by default; Vortex IQ aggregates every site in the realm. Click into a single site in the Salesforce report and compare against a per-site filter in Vortex IQ. The two should match within rounding. The mismatch is almost always (a) site filter scope, (b) status filter (“All” vs “Confirmed only”), or (c) timezone (BM uses site-local time, the card uses UTC).
We’re considering re-platforming from SFCC to Shopify Plus / Adobe Commerce. Will this card help me decide?
Indirectly. The card gives you the gross revenue baseline. For a re-platform decision, you need the cost-of-running-SFCC view (license + cartridge maintenance + B2C Cloud entitlements) divided by this revenue, and the effort estimate to migrate cartridges, ISML pages, and SCAPI consumers. Vortex IQ’s role is to give you the trustworthy revenue baseline and ongoing parity tracking once a migration is under way. See adobe_commerce.total_revenue and shopify.total_revenue for the parallel docs.
Why does the card show a small but persistent gap from CyberSource / Adyen totals?
Three usual reasons. (1) Refund timing. SFCC order_total does not change after a refund; the payment processor’s number does. Over a 90-day window the gap closes, in a 7-day window it can be 1 to 3%. (2) Authorisation-only orders. Some flows (e.g. “Save card for later”, store credit redemptions) hit SFCC as orders without a full payment-processor charge. (3) Multi-processor orders. A single SFCC order paid part-PayPal-part-credit-card lands in two processors but one SFCC row. The card sums the SFCC row once.
How does SFCC handle subscription / repeat-purchase revenue?
SFCC does not have native subscriptions; merchants use cartridges (Subscribe Pro, Ordergroove, Bold) to layer recurring billing on top. Each recurring charge is a separate SFCC order with its own order_total, so a customer paying 240. The card sums them naturally.