WardrobeAudit

Auditing Try Before You Buy Returns: Where the Model Leaks

October 22, 2026

Try before you buy programs let customers receive items, decide at home, and pay only for what they keep, which makes their returns fundamentally different from ordinary returns: a high return rate is the design, not a defect. Auditing such a program with normal return metrics produces nonsense, a sixty percent return rate that looks like a crisis and is actually the model working. The leaks that matter are subtler: items worn beyond a fair trial and returned, keep rates drifting by category in ways that reveal sizing or photography problems, and trial periods quietly stretching past the stated window. This audit framework measures those instead.

Audit the keep rate by category, not in total

The headline number hides everything. Compute keep rates by category, by price band, and by size, and look for the outliers in both directions. A category with a keep rate far below its peers usually has a fixable cause: a size curve that runs small, photography that misstates color, or a fabric that disappoints in hand. Those are merchandising findings discovered through the audit, and they are worth more than the return savings.

A suspiciously high keep rate deserves the same attention. It can mean the trial friction is doing the deciding: return shipping that is annoying, a window too short to decide calmly, or charges that land before the reminder email. Customers keeping things they do not want is not success; it is tomorrow's chargebacks and resentment, and the audit should say so.

The worn trial problem

Every try before you buy program quietly answers a question: how much use is a fair trial? Trying on at home is the offer; wearing to an event is wardrobing with a permission slip. Auditing means defining the line in condition terms the inspection team can apply: tags, soles, scent, and wear marks, scored the same way as ordinary return inspections.

Sample before you accuse. Pull a random sample of returned trial items monthly and grade their condition blind. That gives the program a defensible wear rate: a percentage, trended over time, that tells you whether the problem is growing and whether it concentrates in categories, price bands, or event seasons. Programs that skip sampling end up arguing from anecdotes.

Timing and window discipline

Trial windows leak at the edges. Measure the actual distribution of return ship dates against the stated window: how many returns leave on the last day, how many after it, and how often extensions are granted. A window that is routinely extended by support, however kindly, is a longer window being run without the pricing decision that should accompany it.

Also audit the charge timing. Customers should never be charged for an item whose return is already in transit, and the audit should verify, with real order examples, that the system honors tracking scans rather than calendar deadlines. Few things destroy trust in a trial program faster than a charge for a box the carrier already has.

What a healthy audit report looks like

A good quarterly audit fits on one page: keep rate by category with the two outliers explained, the sampled wear rate with its trend, window compliance percentages, and the count of disputed charges with their resolution times. Each number has an owner and a threshold that triggers action, agreed before the numbers arrive.

Close the loop by publishing findings to the teams that can act: sizing notes to product, photography fixes to creative, window and charge fixes to operations. An audit that ends in a dashboard nobody reads is overhead; an audit that changes three decisions a quarter is one of the cheapest improvement tools the program has.

Keep reading on this site: Auditing bopis returns, Auditing gift receipt returns, Auditing empty box claims. Each of those pieces connects to the ideas above and gives more detail on the parts this guide could only summarize.

Frequently asked questions

What keep rate should a try before you buy program expect?

It varies widely by category, with apparel often keeping a third to a half of trialed items. The right benchmark is your own category history and margin math: model the keep rate the program needs at your shipping and inspection costs, then audit against that line, not a generic figure.

How do we stop people wearing trial items to events?

Mostly through condition auditing and clear terms: state what a fair trial means at checkout, inspect and document returned condition consistently, and act on repeat patterns at the account level. A small, visible enforcement rate deters far more than it catches.

Should trial returns be inspected differently from normal returns?

The condition standard should be the same; the interpretation differs. A normal return of a worn item is an exception; in a trial program some handling wear is expected. Grade both with the same rubric and compare the distributions, not individual items, to judge abuse.

What is the most common hidden cost in these programs?

Round trip shipping on low keep rate categories, with inspection labor close behind. The audit usually finds the program is healthy in aggregate and underwater in two or three categories, which is where category level keep rate reporting earns its keep.