Ask a team what a return costs and most will name the return label. That is the smallest line. The real cost stacks up across return shipping, warehouse handover, inspection, restocking or disposal, the refund itself, and the sale you may never recover. Shopify estimates that processing a single return runs 20% to 65% of the item's original value once you add it all up. A five dollar label can hide a twenty dollar problem, and because these costs sit in different systems, most brands never total them per return. When you finally do, two things happen: you stop offering free returns on everything, and you find the SKUs quietly draining margin. Doing that totalling is exactly what Pango is built to make possible.
Why return shipping is the smallest cost
The return label is the number everyone quotes, because it is the one that shows up on an invoice. It is visible, so it feels like the cost.
It is not. It is the entry fee. Once the parcel arrives, a chain of labor and lost value kicks in that dwarfs the postage. The trouble is that these other costs live in different systems: shipping is with the carrier, handover is in the warehouse, refunds are in your payments tool. Nobody adds them up per return, so the label stands in for the whole thing. Pango runs returns, exchanges, and claims in one flow, so those events finally sit in a single system instead of four.
The full cost stack of a single return
A return is not one cost. It is a stack of them, spread across your operation. Here is the whole thing in order.
| Cost line | What it covers | Often overlooked? |
|---|---|---|
| Return shipping | The label and freight | No, this is the visible one |
| Warehouse handover | Receiving and sorting the parcel | Yes |
| Inspection | Checking condition and grading the item | Yes |
| Restocking | Cleaning, repackaging, shelving | Yes |
| Disposal | Writing off items that cannot be resold | Yes |
| Refund processing | The refund and any payment fees | Sometimes |
| Lost resale value | Reselling below full price, or not at all | Almost always |
The visible line is the top row. The margin damage is in the rows below it.
Warehouse handover and inspection time
The moment a returned parcel hits your warehouse, it starts consuming labor. Someone receives it, sorts it, and moves it to an inspection station. That handover time is real cost, and it scales with volume. Then inspection: a person opens the parcel, checks the item against the return reason, and grades it as full-price resellable, discount resellable, or a write-off. That judgment takes time and training.
These two steps rarely show up in any dashboard. They are buried in warehouse labor hours, yet they are often the largest slice of the true cost. Pango's analytics track warehouse handover time and carrier performance directly, the first place this hidden cost becomes visible once returns, tracking, and delivery run on one post-purchase platform.
Restocking, disposal, and lost resale value
After inspection, the item goes back to stock or to disposal. Restocking is not free: cleaning, repackaging, and shelving all take labor, and even a perfectly resellable item usually sells below full price the second time, because it is now an open-box or clearance unit. That gap is lost resale value, the cost almost nobody counts.
Disposal is worse. When an item cannot be resold, you have paid to ship it, receive it, and inspect it, only to write it off entirely. For those SKUs, a returnless refund is often the cheaper path, because it skips the shipping and handling you would spend to reach the same write-off. With Pango, you can set that returnless rule on exactly the SKUs where the math says so, instead of applying one blunt policy to everything.
Cost per return by product type
The true cost is not one number. It varies wildly by product type, which is why a single free-returns policy overpays on some items and bleeds on others. A small, durable, easily resellable item costs little to take back. A bulky, low-margin, or hygiene-sensitive item can cost more to process than it earns. Cross-border returns sit at the expensive end, because freight and customs stack on top of everything else.
The lesson is not to make returns harder. It is to stop treating every return as the same cost. Once you cost them per type, the policy writes itself, and knowing your good return rate by category tells you where you stand.
Turning cost data into decisions
Adding up the true cost is not an accounting exercise. It is how you decide what to change. When you see cost per return by SKU, patterns jump out: a handful of products drive most of the expense, usually for a repeatable reason like sizing or damage. Fix the reason and the cost falls, which is the core of reducing your return rate.
Pango is what makes that data legible. It surfaces return reasons and patterns by SKU, so you see which products drive the cost and why, and turn a vague cost center into a list of specific, fixable line items. The other lever is what happens to the return itself: turning a refund into an exchange recovers the revenue on the returns you cannot prevent, and a branded tracking page that normalizes carrier statuses cuts the WISMO tickets that pile hidden support cost on every delayed return.
The bottom line
A return is a stack of costs, most of them invisible because they live in different systems. Put returns, exchanges, tracking, and analytics on one layer and the stack becomes a number you can see per SKU, and a number you can see is a number you can cut. Pango runs that layer, surfaces the cost drivers, and turns refunds into exchanges where it makes sense, with a full per-return cost model built to fit your warehouse and refund data. For the system behind it, see what a return management system is, or book a demo to see your own numbers.
