Process first, tone second — but both matter
A slow or inconsistent return process damages both customer sentiment and account health metrics (return-related disputes feed into order defect rate on most platforms). A fast, clear process with an empathetic tone tends to actually reduce negative reviews even when the underlying issue (a damaged item, a wrong size) wasn't the seller's fault.
The process framework
Acknowledge the request quickly (even an automated first response is better than silence for 24+ hours), follow the specific marketplace's return workflow (each platform has its own required steps and timelines — don't assume email-based store logic transfers to a marketplace's system), and resolve at the fastest point you're comfortable with rather than dragging out an inevitable refund through back-and-forth.
A step-by-step handling sequence
- Acknowledge within your SLA window — a quick, specific reply ("Sorry to hear the size didn't work out — let's get this sorted") does more for sentiment than a longer delay followed by a more thorough one.
- Identify which bucket the request falls into: buyer's remorse / wrong choice, a genuine product issue (damaged, defective, not as described), or a seller-side error (wrong item shipped, listing error). Each deserves a different tone and sometimes a different resolution path.
- Follow the marketplace's required return workflow for that request type — most platforms require the return to be initiated and tracked through their own system even if you'd resolve it faster informally, since the platform's own metrics and buyer protections are tied to that workflow.
- Resolve at the fastest point that's reasonable — don't require a full return-and-inspect cycle for a case where a no-return refund is clearly the more sensible resolution (see below).
- Follow up briefly after resolution for a higher-value or higher-friction case, confirming the refund or replacement landed correctly — this small step meaningfully reduces the odds of a residual negative review from a buyer who resolved the issue but never got confirmation it was truly finished.
When to just refund without requiring a return
For inexpensive items, the cost of return shipping and processing often exceeds the item's value — many sellers instruct customer service to issue a no-return-required refund below a set dollar threshold, which resolves the situation faster for the customer and is frequently cheaper overall than processing a physical return. Setting this threshold explicitly (rather than deciding case by case) also speeds up handling time, since a customer service rep or contractor doesn't need to escalate every low-value refund decision individually.
Handling a return that looks like abuse
Occasional return-policy abuse (a buyer claiming "damaged" repeatedly, or returning a clearly-used item as new) is a real pattern, but treat each case on its own evidence rather than assuming bad faith by default — a wrongly-accusatory response to a legitimate customer does far more damage to sentiment (and can trigger a dispute that counts against you) than the cost of one occasional bad-faith return. See Fraud Prevention for Sellers for patterns worth tracking systematically rather than reacting to individually.
Tone: templates help, but avoid sounding robotic
A good response template (see Writing Customer Communication Templates) should still read as though a person wrote it — acknowledging the specific issue rather than a generic "we're sorry for any inconvenience" that reads as canned regardless of what actually happened. Reference the specific product, the specific issue described, and (where relevant) what you're doing about it — three details that take seconds to add and substantially change how genuine the reply reads.
Cancellations need the same care, in the other direction
A cancellation initiated by the seller (due to a stockout, pricing error, etc.) should be communicated proactively and apologetically rather than left for the customer to notice — silence around a cancellation is one of the more common preventable sources of a negative review. Where possible, offer something concrete alongside the apology: an accurate restock timeline, a comparable alternative product, or a small gesture (a discount on a future order) proportionate to the inconvenience — a bare "your order has been cancelled" notification with no context or acknowledgment reads as dismissive even when the cause was a genuine, unavoidable stockout (see How to Prevent and Recover From Stockouts for the inventory side of preventing these in the first place).
Refund timing and how it interacts with metrics
Process refunds as soon as the decision is made rather than batching them — on most platforms, refund timeliness itself is tracked as part of order defect rate or a similar composite metric, meaning a correct-but-delayed refund can still cost you standing even though the customer ultimately got the right outcome.
Documenting the pattern, not just handling the instance
Track return/refund/cancellation reasons over time by category (wrong size, damaged in transit, listing inaccuracy, stockout) — a recurring reason pointing to a fixable root cause (a sizing chart that's consistently misleading, a packaging issue causing transit damage) is far more valuable to catch and fix upstream than to keep resolving one instance at a time indefinitely.