How many return reason codes should a retailer offer customers?

Six to eight. More than that and customers choose randomly to finish the form, which destroys the data. Keep the customer list short and shopper friendly, and put the detailed classification in the warehouse inspection layer instead.

Why separate customer reasons from warehouse findings?

Because they measure different things and often disagree. The customer reports a story, inspection records physical condition. The gap between the two, by category, is one of the most useful audit signals a retailer has, and it only exists if the layers stay separate.

Can reason codes detect wardrobing on their own?

No single code can. Wardrobing shows up in the combination of inspection findings, return timing, and customer history. That is why risk flags should be derived analytically from all three layers rather than collected as a form field.

How often should a returns taxonomy be reviewed?

Quarterly is a good rhythm. Remove codes nobody selects, split codes that have grown to cover too much, and check that every code still has an owner and a decision attached to it. Taxonomies decay quietly without a review habit.

Why separate returns abuse by channel in an audit?

Because the abuse profiles, the data available, and the fixes all differ. Direct store abuse is repeat and account based. Marketplace abuse is more opportunistic and listing driven. Blended numbers hide migration between channels and point enforcement at the wrong target.

Can retailers act on abusive marketplace accounts?

Only within the platform's rules, which usually means evidence based disputes, listing fixes, and reporting rather than direct account action. That limitation is exactly why marketplace prevention has to focus on listings, expectations, and documentation.

Which channel usually has worse wardrobing?

It varies by category, but occasionwear sold through marketplaces often shows higher one time wardrobing because platform return norms feel anonymous and frictionless. Direct stores tend to show more repeat, habitual patterns. Your own channel split data is the only version worth acting on.

How often should channel abuse be reviewed?

Quarterly is a practical rhythm, with a closer watch after any policy change in either channel. Abuse migrates toward the softer policy, and a quarterly review catches the shift while it is still small enough to address cheaply.

How often should a marketplace seller audit returns?

Quarterly is a workable rhythm for most sellers, with a quick monthly glance at returns cost by category. Audit immediately after any spike in returns rate or a platform policy change, because both can shift which products are profitable to list.

What is the single most useful marketplace returns metric?

The unsellable return rate by category: the share of returned items you cannot resell at full value. It captures wear abuse, damage, and missing components in one number, and it points directly at the listings and categories to fix first.

Can I refuse returns as a marketplace seller?

On most platforms, only within narrow limits, and your settings affect search placement and account health. The practical lever is not refusal but documentation and listing quality, plus moving chronically abused products off the platform.

What is resale channel leakage in returns?

It is returned or written off stock leaving your controlled channels and being sold elsewhere, usually at a discount, without your authorization or revenue share. It differs from legitimate outlet and liquidation sales, which are recorded channels with agreed pricing and reporting.

How can I tell if a resale listing is leaked stock?

Look for volume, range, and timing: multiple units of a current item across sizes, new with tags, listed below your price shortly after a returns peak. Style codes and packaging details visible in photos help connect listings to your stock rather than to ordinary customer resales.

Should I confront a seller listing our stock?

Document first, act second. Archive the listings with dates and photos, trace the likely source internally, and involve your legal or marketplace reporting channels rather than messaging the seller directly. Premature contact mostly teaches the source to hide better.

Auditing Bracketing Returns: When Fit Data, Not Fraud, Is the Problem

October 17, 2026

Bracketing is the practice of ordering two or three sizes of the same item and returning the ones that do not fit. It inflates return rates, ties up inventory, and can cost more than wardrobing in some categories, but it is not fraud: the customer keeps and pays for an item. Auditing bracketing means measuring how much of it your own size information causes, through inconsistent sizing, missing measurements, and reviews you never mined, and fixing those causes instead of punishing the behavior.

Measure bracketing separately or not at all

Start by isolating true brackets: the same customer, the same style, two or more sizes, one kept, in one order or a tight window of orders. Most return dashboards bury brackets inside the general return rate, which makes fit problems look like fraud problems and sends the loss prevention team chasing your most honest customers.

Report the bracket rate by category and by style, not chainwide. A chainwide average hides the story: one badly sized shoe line can produce most of a networks bracketing, while the rest of the catalog fits the way customers expect. The audit unit is the individual style, because that is where the fix will happen.

Interrogate your own size information

For each high bracket style, audit what the customer was told: Is there a size chart, and is it this brands chart or a generic one? Are garment measurements given, or only body measurements? Do reviews mention runs small or runs large, and has anyone read them this season? Missing or wrong information at this level manufactures brackets at scale.

Then check consistency across your own range. If your size medium dress measures like a competitors small, returning customers will bracket even when first time customers do not, because their learned size betrays them. A simple audit of actual garment measurements across the top returned styles finds these traps within a week.

Tell bracketing from wardrobing in the data

The two patterns share a high return rate and nothing else. Bracketers keep an item from almost every order, return unworn extras quickly, and their returns show no wear on inspection. Wardrobers keep nothing from event category orders and return items with wear signs after event dates. Mixing them in one metric produces policies that annoy the first group and miss the second.

Use the kept item as the pivot in your reporting: accounts and orders with a kept item are a fit story until proven otherwise. That single distinction should route bracketing to the ecommerce and product teams, where it belongs, and keep it out of fraud queues entirely.

Fixes that actually reduce brackets

Publish garment measurements for high bracket styles, add fit notes written from returns data, and surface review based guidance like eighty percent of buyers say this runs small at the moment of size selection. Each fix is cheap; together they routinely cut bracketing in a problem category by a third or more within a season.

Reserve policy friction for the extreme tail: accounts bracketing nearly every order with nothing kept are not bracketing at all, and the data review will show it. Everyone else is telling you your sizes are hard to predict. An audit that ends in better size information pays for itself; one that ends in customer penalties just exports the sale to a competitor with a clearer chart.

Keep reading on this site: Auditing returns resale channel leakage, Auditing damaged return claims, Return fraud audit marketplace sellers. Each of those pieces connects to the ideas above and gives more detail on the parts this guide could only summarize.

Frequently asked questions

Is bracketing a form of return fraud?

No. Bracketing is a rational response to uncertain sizing: the customer pays for and keeps an item. It becomes a problem worth managing because of shipping, handling, and inventory costs, not because of dishonesty. Treating bracketers like fraudsters is both unfair and ineffective, since the cause is usually the retailers own size information.

How can we tell how much bracketing a style causes?

Look at the share of multi size orders for that style and the direction of the keep: if customers systematically keep the size up, the style runs small and the chart or the cut is lying. Random keeps in both directions suggest normal fit uncertainty. Systematic keeps are a measurement confession.

Should retailers charge for return shipping to stop bracketing?

It reduces bracketing, but bluntly: it also reduces first orders from new customers who cannot predict your sizing. Targeted versions work better, like free exchanges for a different size, which attacks the fit problem directly and keeps the kept item rate high.

What is a healthy bracketing rate?

It varies by category: footwear and tailored clothing naturally bracket more than basics. The useful comparison is your rate per style against its own history and against similar styles in your range. A style bracketing at twice the rate of its neighbors is the audit finding, whatever the absolute number.