Returns and exchange form
A returns and exchange form that turns a frustrated shopper into a sortable RMA request, order number and reason attached, backend already wired in and spam filtered, so you review and reply instead of digging through email threads.
How to use this form
- Create a form in your Formpaste dashboard and copy its access key.
- Paste the template below into your project and swap YOUR_ACCESS_KEY_HERE for your key.
- Set your destination email and allowed domains in the dashboard.
- Deploy - submissions land in your inbox, spam filtered, no CAPTCHA.
Framework guides for this form
Prefer a guide for your exact stack? Open the per-framework walkthrough.
What is a returns and exchange form?
A returns and exchange form is the front door to your RMA process. When a customer wants to send something back or swap it, they tell you who they are, which order it was, and what went wrong, and you get a structured request you can review and act on. It replaces the messy “I want to return this” email with a tidy record that has everything you need to decide the next step.
Set the boundary clearly. This is intake, not a self service returns portal. The form does not print a shipping label or issue a refund on its own; it collects the request so a human can check it against your policy and reply with instructions. For most shops that human review is a feature, because returns are exactly where you catch abuse, offer an exchange instead, or save a sale with a quick fix.
When to use it
Use a returns form whenever customers may need to send goods back and you want those requests to arrive organized rather than scattered. An apparel shop handling sizing swaps, a maker dealing with the occasional damaged item, or any store without a heavyweight returns platform will get more done from a single reason coded inbox than from freeform email.
It is the right fit when returns need judgment: confirming the order, checking the return window, deciding refund versus exchange, or asking for a photo of damage. If you would rather review each case and reply than automate refunds blindly, this form gives you clean cases to work through.
What to include
This template captures precisely what you need to open and triage a return. Name and email are required, so you know who is asking and where your reply goes. The order number is required too, because without it you cannot verify the purchase or find the item in your records.
The reason is a required select, and it is what makes this form pull its weight. It offers Wrong size, Damaged, Not as described, Changed my mind, and Other, so you can sort and route returns at a glance instead of reading every message to figure out what happened. The details textarea is optional and pairs with that Other option, giving customers room to explain the specifics, add a photo note, or say which size they would prefer in an exchange.
Tips for smoother returns
Publish the policy next to the form. Your returns window, condition rules, and who pays return shipping belong right beside the fields, so a request arrives already matching what you can actually approve.
Lean on the reason codes. Sort your inbox by reason and you can batch the easy cases, flag Damaged for a photo, and spot patterns, like one product that keeps coming back as Wrong size and needs a better size guide.
Reply like a person. Reply-to is set to the customer, so a return is a single reply from your inbox. A prompt, human response at the return stage is often what decides whether they buy from you again.
Also works on
No dedicated guide yet, but this form drops into any of these too. Open the platform overview to get started.
Frequently asked questions
Paste a form. Get submissions.
Instantly without setting up any backend, servers or databases. 250 submissions/mo free - no credit card.