How to write a return policy that prevents disputes

A customer wants to send back a worn pair of boots eleven weeks after buying them. Your policy page mentions neither worn goods nor eleven weeks. So you are about to make the rule up, under pressure, in writing, with a chargeback sitting in the other person's back pocket.

That is what a return policy is for. Not to limit returns — to remove the ambiguity that turns a routine refund into an argument. Nearly every dispute a small store has starts with a question the policy did not answer, and the person who has to improvise is always you.

Below is the order to write one in. The order matters: four decisions come before any sentence gets written, and people who start with the wording end up with a page that reads well and settles nothing.

Decide these four things before you write anything

1. The window

Pick a number of days and pick it for a reason. Thirty days from delivery is the common default because it is long enough to feel safe and short enough to bound your exposure.

The mistake is choosing a window and not saying what it is measured from. "30 days" is ambiguous; "30 days from the delivery date shown by the carrier" is not, and the carrier's date is a fact neither of you can argue with.

2. The condition the goods must be in

Write the physical test, not an adjective. "Unused" starts fights because trying on a shirt is use. "Unworn, unwashed, with tags attached, in the original box" can be checked by the person opening the parcel.

If your product cannot be inspected and resold — food, cosmetics, anything sealed for hygiene — say that here rather than hiding it in exclusions later.

3. Who pays the return shipping

This is where most arguments actually start, and most policies say nothing about it.

Three honest options: you pay (strongest for conversion, most expensive), the customer pays (cheapest, suppresses some first purchases), or you pay when the item is faulty or wrong and the customer pays when they changed their mind. The third is the one most small stores can defend, and it is the one to write down.

Whichever you pick, state it in the same sentence as the window. A policy that grants a return and goes quiet about the freight has not avoided the cost, only the conversation.

4. The exclusions — and only the real ones

List the categories you genuinely will not take back: custom or personalized items, perishables, opened hygiene products, digital downloads, gift cards, final-sale items.

Two rules: every exclusion needs a reason you would say out loud, and it has to appear on the excluded item's own product page, not only in the policy. Otherwise it will not hold when someone says they never saw it.

Then write these six clauses

5. Separate "I changed my mind" from "it arrived broken"

These are different events and merging them causes most of the remaining trouble. A change of mind is a courtesy, bounded by your window and condition rules. A faulty, damaged or wrong item is your error, so the window, the condition and the freight should all be treated differently — and faulty goods usually fall under consumer protection rules your window cannot shorten.

6. How the refund is issued, and when

Say the method: back to the original payment method, always. Say the clock: how many business days after you receive and inspect the item. Say whether original shipping is refunded — most stores refund the goods but not the outbound freight, which is fine, provided it is written down.

"We will refund you promptly" is the single most dispute-generating sentence in this genre. Replace it with a number of days.

7. One route to start a return

One email address or one form, not "contact us", which invites three channels and loses one of them. Ask for exactly what you need to act: order number, item, faulty or unwanted, and a photo if damaged. Asking the reason is useful; demanding a justification before you reply is how a refund becomes a complaint.

8. Say whether you accept exchanges

Exchanges are harder to run than refunds, because the replacement has to be in stock on the day. Either say what happens when the size they want is gone, or say "we refund rather than exchange, so reorder whenever you like".

9. Restocking fees and partial refunds, if any

If you deduct anything — a restocking fee, a missing accessory, a reduction for an item that is no longer sellable — name it as a specific amount or percentage before anyone buys. A deduction invented at refund time is the classic trigger for a card dispute, and the dispute will not go your way. Most small stores are better off with no restocking fee: it collects very little and costs the goodwill of the people who would have bought again.

10. Where the policy lives

Writing it is half the job; it has to be present at the moment the decision is made.

• A footer link on every page, labeled "Returns", not buried under "Information".
• One line on the product page near the price: "30-day returns. We pay return shipping on faulty items."
• The same line at checkout, before the payment step.
• A link in the order confirmation email, which is the message people actually keep.

The clauses that prevent disputes

Why a harsh policy costs more than it saves

A restrictive policy looks like it protects margin. Run the numbers and it mostly protects your feelings.

Illustrative figures, so substitute your own: average order $38, contribution per order $18.75, return rate 5%. On 100 orders that is five returns — say four come back resellable at about $7.50 of freight each, and one is a write-off costing the full $18.75 plus freight. Total: roughly $56 across 100 orders, about 56 cents an order.

Now the other side. One buyer deterred by a restrictive policy costs $18.75 of contribution, so three deterred buyers per hundred would cost more than the entire return program. Three in a hundred is exactly the kind of effect a policy page produces without ever appearing in your reports.

Then the part that hurts. A refused return becomes a card dispute: you lose the revenue anyway, you lose the goods, you pay a dispute fee, and it counts against your account's dispute ratio. One escalation can cost more than the handful of returns you declined.

Write a clear policy, not a tight one. Clarity reduces disputes; tightness relocates the cost somewhere you cannot see it.

What a policy cannot do

It will not stop return fraud. Wardrobing — buy, wear once, send back — is defeated by your condition test and by watching individual customers, not by wording.

It will not answer the genuine edge case. Someone always has a reason you did not anticipate, and the policy's job then is to give you a defensible default to depart from.

It will not fix a misleading product page. Much of what comes back is a sizing or expectation problem, so the repair lives in the photographs, measurements and description. A product that returns far more than the others is a listing problem wearing a returns costume.

And it will not maintain itself. Record every exception you grant — one line: date, order, what you allowed, why. A dozen entries show you which clause is actually ambiguous, and that is how version two gets written.

Where mAutomate fits

mAutomate's AI customer support answers shopper questions on your website, so "can I return this" gets a consistent answer from your actual policy rather than whatever you remembered at 11pm. The AI drafts and recommends, and nothing goes live until you approve it — which is the right arrangement for a refund decision.

Knowing how to write a return policy is mostly knowing which four decisions come first; after that the page takes twenty minutes. The freight side is worked through in the free shipping math, and the plans page lists what each tier includes.