At a glance
The top-N most-refunded products by refund value (or refund count) over the period. The card refund-investigation always lands on. Refund value clusters disproportionately on a tiny minority of SKUs: typically 5-10 SKUs explain 30-50% of total refund value on most stores. Identifying these and acting on them (relisting with better images, fixing size charts, pulling defect batches, hiding offending SKUs) is the highest-leverage refund reduction lever available. On BigCommerce specifically, refund-without-return cases (Amazon A-to-Z claims, “keep it” goodwill) means this card may show items that never came back to the warehouse, which differs from the BC Return Status view of physically-received returns.
Calculation
Calculated automatically from your BigCommerce 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 US apparel brand on BigCommerce, 90-day window 14 Feb 26 to 14 May 26. Total refund value across the period: $58,200 from 1,840 refund events.
What’s interesting:
- Top 10 SKUs = 63% of refund value (from 28% of gross sales). Refund value is wildly concentrated; finding and fixing the top three closes 30%+ of total refund value.
- The Linen shirt (M) at 13.8% refund rate is the clear quality issue. Almost twice the rate of the next-worst SKU. Investigate: is it a fit issue (sizing chart wrong), a fabric issue (shrinkage in wash), an expectation issue (description / images don’t match reality)? Pull customer refund reasons for this SKU specifically; usually 3-5 distinct reasons explain 80% of refunds.
- Slim-fit chinos in 4 sizes all appear in top 10 (sizes 30, 32, 34, 36). This is a classic “size-fit issue across the range” pattern: customers don’t know their size in this fit, order multiple sizes, return all but one. Either improve the size guide, offer a try-before-you-buy option, or accept the structural higher refund rate as the cost of doing fit-sensitive apparel.
- Wool overcoat appears at #3 by value but only 4.4% refund rate. This is “high-AOV product with normal refund rate”; the refund value is high because the AOV is high, not because the SKU has issues. Don’t optimise this SKU for lower refund rate; it’s already healthy.
- The 220 long-tail SKUs at 1.7% blended refund rate are healthy. Most stores’ “average” SKU runs 1-3% refund rate; the top-10 outliers are where attention belongs.
- Investigate the Linen shirt (M) immediately. 13.8% refund rate on a high-volume SKU is the highest-leverage fix in the catalog. £5,800 of refund value over 90 days = £23,200/year on that single SKU.
- Address the chino sizing issue systemically. Better size guide with body measurements, “try multiple sizes” promo (free returns), or accept 7-9% as the structural rate.
- Audit refund reasons for top-3 SKUs. Free-text reasons from BC’s refund flow typically cluster into 3-5 categories per SKU; this is the diagnostic input.
- Consider relisting with better images. Apparel refund rates drop 2-4pp after image quality upgrades (multiple angles, model wearing, scale references).
- Watch for new SKUs entering the top 10. A new SKU appearing in the top-5 within 30 days of launch is the early-defect signal; pull it from active inventory pending investigation.
- Pair with BC Top Products to find SKUs that are top-revenue and top-refunded simultaneously; these are the highest-leverage targets.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in BigCommerce’s own dashboard: The closest native view is BC Control Panel → Analytics → Insights → Refunds → By Product (Plus and Enterprise tiers). For Standard tier, use the Orders export filtered to refunded orders and pivot onproduct_id in spreadsheet.
For per-channel breakdowns: Channel Manager → (channel) → Returns / Refunds reports. Amazon Channel Manager surfaces marketplace refunds separately.
Why our number may legitimately differ from the vendor’s:
Cross-connector reconciliation (when both connectors are connected for this merchant):