Refund Request Form Template

A refund request handled well is a strange kind of marketing: the customer whose problem was fixed quickly often ends up more loyal than one who never had a problem. Handled by email, though, refunds sprawl — missing order numbers, photos requested in the third message, decisions delayed by facts that should have arrived in the first. This form collects the complete case up front, so the person deciding can decide.

Why these fields. Order number, purchase email, and purchase date are the lookup triangle — any two usually locate the order, all three make it certain, and certainty is what lets you skip the "can you confirm…" round-trip. The reason selector does double duty: it routes the case (a damaged item is a shipping conversation, a never-arrived order is a carrier investigation, a changed mind is pure policy) and it accumulates into product intelligence — a spike in "not as described" is a listing problem wearing a refunds costume. The evidence upload appears only when the reason is damage or a wrong item, through a logic rule: those are the cases photos genuinely settle, and asking a changed-my-mind customer to photograph anything is friction with a hint of accusation. Photos are capped at three images, 10MB each, verified as real image files. The refund-route question sets expectations on the last step — original payment method or store credit — which is precisely where refund conversations otherwise stall.

What we left out. The money movement itself. The refund is issued in your payment or shop system, where it belongs — this form is the intake, the evidence file, and the audit trail that makes the decision fast and defensible. Also interrogation fields like "did you read the sizing chart": tone leaks, and refunds are trust moments.

Who uses this. E-commerce shops on any platform, digital-product and course sellers, subscription boxes, event organizers handling cancellations, and local businesses that take deposits.

Make it yours. Rewrite the reason list to your catalog's reality — sellers of fragile goods split "damaged" into transit and manufacturing, digital sellers replace shipping lanes with access problems. Turn on email notifications so cases reach whoever decides, and add a webhook if approvals happen in a channel or ops tool. The responses view is the case history: search a customer's email to see their pattern before deciding a borderline case, and export the CSV monthly to read refund reasons as the product feedback they secretly are.

Decide once, fast. The form's promise — a decision within two business days — is only keepable because everything needed for the decision arrives together. That speed is the loyalty play.