First canary on a quality issue or deploy regression.
At a glance
Share of Salesforce Commerce Cloud orders that produced a Return or Credit Memo in the period. Computed as COUNT(orders with refund) ÷ COUNT(orders). The first canary on a quality regression, sizing issue, or deploy defect. Pair with the value-weighted view in finance reporting.
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. Window covers 14 Mar 26 to 12 Apr 26.
What’s interesting:
- The headless sub-brand jumped 2.6pp in 30 days. That is the actionable signal. Three usual culprits in order. (a) Quality issue on a launch SKU: check Top Products for any new SKU with refund rate >3× category average. (b) Sizing/fit issue, common when a buyer-marketing change brings new customers who don’t know the brand’s fit; size-guide updates and PDP video typically cut this within 4 to 8 weeks. (c) A deploy regression, SFCC deploys via Code Replication often take effect at 02:00 UTC; if the inflection landed on a specific Wednesday, look at the Tuesday release.
- DE refund rate (17.8%) is structurally high. German consumers exercise statutory return rights more aggressively than US or UK, and DE apparel sites typically run 16 to 22% refund rates. Per-site thresholds matter, the
>5%cross-category default would alert daily on a healthy DE site. Tune the alert to>20%for DE apparel. - JP refund rate (6.8%) is structurally low. Japanese consumers return at much lower rates (typical 3 to 7% across categories) due to cultural and shipping-cost reasons. A JP refund rate climbing to 10% would be a serious signal that gets lost in the realm-wide reading.
- B2B refund rate (1.3%) is normal for trade portals. Trade orders are mostly buying-team-vetted, scheduled, and often non-returnable by contract. The 18 B2B refunds are likely either damaged-in-transit or order-error replacements. A B2B refund rate above 2% would point to a process failure (wrong SKUs shipped, mis-priced contracts).
- Realm-wide refund rate (12.9%) is up 0.5pp vs prior period. The card alerts when the realm-wide rate crosses
>5%, which it always does on this fashion realm; per-site alerts with category-tuned thresholds are the right layer for this kind of merchant. The prior-period delta is the real signal.
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 athttps://<realm>.business.demandware.net. The closest like-for-like view is Merchant Tools, Site, Reports & Dashboards, Returns for any single site. Set the same date range, ensure status filter includes both Returns and Credit Memos (BM may default to Returns only), and look at the Return Rate column.
The cross-site rollup view is Reports & Dashboards, Operations which weights by orders.
Other Business Manager views that look like the same number but aren’t:
- Reports & Dashboards, Returns by Reason: lists return reasons, useful for diagnosis but is not a rate.
- Order Search, filtered to “has return”: counts orders matching a filter, can be used to hand-compute the rate.
- Einstein returns dashboard: refund rate within the Einstein-personalised audience, narrower than this card.
Internal identity (within SFCC):
This card is order-count weighted. The companion value-weighted view is
sfcc.refund_value ÷ sfcc.total_revenue (separate card, when added). The two should track within ~1pp on most realms; a divergence of >3pp means refunds are concentrated on either high-AOV or low-AOV orders disproportionately.
Cross-connector reconciliation:
Net of all PSPs: if you sum CyberSource refunds + Adyen refunds + PayPal refunds + Worldpay refunds, the total should sit close to this card’s numerator. A persistent gap > 5% means a PSP is missing or a manual / store-credit refund channel is bypassing the PSPs entirely.
Known limitations / merchant FAQs
Why is my refund rate climbing this month? Three usual root causes in order of likelihood. (1) Quality issue on a recently-launched SKU. Check Top Products by Revenue for new entries; any SKU with refund rate >3x its category average is the smoking gun. (2) Sizing or fit issue, common in apparel. Returns spike when a buyer-marketing change brings in customers unfamiliar with the brand’s fit; size-guide updates and PDP video typically cut this within 4 to 8 weeks. (3) Deploy-related defect. Check the deploy / release log against the inflection point. SFCC deploys via Code Replication often take effect at 02:00 UTC; if rate jumped on a Wednesday-09:00 read, look at Tuesday’s deploy. Does this card include B2B refunds? Yes. SFCC stores B2B and DTC returns in the sameReturn and CreditMemo objects on the order; the card sums both. B2B refund rates are typically much lower than DTC (sub-1% vs 8 to 25% for fashion DTC) so they pull the realm rate down. If you want the DTC-only view, filter out the B2B siteIds.
Why doesn’t the gross Total Revenue card move when refund rate spikes?
By design. Total Revenue is gross (sum of order_total at original confirmation); refunds live on separate Return / Credit Memo objects and do not retroactively edit the original order. This card and Total Revenue measure two different layers, both useful: Total Revenue tells you “what we sold”, this card tells you “how much we kept”. The unrendered “net revenue” view is on the connector roadmap.
Is the rate computed by order count or by refund value?
By order count for this card: count(orders with at least one return) / count(orders). The companion value-weighted view (refund_value / order_total) is a separate card. Order-count rate is the right read for product-quality and CX-team operations; value-weighted rate is the right read for finance.
SFCC has both Returns and Credit Memos in its data model. Which counts?
Both, an order with either a Return or a Credit Memo (or both) increments the numerator. The two are different SFCC concepts: a Return tracks the physical goods (received, inspected, restocked); a Credit Memo tracks the financial event (refund issued, store credit issued, partial). Most customer-facing refunds produce both. Order-cancellations before fulfillment often produce only a Credit Memo with no Return. The card pools them.
Why does Business Manager show a different refund rate?
Three reasons. (1) Order-count vs value-weighted. BM’s standard report is value-weighted; this card is order-count. (2) Site-scope. BM defaults to one site; this card aggregates the realm. (3) Window. BM “Last 30 days” is rolling; some BM dashboards show fiscal-month-to-date. Confirm the window is identical before comparing.
What is a “good” refund rate on SFCC?
Wildly category-dependent. Useful benchmarks. (1) B2B trade portals typically 0.3 to 1.5%. (2) DTC fashion / apparel typically 8 to 25% (peak return season is post-Christmas through January). (3) DTC beauty / health / supplements typically 1.5 to 4%. (4) DTC electronics / accessories typically 4 to 10%. The >5% alert threshold is a reasonable cross-category default; tune per-site for fashion realms.
My refund rate dropped suddenly. Could that be bad?
Yes, more often than merchants expect. Two suspicious patterns. (1) A returns-portal outage stops customers requesting refunds; CS tickets spike a week later when the backlog clears. Check returns-portal uptime and CS ticket volume for the same week. (2) A returns-policy tightening (e.g. dropping free returns, shortening the window) cuts refund rate in the short term but can cut conversion rate at checkout in the medium term. Pair this card with Conversion Rate over a 90-day window after any policy change.
How does refund rate flow into the customer LTV calculation?
Net revenue per cohort drives LTV; refund rate sets the gap between gross revenue (this card’s complement) and net revenue. A 1 percentage-point reduction in refund rate at a 10% gross rate is worth roughly 11% of refunded revenue back to LTV (depending on how the cohort is bucketed). This is why refund-rate work pays back faster than acquisition work on most fashion DTC realms.