Returns-Adjusted ROAS: The Metric Your Dashboard Is Hiding

What Is Returns-Adjusted ROAS? The 60-Second Answer

Returns-adjusted ROAS (raROAS) is your return on ad spend recalculated on net revenue after refunds instead of gross checkout revenue: raROAS = (attributed revenue − refunded revenue from those orders) ÷ ad spend.

The scale of the problem is not niche: the National Retail Federation and Happy Returns estimate that 19.3% of online sales will be returned in 2025. If you sell apparel or footwear, your rate is likely higher still. Yet almost every attribution dashboard, platform-native or third-party, reports ROAS at the moment of checkout and never looks back.

Why Your Dashboard Ignores Returns

Three structural reasons. Second, incentives: ad platforms have no reason to subtract refunds from the revenue they claim: gross numbers make every platform's self-reported ROAS look better. Third, plumbing: refund events live in your store's order system, while conversions live in pixels; most tools never join the two tables.

This sits on top of the inflation you already know about, view-through credit, retargeting claiming existing demand, but returns inflation is different in one important way: it varies by channel, so it does not cancel out when you compare channels. It re-ranks them.

The ROAS Truth Ladder

Rung 5 requires modeling the counterfactual, which is where causal inference comes in.

A Worked Example: Two Channels, One Illusion

Illustrative example with round numbers. A European fashion brand spends €10,000 each on Meta prospecting and Google Shopping in a month:

On gross ROAS, Google Shopping wins and gets next month's incremental budget. On returns-adjusted ROAS, it loses by 17%. Why the gap? Shopping traffic in this example skews toward multi-size "bracketing" purchases and comparison shoppers, while Meta prospecting converts audiences who saw fit details and styling upfront. The average order value looked identical; the kept revenue did not.

Now add rung 5. A causal model asks what Google Shopping sales would have been without the spend: and finds a chunk was branded product searches that would have converted organically. The causal, returns-adjusted contribution drops further. The channel your dashboard crowned in week one is, after returns and counterfactuals, your weakest euro.

How to Implement Returns-Adjusted ROAS: 7 Steps

1. Join refunds back to originating orders. Your Shopify order export already links refund events to order IDs: no new tracking needed.
2. Attach orders to channels. Use your existing attribution data, but note its limits: attributed and incremental revenue are different things. Fix returns first, attribution second.
3. Use a returns maturation window. Comparing a fresh campaign's gross to an old campaign's net is a classic apples-to-oranges error.
4. Compute raROAS per channel and per campaign. Expect re-ranking. Bracketing-heavy channels (marketplaces, Shopping, size-uncertain categories) drop most.
5. Go one rung further where margins are thin. Deduct return shipping and restocking to approximate contribution: the contribution margin calculator and break-even ROAS calculator handle the arithmetic, and your true profit margin per channel emerges.
6. Feed net revenue into your causal model, not gross. A causal model trained on gross revenue faithfully learns to prefer high-return channels. Garbage in, confident garbage out.
7. Watch serial returners at the audience level. A small segment drives outsized refunds; their lifetime value is often negative even when every individual purchase looked profitable: the mirror image of LTV-based bidding logic.

Common Mistakes

• Adjusting blended numbers only. A returns-adjusted MER tells you the house is losing money, not which room the leak is in. Per-channel or it does not change decisions.
• Judging campaigns before returns mature. Every "winning" test read at day 7 is structurally biased toward high-return audiences.
• Treating returns as a fixed tax. Return rates differ by channel, creative, and audience: that variance is exactly the signal gross ROAS throws away.
• Confusing returns adjustment with attribution accuracy. They stack; they do not substitute. Netting refunds off over-claimed platform numbers still leaves the over-claiming. You need true ROAS on both axes.

Checklist

• Refunds joined to orders and channels in your data export
• Returns maturation window defined per category
• raROAS reported next to gross ROAS in every channel review
• Bracketing-prone channels flagged and re-benchmarked against fashion attribution benchmarks and Google Ads fashion ROAS norms
• Net revenue feeding your attribution model
• New-customer CAC computed on kept customers, not gross conversions
• Quarterly re-check against ecommerce ROAS benchmarks

Key Takeaways

Returns-adjusted ROAS is cheap to compute, uses data you already have, and routinely re-ranks channels: especially in fashion and apparel, where the cost of bad attribution compounds with every misallocated euro. The full fix is climbing the ladder: net revenue first, then causal contribution, because a correlational model fed gross revenue is wrong twice.

For €99, upload any historical GA4 period and get causal attribution for every channel in 1–2 minutes: no pixel, no migration.