Sell · free template

Refund Request Form

Order lookup and reason-driven refund intake with a choice of refund, replacement or store credit.

A ready-to-use e-commerce & payments form for online shops, makers and subscription brands: 12 questions, 3 pages, 4 conditional rules.

Questions
12
Pages
3
Layouts
classic · card
Conditional rules
4
Typical time
3 min
Preview it in the gallery

Searches this template answers

Also filed under

Live preview and test console

This is the real form. Answer it to test the 4 conditional rules — nothing is sent or stored.

Page 1 of 3Your order

Refund request

Every question on this page is currently visible.

What happens after submit: nothing is stored in this preview. On your own copy, every response triggers an instant email notification and lands in your response dashboard, ready to export or forward.

Happy with it? Take a copy into your workspace — every question, rule and setting comes with it.

Who this template is for

Refund Request Form is built for online shops, makers and subscription brands who need to take an order, a deposit or a recurring payment without a checkout build.

  • Online shops, makers and subscription brands working in e-commerce & payments.
  • Teams who need to take an order, a deposit or a recurring payment without a checkout build without writing code or paying for a custom build.
  • Anyone replacing orders arriving as half-finished emails with no payment attached with one structured record per enquiry.
  • Respondents are shoppers and repeat customers — the form asks them 12 questions across 3 screens.
  • Mobile-heavy audiences, thanks to the one-question-per-screen card layout.

Why this form is useful

It removes the cost of orders arriving as half-finished emails with no payment attached and turns each submission into a record your team can act on immediately.

  • 7 questions are required, so submissions arrive complete instead of needing a follow-up email.
  • It collects a verified email address so replies and confirmations land.
  • It accepts a document or photo upload as evidence.
  • It pins the request to a specific date.
  • Conditional logic hides 4 questions until they are relevant — shorter forms convert better than long ones.
  • Splitting the form across 3 pages keeps each screen short and shows respondents how much is left.
  • Every response is stored, searchable and exportable, so nothing depends on one person's inbox.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

  1. 1Press “Use this template” — a fresh copy of Refund Request Form lands in your workspace, ready to edit.
  2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
  3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
  4. 4Check the upload limits on the file question so respondents can attach what you actually need.
  5. 5Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
  6. 6Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 4 conditional rules ship with it.

  • Features advanced show logic: if “Reason for the request” is Damaged or defective item, the form dynamically exposes “Upload photos of the issue”. Otherwise that question never appears.
  • Features advanced show logic: if “Reason for the request” is Damaged or defective item, the form dynamically exposes “Which item was affected?”. Otherwise that question never appears.
  • Features advanced show logic: if “Reason for the request” is Item arrived late, the form dynamically exposes “What delivery date were you originally given?”. Otherwise that question never appears.
  • Features advanced show logic: if “Reason for the request” is Wrong item received, the form dynamically exposes “What did you receive instead?”. Otherwise that question never appears.
  • All 4 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.

About this template

A refund request is easiest to process when the order is identified before anything else is asked, so this form opens with the order number and purchase date rather than a general complaint box. The reason for the request then branches the questions that follow: a damaged or defective item asks for photos and which item was affected, an item that arrived late asks for the delivery date versus the estimate given, a wrong-item request asks what was received instead, and a simple change-of-mind request skips the evidence fields entirely since none are needed. Every path leads to the same resolution question — a refund to the original payment method, a replacement item, or store credit — because customers rarely want to negotiate that separately after already explaining the problem. A photo upload appears only for damage or defect claims, keeping the form quick for the requests that don't need it. The closing section confirms contact details and gives the customer a place to add anything else relevant, so the team processing the request isn't chasing basic information over email before they can act.

What this form asks

Every question is editable — rename it, make it optional, or delete it entirely.

Page 1 — Your order

  • Order numberrequired
  • Date of purchaserequired
  • Your namerequired
  • Email address used for the orderrequired

Page 2 — What happened

  • Reason for the requestrequired
  • Which item was affected?
  • Upload photos of the issue
  • What delivery date were you originally given?
  • What did you receive instead?
  • Tell us more about what happenedrequired

Page 3 — How you'd like this resolved

  • Preferred resolutionrequired
  • Anything else we should know?

12 questions in total.

How the form changes as it's filled in

This template ships with 4 conditional rules, grouped into 3 behaviours driven by 1 question. Everything below is already set up — edit or delete any rule once the template is in your workspace.

Driven by “Reason for the request

  • Reveals questions

    If “Reason for the request” is Damaged or defective item, the form reveals “Upload photos of the issue” and “Which item was affected?”.

  • Reveals questions

    If “Reason for the request” is Item arrived late, the form reveals “What delivery date were you originally given?”.

  • Reveals questions

    If “Reason for the request” is Wrong item received, the form reveals “What did you receive instead?”.

Set it up step by step

  1. 1

    Ask for the order number first

    Nothing else on this form matters until support can pull up the actual order, so it sits above every other field.

  2. 2

    Only request photos when they're needed

    The upload field only appears for damage or defect claims, keeping change-of-mind requests quick to submit and quick to process.

  3. 3

    Offer the resolution choice up front

    Asking refund-vs-replacement-vs-credit at submission avoids a second round-trip once the reason has already been explained.

  4. 4

    Set an internal response-time expectation

    Pair this form with an auto-reply stating your typical turnaround so customers aren't left guessing after they submit.

Mistakes to avoid

  • Asking for photos on every request, which slows down simple change-of-mind refunds.
  • Not capturing the order number, which forces support to search by name or email first.
  • Leaving the resolution preference for a follow-up email instead of asking it in the original form.

What it pairs with

Most teams don't run this form on its own. These are the forms and systems it sits next to.

What to do with the responses

Match the order number against your order system, review any uploaded photos for damage claims, and action the customer's preferred resolution or reply if it isn't available for that order.

Works in both layouts

These pages cover the same subject ground as the refund request form, matched on the words people actually search for.

Frequently asked questions

Should this replace our formal returns policy?

No — this form is the intake step; your returns and refund policy should still govern what's eligible, and it's worth linking to that policy from the form's opening text.

What if the customer doesn't have their order number?

Consider adding a lookup by email and purchase date as a fallback, or route those submissions to a manual search queue rather than blocking submission entirely.

Can we use this for both refunds and exchanges?

Yes — the resolution question already covers replacement as an option, so you don't need a separate exchange form for most cases.

How do we handle high-value refund requests differently?

Add an internal notification rule that flags requests above a certain order value for manager review before the resolution is actioned.

Is the Refund Request Form template free to use?

Yes. You can preview and test Refund Request Form on this page without an account, and take a copy into your own HelloForms workspace on the free plan. There is nothing to install and no card required to publish it.

What does the Refund Request Form template ask for?

It asks 12 questions across 3 pages, 7 of which are required. Every question is listed in full further down this page, and each one can be renamed, reordered, made optional or deleted after you copy the template.

Can I edit the Refund Request Form form after copying it?

Yes — the copy is entirely yours. Change wording, add or remove questions, switch between the classic and card layouts, restyle it to match your brand, and set who gets notified on each submission.

How does the conditional logic in this e-commerce & payments form work?

4 conditional rules ship with the template: Features advanced show logic: if “Reason for the request” is Damaged or defective item, the form dynamically exposes “Upload photos of the issue”. Otherwise that question never appears. Features advanced show logic: if “Reason for the request” is Damaged or defective item, the form dynamically exposes “Which item was affected?”. Otherwise that question never appears. Features advanced show logic: if “Reason for the request” is Item arrived late, the form dynamically exposes “What delivery date were you originally given?”. Otherwise that question never appears. All rules are editable in the Logic tab.

Where do responses to the Refund Request Form form go?

Submissions land in your workspace under Submissions, where you can search, filter, label and export them to CSV or PDF. You can also email a notification to your team on every submission and send the respondent an auto-reply.

Can I embed the Refund Request Form form on my own website?

Yes. Publish the form and paste the embed snippet into any page or share the direct link. The embedded form resizes to fit its container and loads no advertising or marketing trackers inside the iframe.

Can respondents upload files?

Yes. This template includes a file upload question, so respondents can attach documents or photos with their answers. You can adjust the accepted file types and size limits on that question.

More forms teams pair with the refund request form.

Related categories