Cost-to-Serve Per Return: A Costing Model

Most finance teams can tell you the refund total on last month's P&L, but almost none can tell you what it actually cost to process a single return of a specific SKU through a specific channel. That gap is expensive. A refund is a visible number; the labor to inspect the item, the box and label, the warehouse slot it occupied for four days, the customer service ticket, and the markdown taken to resell it are invisible costs scattered across a dozen general-ledger lines. Without a cost-to-serve model, operators end up treating every return as equally bad, when in reality some returns lose a few dollars and others lose the entire margin on the original sale plus more. This post gives you a spreadsheet-ready model to compute cost-to-serve per return, broken down by channel and SKU, so you can see exactly where returns are quietly eating profit.

Why refund amount is the wrong number to manage

Refund amount tells you what you gave back to the customer. It says nothing about what it cost you to get the product back, decide what to do with it, and dispose of it. Two returns with an identical $60 refund can have wildly different economics: a lightly-worn t-shirt that goes back on the shelf at full price costs you shipping and a few minutes of inspection, while a returned electronics accessory that fails QC and gets liquidated at 20 cents on the dollar costs you the shipping, the inspection, the write-down, and the disposal fee. If you only track refund totals, you will never see this difference, and you will keep making channel and assortment decisions based on the wrong signal. This is the same blind spot we covered in our teardown of what a return actually costs end to end — cost-to-serve is the tool that turns that teardown into a number you can attach to every single unit.

The five cost buckets that make up cost-to-serve

A workable model does not need forty line items. Five buckets, consistently applied, get you 90% of the accuracy with a fraction of the maintenance burden.

• Reverse logistics — the label cost, carrier pickup or drop-off fee, and any customer-paid or merchant-paid freight for getting the item back to a facility.
• Handling and inspection — warehouse labor to receive, unbox, grade, and re-shelve or route the unit, usually costed as minutes per unit times fully loaded labor rate.
• Restocking and repackaging — new poly bags, boxes, tags, and any steaming or repair work needed before the item is sellable again.
• Value loss on resale — the difference between original sale price and the price actually realized when the item is resold, liquidated, or written off.
• Customer service and dispute overhead — the amortized cost of support tickets, chargebacks, and refund-related contacts tied to that order.

The fourth bucket, value loss on resale, is usually the largest and the most underestimated. Recommerce market data consistently shows that only about 48% of returned items resell at full price, with the rest moving through discount channels, liquidation, or write-off — a stat pulled from recent recommerce market reporting that should anchor your assumptions (see broader retail cost benchmarks at nrf.com). If your model assumes every returned unit goes back on the shelf at full price, you are understating cost-to-serve by a wide margin.

A worked example

Take a $60 apparel SKU returned through a marketplace channel. Reverse logistics runs $6.50 for a prepaid label and carrier handoff. Handling and inspection, at 4 minutes and a $22/hour loaded rate, is about $1.47. Repackaging adds $0.80 in materials and labor. On the resale side, assume this SKU sells through the recommerce channel at 55 cents on the dollar 60% of the time and at 25 cents on the dollar (liquidation) the other 40% — a blended realized value of about $28.20 against a $60 cost basis, for a value loss of $31.80. Customer service overhead, amortized across all returns for this SKU family, adds roughly $1.10. Total cost-to-serve: $41.67 on a $60 return — more than two-thirds of the sale price gone before you count the original cost of goods.

The refund is what you paid back. Cost-to-serve is what the return actually cost you — and until you separate the two, every channel and SKU decision is a guess.

Building the model: channel and SKU dimensions

Cost-to-serve only becomes actionable when you slice it by channel and SKU, because the five buckets behave very differently across both dimensions. Marketplace returns typically carry higher reverse-logistics cost due to mandatory prepaid labels and stricter SLA windows. Direct-to-consumer web returns often carry lower logistics cost but higher CS overhead because disputes are handled in-house rather than absorbed by the marketplace. SKU-level variation is even sharper: a fast-moving basic with high resale liquidity might carry a value-loss rate near 10%, while a seasonal or trend item returned after the selling window has closed can carry value loss above 80%. Pair this model with a SKU-level return-rate view so you're not just costing returns but predicting which products will generate them.

1. 1Pull 90 days of return transactions with SKU, channel, refund amount, and disposition (resell, liquidate, write-off).
2. 2Assign a standard reverse-logistics cost per channel based on actual carrier and label invoices, not list rates.
3. 3Time-and-motion a sample of 20-30 returns per category to get a realistic minutes-per-unit handling figure.
4. 4Pull realized resale/liquidation values from your recommerce or outlet channel reporting for the value-loss bucket.
5. 5Amortize total CS return-related headcount cost across total return volume for the period to get a per-unit CS overhead.
6. 6Sum the five buckets per SKU-channel pair and rank by total cost-to-serve, then cross-reference against return volume to find your highest-drain combinations.

Turning the model into decisions

Once cost-to-serve is visible by SKU and channel, three decisions become obvious that were invisible before. First, you can set channel-specific return policies — tighter windows or restocking fees on channels where reverse logistics is structurally expensive. Second, you can flag SKUs where cost-to-serve exceeds a threshold of the sale price and route them to a no-return-required refund instead of paying for a round trip that destroys more value than it recovers. Third, you can feed this data straight into the margin-leakage tracking we outline in our guide to return KPIs and profit leakage, so cost-to-serve stops being a one-off spreadsheet exercise and becomes a standing metric reviewed alongside return rate and refund cost. Retailers that have formalized this kind of unit economics work report meaningfully tighter reverse-logistics spend within two to three quarters, a pattern consistent with broader operational-efficiency findings from McKinsey's retail research.

Keeping the model maintainable

The biggest risk to a cost-to-serve model is not inaccuracy on day one, it's decay over time. Label rates change with carrier contracts, loaded labor rates drift with wage inflation, and resale realization rates shift with the recommerce market. Set a quarterly cadence to refresh each of the five input variables, and automate the SKU-channel rollup so it updates with each return batch rather than requiring a manual pull. A model that's accurate but stale by two quarters will misdirect exactly the decisions it was built to inform.