Reasons for returning an item, and which ones are yours
Verified & Reviewed
Copy Link
What a return reason actually records
The reasons for returning an item are the causes a customer gives, or a seller records, for sending a delivered order back. The consensus set is short: it doesn't fit, it's not what the listing described, it arrived damaged, the wrong item was sent, it arrived too late, or the customer changed their mind. My read, after years of running operations for brands that outgrew their warehouse: those aren't one list. Some of them are a customer's preference, and some of them are your own operation reporting a failure back to you, and almost every guide on this subject treats the two as the same thing. The return that opens with "wrong item" started days earlier at a pick face, and the scan that put the wrong SKU in the box sat in your warehouse record the whole time; by the time anyone reads the reason code, the refund, the replacement and the ticket have all been paid for.
The reasons customers give
Pool the reason lists the platforms and the returns guides publish, and the same eight come back.
- It doesn't fit: size or cut, measured against a body the listing never saw.
- It's not what the listing described: the color, material or spec doesn't match the page that sold it.
- It arrived damaged or faulty: broken in transit, or it failed the first time it was used.
- The wrong item was sent: a different SKU, a different size, or somebody else's order entirely.
- It arrived too late to be useful: the birthday or the event the purchase existed for has passed.
- They changed their mind: buyer's remorse, a duplicate purchase, or two sizes ordered to keep one.
- It didn't meet expectations: it works and it fits, it's just not worth what it cost.
- It was never a real return: wardrobing and return fraud sit at the end of every list.
These aren't folklore, they're the values the tooling actually offers. Shopify's Admin API defines ten return reasons, two of which are OTHER and UNKNOWN, and the merchant-side list varies by product category, so apparel offers Too big and Too small where other categories do not.
Some of those reasons are yours
Sort that list by what caused the return instead of by what was in the box, and it stops being one list.
- Reasons the customer chose: fit, style, color, changed their mind, bought two to keep one. Legitimate, expected, and a demand problem.
- Reasons you caused: the wrong item was picked, the parcel was damaged in transit, the order shipped short, the delivery landed after the date you promised. Every one of them was visible in a warehouse record or a carrier scan before the return request existed.
The second pile has a resolution that's not a refund, and it's available weeks earlier: a replacement sent on detection, a credit issued on the spot, an intercept while the parcel is still moving. One in five orders hits an operational break after checkout, and a delivery exception is one of the few that ever gets a name. The measured piece comes from the Postal Service's own auditor, which found more than 11.6 million undeliverable Parcel Select packages scanned return to sender in FY2024, carrying about $138 million in return postage, and only 39 percent reached the sender. Not one of those is a change of mind.
The reason code is not the reason
An operations lead meets the problems with the reason field the first time they try to use it. The field is customer-declared, and the person filling it in wants their money back quickly, not an accurate root cause. What they're allowed to say is picked from a list somebody else wrote: ten values on Shopify, two of them OTHER and UNKNOWN. Those options change by product category, so your apparel reasons and your homewares reasons are different alphabets and won't stack up against each other. And all of it arrives too late to act on, because the reason is collected when the return is requested, days or weeks after the break that caused it.
So a reason report tells you what customers said, aggregated over a quarter. It can't tell you which order broke, or when, or whether anything could still be done about it. That record sits upstream, in the order, the fulfillment events and the carrier scans. Your order management system holds the state of the order. The reason field holds the story the customer told about it afterwards.
One of these reasons has a legal clock on it
Arrived too late is filed everywhere as a soft problem to fix with a better carrier. In the US it's a compliance event.
- Under the FTC's Mail, Internet, or Telephone Order Merchandise Rule a seller must ship within the advertised window or 30 days, and if it cannot, it must offer the buyer the choice to consent to the delay or cancel.
- Once the right to a refund vests, it must be sent within seven working days for cash or check, or one billing cycle on credit.
- The policy you post governs a change-of-mind return, and some states make the posting itself the obligation: California holds a retailer that fails to post conspicuously liable to a buyer returning on or before the 30th day after purchase.
Outside the US it inverts: a UK consumer may cancel a distance contract without a reason, which is worth knowing before you build a process on top of a reason field. The late delivery was already a broken promise on the day it slipped, and the WISMO ticket said so first. The return is just the invoice arriving.
What to watch instead of the list
Two numbers are worth more than the whole reason report, and neither is on your dashboard today. The first is the share of your returns that opened with a brand-caused reason: tag every value in your reason list as customer-chosen or brand-caused on the day you configure it, and you read one number instead of the whole list. The second is the gap between the break and the return request, the days between the warehouse or carrier event that caused the return and the moment the customer asked for one. That gap is the window you had and didn't use.
Both are worth the configuration because of the scale sitting behind them. Online is a channel worth 16.9 percent of total US retail sales in the first quarter of 2026, the National Retail Federation expects 19.3 percent of online sales to be returned in 2025, and USPS OIG has put e-commerce return rates at about three times physical retail. Your RMA process starts long after all three of those numbers were decided.
Why a helpdesk cannot act on the reasons you caused
A helpdesk receives the reason after the customer types it, and answers the customer. It doesn't reship the right SKU, release the credit or stop the parcel. It's a system for replying about problems, not resolving them, and no amount of response time turns it into the other thing.
The category that acts is proactive e-commerce operations, and its mechanism is detect, decide, act. We detect the break in the warehouse record or the carrier scan, decide the resolution against your policy, and act before the customer opens a return.
Here's what we're not. Keeyu isn't a returns portal, not a helpdesk, not a carrier and not an OMS. We don't build your reason dropdown, collect the reason, grade the item or restock it. What we act on is the break that produced the reason. Every order is a promise, and the reasons you caused are a promise that broke before the box came back.
Fix the reasons you caused before the customer picks one
The mis-picked SKU, the parcel damaged in transit, the delivery that slipped past the date you promised: none of those is a customer preference, and none of them should have to reach a reason dropdown to be counted a quarter later. Keeyu watches every order for the break that causes them, decides the fix against your policy, and acts on it, usually before the customer knows anything went wrong. Book a demo and bring your return reason report.
Frequently Asked Questions
What are the most common reasons for returning an item?
Eight reasons cover almost every return: it doesn't fit, it's not what the listing described, it arrived damaged or faulty, the wrong item was sent, it arrived too late to be useful, the customer changed their mind, it didn't meet expectations, and the small share that was never a genuine return at all. The useful way to read that list is by cause. Fit, style and a change of mind are customer choices. A mis-picked SKU, a damaged parcel and a late delivery are operational breaks in your own order, and the customer is reporting them back to you.
What are valid reasons to return an item online?
In the US there's no fixed federal list of valid reasons for a change-of-mind return. Validity is set by the seller's posted policy, which is why two stores can refuse and accept the same return. Some states go further and make the posting itself the obligation: under California Civil Code 1723 a retailer that fails to post its refund policy conspicuously is liable to a buyer returning on or before the 30th day after purchase. Faulty, damaged and misdescribed goods are treated separately and are covered by consumer protection law rather than by store policy.
Do I have to give a reason to return something?
It depends where you bought it. In the US the seller's posted policy governs, and most policies ask for a reason from a dropdown even though there's no general federal right to return unwanted goods. In the UK a consumer buying at a distance may cancel the contract without giving any reason within the cancellation period, subject to named liabilities for enhanced delivery and diminished value. The reason field is a business artifact, not a legal requirement.
What is the most common reason for returning clothing?
Fit. The clearest evidence is structural rather than survey based: platform return reason lists are category-specific, and Shopify's merchant documentation notes that the reasons a merchant can choose from vary by product category, with apparel offering Too big and Too small where other categories do not. Sizing is the one variable the tooling itself is built around, which tells you where apparel returns concentrate.
How should I categorize return reasons on my return form?
Mirror your platform's own values first so the data stays comparable across your catalog. Shopify's Admin API defines ten return reasons, two of which are OTHER and UNKNOWN. Then add one tag of your own to every value: customer-chosen or brand-caused. That second tag is the one that changes what you do, because it separates the returns you can only reduce with a better product page from the returns you could have prevented with a fix to the order.
Is a late delivery a valid reason for a refund?
In the US, often yes. Under the FTC's Mail, Internet, or Telephone Order Merchandise Rule a seller must ship within the advertised window or 30 days, and if it can't it must offer the buyer the choice to consent to the delay or to cancel. Once the right to a refund vests, the refund must be sent within seven working days for cash or check, or one billing cycle where the purchase was made on credit. A late delivery isn't only a return reason, it's a compliance event.
How many returns are caused by the retailer rather than the customer?
Most merchants never tag their own reason values by cause, so the split sits untagged in their own returns table. The nearest measured piece is a government audit. USPS OIG found more than 11.6 million undeliverable Parcel Select packages scanned return to sender in FY2024, carrying about $138 million in return postage, with only 39 percent reaching the sender. None of those came back because somebody changed their mind.
Does collecting return reasons reduce returns?
No. The reason is collected after the return already exists, usually days or weeks after whatever caused it, and a report of what customers said last quarter can't tell you which order broke or when. Collecting reasons well makes the pattern legible, which is worth doing. The returns that actually disappear are the ones prevented upstream, where a mis-pick, a short shipment or a delivery running past its promised date is detected and fixed before the customer ever opens a return.
References
- US Census Bureau. Quarterly Retail E-Commerce Sales. E-commerce at 16.9 percent of total US retail sales in the first quarter of 2026.
- Shopify. Admin GraphQL API, ReturnReason enum. The ten values a return can carry, including OTHER and UNKNOWN.
- Shopify Help Center. Creating and managing returns. Return reasons vary by product category, with apparel showing Too big and Too small.
- USPS Office of Inspector General. Protecting Revenue for Returned Parcel Select Packages (25-053-R25). More than 11.6 million undeliverable Parcel Select packages in FY2024, about $138 million in return postage, and 39 percent reaching the sender.
- USPS Office of Inspector General. Riding the Returns Wave (RARC-WP-18-008). E-commerce return rates running about three times those of physical retail.
- National Retail Federation. 2025 Retail Returns Landscape. 19.3 percent of online sales expected to be returned in 2025.
- Cornell Legal Information Institute. 16 CFR 435.2. The shipping window, the 30-day default, and the seller's duty to offer consent to a delay or cancellation.
- Cornell Legal Information Institute. 16 CFR 435.1. Prompt refund defined: seven working days for cash or check, one billing cycle for credit.
- California Legislative Information. California Civil Code 1723. Conspicuous posting of the refund policy, and liability to a buyer returning on or before the 30th day after purchase.
- UK legislation. Consumer Contracts Regulations 2013, regulation 29. A consumer may cancel a distance contract without giving a reason.
Ready to Stop Reacting?
The fastest way to see how Keeyu prevents complaints is to see it in action.
In one call, we’ll map your current operations, show how our AI Agent fits in, and walk through real examples of issues fixed before customers notice.
Most teams go live within 48 hours. We never share your data.
