How Wardrobing and Return Fraud Show Up in Apparel Resolution Data

Not every return in your apparel store is a fit problem. Some are a one-time rental the customer never paid for, and most merchants only find out after the item has already been worn and returned for a full refund.

Wardrobing hides inside a policy built for good customers

A customer who buys a dress for a wedding, wears it once, and returns it within the window has done nothing that trips a standard fraud filter. This is a policy exploitation problem, not a traditional fraud problem.

Three signals that separate habitual wardrobing from a real fit issue

Return timing

Genuine fit issues tend to come back fast. Wardrobing tends to cluster near the end of the return window, often right after a specific event.

Return frequency per customer

A pattern of returns from the same customer, concentrated in dresses, suits, or other single-occasion categories, tells you a great deal.

Condition-on-return signals

Genuine fit returns usually come back in near-new condition. Worn items tell a different story: deodorant marks, perfume, creasing, missing tags.

Why lumping wardrobing in with fit returns costs you twice

Merchandising draws the wrong conclusions about sizing, and customers genuinely struggling with fit get lumped in with habitual wardrobers when a merchant clamps down.

Turning resolution data into a policy, not a suspicion

Once timing, frequency, and condition are tracked together, a merchant can build tiers instead of guesses, giving the operations team a defensible, data-backed reason for how a resolution gets handled.

Where this fits in the post-purchase stack

This requires the return and resolution data a brand already generates to be structured so timing, frequency, and condition can be compared across customers and over time.

ShipAid's Shipping Guarantee for Apparel Brands gives merchants that structured resolution layer on Shopify, so these signals show up as usable data instead of scattered notes across support tickets.