Returns management process for online stores: 9 steps

Returns are normal in fashion, but they become expensive when each request is handled differently. A repeatable workflow helps you decide faster, communicate more clearly, and use return data to fix the products, size charts, photos and product descriptions that cause most problems.

Below is a nine-step returns management process for online clothing stores: policy, request form, reason codes, approval rules, shipping labels, inspection, restocking or write-off, refund or exchange, and logging. It applies to international Shopify and WooCommerce stores, as well as smaller Haravan and Sapo shops in Vietnam.

Start with a written return policy that removes ambiguity

Before customers request a return, the rules should already exist. A clear policy prevents arguments and makes approval decisions mechanical instead of emotional.

Include at least these points:

Some markets have mandatory return or exchange rights for online purchases. Do not copy a strict policy from another country without checking the current consumer-protection rules that apply to your customer’s location. For Vietnamese shops, check the current official rules on online purchases and defective goods before stating that certain items cannot be returned.

Publish the policy on a dedicated returns page, in the footer, in the order confirmation email, and on product pages for items that are final sale.

Build a return request form with structured reason codes

The request form is where you collect usable data. Avoid a free-text email that says only “I want to return it.” Use a form that asks for order details, the item, the reason, a photo and the customer’s preferred resolution.

A practical form includes:

• Order number or the phone/email used at checkout
• Which item or items the customer wants to return
• Quantity per item
• Reason code from a dropdown
• Optional sub-reason, such as “too tight across the chest” or “too long”
• Photo upload, mainly for damage or wrong-item claims
• Preferred outcome: refund or exchange
• Additional note

Use reason codes from day one. Common codes for fashion stores:

• Size too small
• Size too large
• Fit is off, but size is correct
• Looks different from the photo
• Material feels different from the description
• Damaged on arrival
• Wrong item sent
• Changed mind
• Other

For size issues, add sub-codes for chest, waist, hips, length, shoulders or height. That gives you data to adjust size charts later.

Platform setup notes

• Shopify: In the admin area, create a page under Online Store > Pages and add a form app or return portal app. Many Shopify stores use a returns app that lets customers look up an order and submit a request. If you prefer manual, add an HTML form that sends requests to a shared email.
• WooCommerce: There are several returns and warranty plugins that let customers submit requests from an account or order page. You can also create a page with a form builder that sends the data to a returns mailbox. If using a plugin, make sure it creates a request entry your team can update with approval status.
• Haravan or Sapo: Use the built-in page builder or an HTML block to embed a Google Form, Typeform or equivalent return request form. Link the form from your order confirmation email and customer account menu if available. Because these platforms run on HTML templates, you can usually edit the theme or page content directly.

Photo: cottonbro studio / Pexels

Set reason-based approval rules instead of asking staff to guess

Once the request arrives, the next step is deciding whether to approve it. Staff should not have to make a moral judgment each time. Predefine rules based on reason code, photos and order history.

Example decision rules:

When a customer uploads a photo showing a damaged seam, stain or wrong item, the best move is usually fast approval. The longer you ask for more evidence, the more likely a small problem becomes a complaint.

If you accept exchanges, decide the rule in advance: exchange for a different size is free once the return is approved; exchange for a different product follows the normal return policy; refunds are processed only after inspection.

Send labels, inspect the item, and decide restock or write-off

Shipping labels

If you use a carrier portal or returns app, create a prepaid label and email it to the customer or make it downloadable from the return page. The label should include the return address, RMA number or return ID, and any carrier instructions.

If you do not send prepaid labels, give customers a clear format:

Write this return code on the outside of the package: RMA-1023
Send it to:
123 Fashion Street, Ward X, District Y, City
Keep your shipping receipt until the refund is confirmed.

For international returns, ask the customer to mark the package as “returned goods” or use the wording required by the courier. Check with your courier or tax advisor about commercial invoice wording so you do not pay unexpected import duties.

Inspection

Inspect before approving the refund or exchange. Use a short checklist:

• Does the order number and RMA match?
• Are tags still attached?
• Is there any wear, odor, deodorant mark, perfume smell, pet hair or stain?
• Is the returned item the correct product, size and color?
• Does the reason match the condition?
• If damaged or wrong item, compare with the customer’s photo.

One person should be responsible for inspection, or use a shared spreadsheet status column. Without this step, damaged items get restocked and sold again.

Restocking or write-off

After inspection, choose one of three actions:

• Restock as new if the item is clean, unworn and still has tags.
• Steam, fold or repackage if the item is sellable but packaging was opened.
• Write off if the item is damaged, stained, heavily worn, missing tags or cannot be sold as new.

For wrong items sent by your team, restock under the correct SKU. For damaged items, document photos and keep them for carrier claims or supplier returns where applicable. Items that fail hygiene checks should usually be written off, donated or destroyed depending on local rules.

Photo: Thirdman / Pexels

Process refunds or exchanges with clear customer messages

Refund and exchange processing should be fast and consistent. Once inspection is complete, update the request status and notify the customer.

Good and bad wording examples:

Bad:
“We got your return. It will be processed.”

Good:
“We received your return for order #1023. The item passed inspection, and the refund of $39.00 has been issued to your original payment method. Depending on your bank or payment provider, it may take a few business days to appear.”

Exchange template:
“Your return for order #1023 was approved. The size M you requested is available. We will ship it within 24 hours after our system confirms the return. You will receive a tracking number by email when it leaves our warehouse.”

If you deny a return, explain the reason briefly and reference the policy. For example:

“We received your request for order #1023. Unfortunately, this item is marked as final sale and is not eligible for return. If the item arrived damaged, please reply with a photo and we will review it immediately.”

Keep all messages simple, polite and factual. Avoid emotional words like “you should have,” “obviously” or “we’re sorry you feel that way.” State what happened, what you will do, and when the customer will hear from you again.

Log return data and review it to fix products and size charts

The returns process should generate data, not just refunds. For every return or exchange, record a row in a spreadsheet or system with these fields:

• Return date
• Order ID
• SKU or product name
• Size, color and variant
• Reason code and sub-reason
• Inspection result
• Restocked, written off or exchanged
• Refund amount or exchange order
• Photos or notes

Review the data monthly, not once a year. Look for patterns:

• A dress or blouse with many “Size too small” returns may need a size chart update, a note like “runs small,” or a pattern adjustment.
• A product with “Looks different from the photo” returns may need new product photography or more accurate color descriptions.
• A size chart with too few body measurements may cause repeated fit returns. We covered this in How to Help Customers Choose the Right Size Online for Boutiques.
• If returns say the color or fabric does not match the listing, review the photography and editing process before changing the product. See AI Product Photography for Clothing: Keep Product Shots Accurate.

For example, if a shop has 80 returns for a particular linen shirt and 34 of them are “too small,” the problem is probably the size chart or the cut, not the customer. That is a signal to update the size chart or adjust the product page copy.

Common mistakes that make returns work worse

Avoid these patterns:

• Refunding before inspection. A customer may return a worn or damaged item. Inspect first, then refund.
• Using vague reasons. “Didn’t like it” is much less useful than “color differed from photo” or “too long.”
• Restocking items that should be written off. This creates repeat returns and bad reviews.
• Arguing over small damage claims. If the photo shows a clear defect, approve fast and deal with the cause later.
• Inconsistent customer messages. Create templates so every staff member gives the same policy answers.
• Ignoring return data. A returns log only helps if someone reviews it and changes the size chart, product copy, photos or supplier.
• Hiding the return policy. Customers who cannot find the rules may contact support, open disputes or assume the worst.

A short soft recommendation: if fit or look is one of your top return reasons, a virtual try-on button on product pages can help shoppers judge the garment before buying. Macgi makes a lightweight AI virtual try-on widget that uses your existing product photos, sits next to Add to cart, and works by uploading one full-body photo. You can try Macgi’s virtual try-on widget in the free beta.

FAQ

How many days should a clothing store allow for returns?

It depends on your market and fulfillment time. Many fashion stores use 14–30 days, but you should check current consumer-protection rules in the countries where you sell. The return window should be long enough to allow delivery and trying on, but short enough to avoid increasing restocking risk.

Should customers pay for return shipping?

There is no single rule. Some stores cover return shipping for damaged or wrong items and let the customer pay for fit or changed-mind returns. Others offer free returns to reduce hesitation. The important part is that your policy states who pays before the customer buys.

Can I automate returns on Shopify or WooCommerce?

Yes. Shopify has return and exchange apps that let customers look up orders, choose items and receive labels. WooCommerce has return request plugins and form builders. Haravan and Sapo stores can usually embed a form or link to a returns page. Even without a full app, a structured email form is better than unstructured support emails.

What should I do with an item that was tried on but looks new?

If the tags are intact, there is no odor, makeup, pet hair or visible wear, you can usually restock it after light steaming or repackaging. Use a written condition checklist so the inspection team decides consistently.

How do I track returns if I do not have a dedicated system?

Start with a shared spreadsheet. Create one row per returned item with order ID, SKU, size, reason code, inspection result and final action. Review it monthly. For many small stores, this gives more usable information than upgrading to a complex system too early.