# The refund-without-return trap: when it saves money and when it gets abused | ReturnWarden

Source: https://returnwarden.com/blog/2026-09-30-refund-without-return-abuse.html

September 30, 2026

Refunding a fifteen-dollar item without asking for it back is usually the right call. The return shipping alone can exceed the item's margin, and the warehouse labor to receive, inspect, and restock it turns a small loss into a bigger one. Keep-it refunds are good economics, which is exactly why abusers study them.

The trap is predictability. The moment customers can figure out which items always get refunded without a return, a subset of them starts ordering those items with no intention of keeping them. The policy that saved you money in aggregate starts funding a small group of regulars.

## How keep-it refunds get farmed

The pattern is consistent across apparel brands. An account places several small orders, reports a defect or wrong item on each, and receives keep-it refunds every time. After three or four successes, the account scales up: more orders, more complaints, all on SKUs under the keep-it threshold. The items are kept, worn, or resold; the refunds are pure profit.

What makes this hard to catch is that each individual case looks reasonable. A fifteen-dollar refund is not worth investigating on its own. The abuse is only visible in aggregate: the same account, the same complaint type, a refund rate far above the customer average, all concentrated under the threshold.

## Set the threshold from your real costs

Most brands set the keep-it threshold by gut feel: twenty dollars, thirty dollars, whatever feels small. The right number comes from your actual reverse-logistics cost: average return shipping plus warehouse processing time plus restock or disposal cost. If that total is twelve dollars, a twenty-dollar threshold is giving away eight dollars of margin on every keep-it refund.

Revisit the number quarterly. Shipping rates change, warehouse costs change, and your product mix changes. A threshold that was correct last year can quietly become a subsidy.

## Randomize and cap: the two controls that matter

Predictability is the vulnerability, so remove it. Randomly require returns on a percentage of below-threshold refunds, even five to ten percent. The random check does two things: it verifies the item was actually defective, and it tells anyone farming the policy that the rules are not automatic.

Then cap keep-it refunds per account per quarter. Two per quarter is generous for honest customers and ruinous for farmers, because the farming model needs volume. Accounts that hit the cap get routed to standard returns with inspection, which is exactly the friction that makes the scheme unprofitable.

## Track the keep-it rate like a fraud metric

Your overall keep-it rate should be stable. When it climbs, segment it: by account, by SKU, by complaint reason. Abuse concentrates, so the segment view finds it fast. A SKU with triple the average keep-it rate is either genuinely defective, in which case quality has a problem, or it is being farmed, in which case fraud has an opportunity.

Watch especially for new accounts with immediate keep-it refunds. An honest first-time buyer rarely reports a defect on order one. A farmer's first order is often the start of the pattern.
