Orders by Currency.
At a glance
How your order count splits across the currencies live in your Salesforce Commerce Cloud (SFCC, formerly Demandware) realm. Each SFCC site carries its own currency, so a realm running US (USD), UK (GBP), German (EUR), and Japanese (JPY) sites will show four slices. Unlike the revenue split, this card counts orders, not money, so the currencies are directly comparable: an order is an order regardless of its denomination. It is the cleanest single view of where your customers actually are.
| What it counts | The number of orders grouped by the order’s currency over the window. Each order carries a currency tied to the site it was placed on; this card buckets orders by that currency and counts them. |
| Why it matters | Because it counts orders rather than revenue, the slices are honestly comparable with no FX caveat. It tells you the geographic / market shape of demand by volume, which is often different from the revenue shape (a high-AOV market can have few orders; a low-AOV market can have many). It is a fast read on which markets carry your transaction load. |
| Reading the value | Read it as a volume mix. A currency’s share growing means more orders are coming from that market; shrinking means fewer. Compare against the revenue split: a currency with a large order share but small revenue share is a low-AOV market, and vice versa. |
| Orders vs revenue | This card is volume; Revenue by Site / Locale is value. The two often disagree, and the disagreement is the insight. |
| Status scope | Counts orders as returned by the order API over the window. SFCC has rich order statuses (CREATED, NEW, OPEN, COMPLETED, CANCELLED, FAILED); whether all are counted or filtered to confirmed orders depends on the card’s filter configuration. |
| Currency source | The currency is the order’s currency, which derives from the siteId the order was placed on. A single multi-currency site is uncommon in SFCC; in practice currency maps closely to site. |
| Unit | number |
| Time window | 30D (default 30-day window) |
| Alert trigger | none configured by default. A shift in the currency mix is usually read alongside revenue and conversion rather than alerted on directly. |
| Sentiment key | scc_orders_by_currency |
| Roles | owner, finance |
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 retailer runs one SFCC B2C realm with four DTC sites and a B2B portal. The 30-day window covers 14 May 26 to 12 Jun 26.| Currency | Sites contributing | Orders | Share of orders | (For contrast) revenue share |
|---|---|---|---|---|
| USD | RefArch-US, RefArch-B2B, Headless-Subbrand | 198,420 | 59.9% | 59.5% |
| GBP | RefArch-UK | 62,400 | 18.8% | 20.1% |
| EUR | RefArch-DE | 41,800 | 12.6% | 12.7% |
| JPY | RefArch-JP | 28,600 | 8.6% | 7.7% |
| Total | 331,220 | 100% | 100% |
- The slices are directly comparable with no FX needed. Unlike the revenue donut, this card counts orders, so a USD order and a JPY order are the same unit. That is what makes Orders by Currency the honest first read of market shape: 59.9% of orders are USD-denominated, full stop, no exchange-rate assumptions required.
- Order share and revenue share track closely here, which itself is the signal. USD is 59.9% of orders and 59.5% of revenue; the market AOVs are broadly similar across DTC sites. When these two columns diverge sharply, that is the interesting case: a currency with a big order share but small revenue share is a low-AOV market (a candidate for basket-building), and the reverse flags a high-AOV market punching above its volume.
- USD spans three sites, including the B2B portal. Because currency derives from site, the USD slice silently bundles US DTC, the B2B trade portal, and the headless sub-brand. If you need to separate them, switch to Revenue by Site / Locale or filter by
siteId. Currency is a coarser cut than site. - A new currency slice appearing is a launch event. If a fifth currency shows up next month, a new country site went live (or a site’s currency changed). Cross-check against Active Sites / Storefronts, the new currency should correspond to a new active site.
Sibling cards merchants should reference together
| Card | Why pair it with Orders by Currency |
|---|---|
| Revenue by Site / Locale | The value counterpart to this volume view. Comparing order share against revenue share reveals per-market AOV differences. |
| Total Orders | This card is Total Orders sliced by currency. The slices must sum to the realm-wide order count. |
| Average Order Value | Explains why a currency’s order share and revenue share differ. High AOV markets punch above their order volume. |
| Active Sites / Storefronts | Each currency maps to one or more sites. A new currency slice should match a new active site. |
| Conversion by Locale | A currency carrying lots of traffic but few orders is a conversion problem in that market. |
| Payment Status Distribution | Different currencies / markets favour different payment methods; payment health can vary by currency slice. |
Reconciling against Salesforce Commerce Cloud
Where to look in Business Manager: SFCC’s admin tool is Business Manager, at a per-realm URL likehttps://<realm>.business.demandware.net. SFCC does not present a single cross-site “orders by currency” report out of the box, because currency is a site property. To reconcile, read order counts per site under Merchant Tools, Site, Reports & Dashboards, Sales (or Ordering, Orders with a date filter) for each site, then group the per-site counts by the site’s configured currency. Sites sharing a currency (for example a US DTC site and a B2B portal both on USD) roll into the same slice on this card.
For an exact cross-check, Ordering, Order Search filtered by date lets you export orders and count them by currency in your own tool.
Other Business Manager views to be careful with:
- Reports & Dashboards, Sales (per-site): gives the order count for one site, in one currency.
- Ordering, Orders / Order Search: the order-level source; export and group by currency for an exact match.
- Site currency configuration (Administration, Sites): tells you which currency each site uses, so you can map sites to slices.
| Reason | Direction of divergence |
|---|---|
| Time-zone. BM per-site reports use the site’s time zone; Vortex IQ uses UTC by default. Boundary days shift. | ±1 day at boundary |
| Status filter. BM reports may apply a default status filter; this card counts per its own filter configuration. Match the filters before comparing. | Either, depends on filter |
| Currency-to-site mapping. Reconciling requires grouping per-site BM counts by currency; an error in that mapping (for example forgetting a B2B portal shares USD) causes apparent gaps. | Manual mapping error, not a real divergence |
| Data warehouse lag. SFCC Reports & Dashboards lags real-time order placement; the order API is near-real-time. | Vortex IQ slightly higher for current-day data |
| Multi-currency site (rare). If a single site supports more than one currency, BM per-site counts and this card’s per-currency counts will not line up one-to-one. | Slice-level differences only |
Known limitations / merchant FAQs
Why count orders instead of revenue by currency? Because order counts are directly comparable across currencies with no FX. An order is one unit regardless of denomination, so the slices are honest. Revenue by currency would mix USD, GBP, EUR, and JPY amounts that are not on the same scale. For the value view, use Revenue by Site / Locale and read it in a single base currency. Why does one currency bundle several of my sites? Because currency derives from the site, and multiple sites can share a currency. A US DTC site, a B2B portal, and a headless sub-brand can all be USD, so they merge into one USD slice here. Currency is a coarser cut than site. To separate them, filter bysiteId or use the site-level cards.
A new currency slice appeared. What does that mean?
A new site went live with a new currency, or an existing site’s currency was changed. Cross-check against Active Sites / Storefronts, a new currency should map to a new active site. If no new site launched, investigate a configuration change on an existing site.
Order share and revenue share disagree for a currency. Is that a problem?
Not necessarily, it is usually just AOV. A currency with a large order share but small revenue share is a low-AOV market; the reverse is a high-AOV market. The disagreement is the insight, not an error. Pair with Average Order Value to quantify it. A sudden divergence that was not there before is worth investigating.
Does this count cancelled and failed orders?
It depends on the card’s filter configuration. SFCC has many order statuses, and the card can count all of them or filter to confirmed orders. If your count looks high versus a status-filtered Business Manager report, the card is likely counting more statuses. Match the filters before assuming a divergence.
How does the B2B portal show up here?
As part of whichever currency it is configured in, usually the same currency as the matching DTC site (often USD). B2B carries few orders relative to DTC, so it is typically a small contributor to its currency’s order count even though it can be a large contributor to that currency’s revenue.
Can I alert on a currency mix shift?
There is no default alert. A currency mix shift is usually interpreted alongside revenue and conversion rather than alerted on in isolation, because it is rarely actionable on its own. If you want one, configure a sensitivity rule per profile, for example flagging when a currency’s order share moves sharply versus the prior period.