A 9% return rate isn’t costing you 9%.
It’s costing you 15–20% in operational expenses and you don’t have any clue how.
That 15–20% is not due to processing fees or reverse shipping, though those are real costs.
It’s because your return rate is not a returns problem.
It’s two problems running at the same time and feeding each other.
And you are probably not looking at either of them.
Why?
Because it’s just the return rate you are fixated on… because that’s what’s on the dashboard.
The Belief That’s Costing You
Here’s what most DTC founders do.
They see the return rate go up, they think customers are unhappy, margins are shrinking, and they tighten the return policy.
That feels like action. But it’s solving the wrong problem.
Because your return rate didn’t start when your customer sent the product back.
It started when your fulfilment process sent the wrong product out or when a supplier decision put a product in the customer’s hands that looked or felt nothing like what they ordered.
The return is the receipt. The fulfilment failure is the transaction.
And by the time the receipt arrives, you’ve already paid twice: once when the process broke, and again when you process the return.
Problem 1: Returns Are Breaking Your Fulfilment Efficiency
This is the problem nobody connects to returns — and it quietly gets worse every month.
When a return comes back into your warehouse, it doesn’t slot neatly back into your inventory. It enters a queue. And that queue is where your fulfilment efficiency starts breaking down.
Your inventory count becomes unreliable. The returned unit is back in the building but it’s not back in stock. It’s waiting for inspection. Your system may already be counting it as available. Your team is making reorder decisions on a number that includes units that aren’t actually sellable. You think you have 200 units. You have 160.
Damaged and used returns don’t go back to sellable stock. Some returns come back damaged. Some come back used. Some come back with missing tags or opened packaging. Each of those units needs a decision — can it be discounted, bundled, written off, or thrown away? Until that decision is made, it sits. And sitting inventory costs money every single day.
Processing takes time nobody has budgeted for. Every return needs to be inspected, re-barcoded if it passes, added back to warehouse stock, or disposed of if it doesn’t. That is warehouse labour, time, and attention that is not going toward outbound fulfilment. The higher the return volume, the more your warehouse is running in two directions at once — and the more your outbound efficiency suffers.
The biggest bottleneck: decision delays. Damaged stock, supplier disputes, write-off approvals — these all need a decision from someone senior. And senior people are busy. So the returned stock sits in limbo. The queue grows. The inventory count stays wrong. And every downstream decision — reorders, cash flow, campaign timing — is being made on data that includes functionally unavailable units.
This is how a 9% return rate becomes a fulfilment efficiency problem. Not because of the returns themselves — but because of what happens to them when they come back in.
Problem 2: Returns Are Destroying Customer Trust — Before the Return Even Happens
Here’s the part that never shows up in your return rate calculation.
Most returns aren’t triggered by a customer changing their mind. They are triggered by a fulfilment failure — the wrong item in the box — or a quality failure — the product that arrived looked or felt nothing like what was ordered.
At IndiaRush, we experienced this firsthand. A supplier decision on a specific product category — a change in material that looked acceptable on a sample but failed at scale in bulk production — created a return spike we couldn’t explain until we traced it back to the source. The customers weren’t being difficult. The product had changed without the listing changing. The expectation was set in the photograph. The reality arrived in the box.
By the time a customer contacts you about a wrong item or a quality issue, the trust is already fractured. Not completely broken — but fractured. They’re giving you a chance to fix the immediate situation — the return, the refund, the replacement. Most brands do fix that part.
But the customer has no way of knowing whether you fixed what caused it. They don’t know if the supplier was changed, the listing updated, or the fulfilment process tightened. From where they sit, they ordered something, it failed them, and the brand handled the complaint.
So when they consider ordering again, they’re not just weighing your product against their need. They’re weighing it against the memory of the last time — the wrong item, the quality that didn’t match the photograph. You never told them things changed. So why would they risk it?
That’s why the next order doesn’t come.
The Connection Nobody Makes
Your return rate is not a customer behaviour metric. It’s an operational health metric.
Every spike in your return rate is telling you one of two things — or both at the same time:
- Your fulfilment process is sending out the wrong things
- Your supplier decisions are creating a gap between what you show and what you ship
Fix the upstream failure and the return rate drops. The fulfilment efficiency recovers. The customer trust rebuilds.
Keep managing the downstream symptom — faster refunds, better return policies, more support agents — and the rate stays where it is, the efficiency stays broken, and the trust keeps eroding one wrong item at a time.
Your return rate is 9%. Your fulfilment process and your supplier decisions are the inputs that determine whether that number goes to 6% or climbs to 14%.
Those are the leading indicators. The return rate is just the lagging number telling you how those inputs have been performing for the last 90 days.
3 Things You Can Do This Week
Step 1: Pull your top 3 return reasons by volume Not the total return rate — the specific reasons. Wrong item, quality issue, not as described, sizing. Rank them. The top reason is where your fix lives. Wrong item means your fulfilment process. Quality or not as described means your supplier or your listing.
Step 2: Calculate your returns processing backlog How many returned units are currently sitting in your warehouse unprocessed — not yet inspected, not yet added back to stock or written off? That number is your inventory count error. Every reorder decision you make while that backlog exists is being made on corrupted data.
Step 3: Trace your last return spike to its source Pick the month where your return rate was highest in the last 12 months. Pull the top SKU driving that spike. Ask one question: what changed upstream for that SKU in the 4–8 weeks before the spike? New supplier, new batch, new listing, new fulfilment team member. Something changed. Find it.
The Question Worth Sitting With
You look at your return rate every month. But are you asking the right question?
Most founders ask: how do I reduce returns?
The question that actually fixes the problem: what did my fulfilment process or my supplier decisions do in the last 90 days that my customers are now sending receipts for?
One question manages a symptom. The other fixes the source.
Book a free 30-minute Operations Maximizer session → calendly.com/arti-retainup-core5-os/operations-maximizer-strategy-session
Arti is a fractional COO and eCommerce operations consultant helping DTC founders in the $3–8M range identify and fix the six operational leaks quietly draining their cash — using the CORE5 OS framework built from scaling and closing a $20M DTC brand.