Return Reason Codes: How to Set Them Up

To set up return reason codes, write a short list of reasons that do not overlap, give each one a code, and make the shopper pick exactly one on your returns form. Then record the code with every return so you can count them later.

Codes turn free-text complaints into data. They are the first step before you can use AI size recommendation for fashion stores or any sizing change to its full effect, because you need to know which returns are about size.

What is a return reason code?

A return reason code is a short label, such as SZ-S for "too small", that you attach to a return. The code can be a number, a short word or a mix.

An RMA (return merchandise authorization) is the approval and tracking number for the whole return. The reason code is a separate field on that RMA. Many stores use both.

Why do fashion stores need them?

Fashion returns have mixed causes: size, quality, color, style and shipping damage. Without codes, these blend into a single number and you cannot see which cause is growing.

With codes, you can answer questions like "which product gets the most 'too small' returns?" The guide to analyzing return reasons by product shows how to read the data once you have it.

How do you build the list step by step?

1. Start from real returns. Read your last batch of returns and write down the reasons shoppers gave in their own words.
2. Group them. Put similar reasons together, such as "too tight" and "too small."
3. Remove overlaps. Each reason should mean one thing, so a return fits in only one group.
4. Keep it short. A long list makes shoppers pick "other."
5. Assign codes. Give each group a short code with a prefix for the type.
6. Test it. Have two team members code ten past returns each and compare answers.

If the two of you disagree often, the list has overlaps. Rewrite those reasons.

What should the starter list include?

Here is a list you can adapt. It is an example for a fashion store, not a standard.

Code	Reason shown to shopper	Bucket
SZ-S	Too small	Fit
SZ-L	Too large	Fit
SZ-LEN	Wrong length	Fit
QL-DEF	Faulty or damaged	Quality
QL-WRG	Wrong item sent	Operations
EX-CLR	Color not as expected	Expectation
EX-FAB	Fabric not as expected	Expectation
EX-STY	Style not as expected	Expectation
CH-MND	Changed my mind	Other
CH-DUP	Ordered more than one size	Other

The prefix shows the bucket, so you can group codes with a simple filter. The buckets match the split described in quality complaints vs fit complaints.

Why separate "ordered more than one size"?

Some shoppers buy two sizes on purpose and return one. That is not a fit failure, so it deserves its own code. Otherwise it inflates your "too large" count.

How do you put the codes on a returns form?

Show shoppers plain words, not codes. Keep the code internal, and map each reason to it behind the scenes.

Follow these form rules:

• Single choice. Make the shopper pick one reason.
• Plain wording. Use "Too small," not "SZ-S."
• Optional note. Add a short text box for details.
• Size follow-up. If the shopper picks a fit reason, ask which size they ordered and which they think would fit.
• Photo upload. Let them attach a photo for damaged or faulty items.

The size follow-up is the most useful field. It shows whether your size chart runs small or large.

How do you keep the codes clean over time?

Review the list every few months. If "other" grows into a large part of your returns, read the notes and add a new code.

Do not delete old codes. Retire them from the form but keep them in your records, so past data stays readable.

Check that your team uses the codes the same way. When a staff member processes a return by hand, they should pick the code that matches the shopper's reason, not what they think the cause was.

What do you do with the data?

Count returns by code and by product. A product with many "too small" returns may have a chart problem. The guide to when to pull a product based on return rates covers that decision.

Then look at the product page itself. A good page gives measurements, fit notes and photos before the shopper buys, and the product page checklist for fashion stores lists what to include.

For fit returns, a size recommendation based on your own size chart gives shoppers a label before they order. You can test it on the Free plan, which includes 3 measurements a month.

FAQs

How many return reason codes should I have?

Keep it to around ten or fewer. A longer list pushes shoppers to choose "other" and makes your data less useful.

Should shoppers see the codes?

No. Show plain wording and keep the code internal.

Can I use free text instead of codes?

Free text is useful as an extra note, but it is hard to count. Use codes for counting and a text box for detail.

What is the difference between a reason code and an RMA?

An RMA identifies the return as a whole. A reason code says why the shopper is returning the item.