A return begins with a parcel on the doorstep and an email that says "this is wrong". Your warehouse needs to know what comes back, in what state and why, before it arrives. I would rather have those answers in a list.
Use this when
Customers return goods you must inspect first: clothing, electronics, gifts and anything with a condition rule. You want to approve before they ship.
Skip it when
You accept every return with no questions. A contact form is enough for that.
What it asks and why
- Order number and arrival date: to check the return window yourself.
- Items and reason: a pick-list you can count to see why things come back.
- Condition and packaging: what your warehouse will meet at the door.
- Refund, exchange or credit: decides which team handles it.
- How it will be sent back: post, pickup or drop-off, so you plan the label.
The form makes no authorization number. You reply with your own.
What a customer's AI would ask
"What is your order number?" Then "Why are you returning it?" Then "What condition is it in?" It shows all answers and sends only after a yes. See agent-fillable forms.
Faulty goods under warranty belong in a warranty claim form. Exchanges for sold-out sizes can go on a waitlist. More ideas are in forms for Ecommerce and Shopify stores.
Questions
Does the form create an RMA number?
No. It gathers the request. You review it, then reply with your own authorization number and return address.
How do I handle exchanges?
The form asks what the customer wants instead. Filter the CSV by that answer, send exchanges to your stock list and send refunds to your payment tool.
Can I require the original packaging?
Say so in the form description. The form has a packaging tick, but it cannot block a return, so check each row yourself.