How to Calculate Return Rate: Three Formulas, Worked Examples, and Benchmarks

Return rate is one division, and most brands compute the wrong one. Units, orders, and revenue give three different answers from the same quarter, and they routinely sit four to six percentage points apart.

A quick disambiguation first: this is the retail metric, not the finance rate of return that dominates this search. For retailers and brands, return rate measures how much of what went out came back. For omnichannel retailers feeding D2C, stores, and dealer networks at once, it's also three different numbers per channel, which is where the spreadsheet version starts to crack. Claimlane's angle on this metric is simple: the rate is only as useful as the reason data underneath it.

The formulas first, then one worked example carried through everything else.

The three return rate formulas

All three need a defined time window and a consistent rule for the numerator. The window question matters more than it looks: returns lag sales by days to weeks, so a fast-growing brand computing returns-this-month over sales-this-month understates the true rate. Match returns to the sales cohort they came from.

What sits behind the numerator, and what a returns management system does to keep it clean, is covered further down.

One brand, three numbers: a worked example

Take a sporting goods retailer's quarter: 120,000 units sold across 38,000 orders, €4.56M gross revenue. Returns: 14,400 units across 6,840 orders, €598,000 of returned revenue.

Same quarter, three answers, six points of spread. The order rate runs hottest because one returned item flags the whole order. The revenue rate sits above the unit rate whenever returns skew toward expensive items, which they usually do in ecommerce returns.

A brand quoting "our return rate is 12%" without naming the formula isn't lying. It's just not saying anything checkable.

Which formula to use when

Use all three, for different jobs. Unit rate is the operations metric: it scales with warehouse touches and freight spend. Revenue rate is the finance metric: it ties to margin and belongs in the monthly pack. Order rate is the customer-experience metric: it approximates how many buying experiences ended with a return.

The common failure is comparing a unit rate against an order-rate benchmark, then celebrating or panicking over a phantom gap. Bracketing behavior widens the spread further, since bracketers inflate unit and order rates while their kept items soften the revenue rate.

Name the formula in every report. One line of discipline removes most return-rate confusion.

What counts as a return

The numerator needs rules, written once and enforced by the intake. Four decisions cover the awkward cases.

Exchanges: count them in the operational rate (the unit still travels) but track them separately, since an exchange retains revenue. Dealer and wholesale returns: keep B2B flows out of the D2C rate and report them on their own line, a distinction hybrid B2C and B2B claims setups handle structurally. Warranty replacements: not returns, claims, covered two sections down. Refused and undeliverable parcels: transit events, not customer decisions, so log them under delivery, not returns.

Deduplication matters too. An exchange that later gets returned is one unit, not two, and a returns process customers are kept informed through tends to also be the one generating clean records.

Benchmarks: what a good return rate looks like

Ecommerce overall runs in the high teens to low twenties as a percentage of sales, with apparel and footwear well above that and hardgoods like furniture, tools, and general merchandise returns below it. Channel matters as much as category: store returns run far lower than ecommerce for the same products.

Category-by-category numbers, and the data behind them, live in the average ecommerce return rates guide, so this article won't repeat the table. The working rule: benchmark against the category and the channel, not against "ecommerce."

One caution on chasing a low number. A return rate can be too low, signaling a returns process so hostile customers just keep broken products and churn quietly.

Controllable vs uncontrollable: the segmentation that makes the number useful

A blended return rate says how much. It never says why, and the why splits into two budgets.

The split only exists if intake captures a reason on every return, against a fixed taxonomy, which is the whole argument for structured returns reason codes. A brand at 18% blended might be 5% controllable and 13% uncontrollable, and those two numbers have different owners and different fixes.

Set targets per segment. Blended targets produce blended excuses.

Return rate vs warranty claim rate

Durable-goods brands have a second number hiding behind the first. A product that fails in month seven never enters the returns math, it arrives as a warranty claim, and brands that only watch return rate systematically undercount product failure.

The fix is reporting both on one dashboard: return rate for the purchase window, claim rate (confirmed claims ÷ units sold) for the life of the fleet, as part of the wider returns and warranty KPI set. The two series together show whether a quality problem is surfacing early or late.

For a sporting goods or electronics brand, a 1.5% claim rate on top of a 12% unit return rate changes the quality conversation entirely. One number is sizing noise, the other is engineering signal.

What each return costs

The rate gets attention. The unit economics get budgets. A workable fully loaded cost per return for mid-priced goods: return freight €8, receiving and inspection labor €5, repackaging €2, average markdown or write-off €3, roughly €18 per returned unit before refund float and support time.

On the worked example's 14,400 returned units, that's about €259,000 a quarter in processing cost alone, near 5.7% of gross revenue, before counting the hidden costs of returns and claims like customer churn after a bad experience. Categories with long, manual flows run far worse, the dynamic documented in why furniture returns take 47 days.

That's the finance-readable frame: a two-point cut in controllable returns on this example is worth roughly €86,000 a year in processing cost, plus the recovered margin on goods that never left.

Where the data lives

The formula's inputs are scattered by default. Units and orders sit in Shopify or the commerce platform, refunds in the payment stack, credit memos in NetSuite, SAP, Microsoft Dynamics, or Business Central, and the return reasons, if they exist at all, in a helpdesk inbox.

Assembling the metric monthly from four exports is how return-rate reporting quietly dies. The structural fix is an intake that writes one record per return with reason, channel, and value attached, synced to the ERP through ERP and finance integration, so analytics reads return rate per SKU, channel, and reason without a data project.

That single record is also what keeps unit, order, and revenue variants consistent, since all three divide the same ledger.

When the number is bad: what actually moves it

Fixes follow the segmentation. Controllable returns respond to operations: pre-shipment QC on the top returned SKUs, packaging upgrades where damage reasons cluster, product content fixes where "not as described" clusters, and fraud screening where serial returners cluster, per the playbook in return fraud prevention.

Uncontrollable returns respond to expectation-setting: size guidance, richer imagery, and exchange-first flows that keep revenue in the house. The plumbing that runs all of it at scale is a return management system, which is also what enforces the reason taxonomy the whole article depends on.

Rank SKUs by returned-unit cost, fix the top five, re-measure the cohort. Quiet, repetitive, effective.

FAQ

Pick one formula, pull last quarter's numbers, and compute it this week, then compute it again segmented by reason. The gap between those two views is the to-do list. When the reason data turns out not to exist, build the return & warranty portal customers actually use and start collecting it on the next return.