A return-request email should make the item, order, reason, and requested return process easy to identify. It is distinct from a refund request because a return focuses first on sending the item back; any refund can be handled as a separate outcome.
ReviewedEvidence2 sourcesSectionWriting & Style
Quick answer
A clear version is: “I’d like to return order 48219 because the item does not fit. Could you send the return instructions and let me know whether I need a return authorization number?”
Key details
Core Issuea return request should identify the order/item, state that a return is requested, give the relevant reason or policy context, and ask for the required return instructions or authorization
Phrase Roleasking a seller or provider for permission/instructions to send an item back
Registerprofessional
Important caveats
Scope Boundary
Use Request a Refund — Email Wording when the main request is the return of money rather than instructions to send an item back.
Further guidance
Reason
Give a concise reason when relevant to the policy or process.
Request
State directly that you want to return the item and ask for the required instructions or authorization.
Transaction
Identify the order, item, purchase date, or other reference needed to find the transaction.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
A return-confirmation email should confirm acceptance and give practical shipping, authorization, deadline, or next-step details without promising a refund before the stated process has been completed.
A refund-request email should make the transaction, requested amount or scope, reason, and processing details easy to verify. It differs from a payment request because the money has already been paid and is now being requested back.
A replacement-request email should identify the item and transaction, explain why replacement is needed, and state the substitute requested. It can accompany a complaint, but the desired outcome is specifically replacement rather than a general remedy.
An approval-response email should make the yes decision unmistakable and state any conditions, limits, or next steps. It is the response counterpart to a request-for-approval email.
A professional decline should be clear enough that the requester knows the decision, while avoiding unnecessary blame or vague language. Alternatives should be offered only when they are genuinely available.
A demo-request email should give enough context for the presenter to tailor the session and should make the scheduling request easy to answer. It is more specific than a general meeting request because the purpose is to demonstrate defined capabilities.
A meeting request is clearest when it says why a meeting is needed, what decision or topic it will cover, and what scheduling action the recipient should take. Specific context reduces unnecessary back-and-forth.
A quote-request email should give enough scope for the recipient to price the same requirement you actually intend to buy. Include quantities, specifications, timing, delivery or location details, and any terms that materially affect the quotation.
