How to write a returns policy that cuts support tickets

In this order, each with its own heading, because customers scan for the one that applies to them rather than reading from the top.

Most returns policies read as though a lawyer wrote them to protect the store from its own customers. That tone does not actually protect you — it just means nobody reads to the end, and the parts they skipped turn up as questions.

So: short sentences. Second person. “You have 30 days”, not “Customers shall be entitled to a period of thirty (30) days”. Real numbers rather than “a reasonable period”. And no word in the policy that you would not say out loud to the customer on the phone.

Wording that works

Fill in your own numbers — these are shapes, not terms:

• You have [30] days from the day your order is delivered to start a return.
• Items need to be unworn, with tags attached, in their original packaging.
• Sale items and personalised orders can’t be returned.
• Return shipping is [paid by you / covered by us]. If the item arrived damaged or faulty, we cover it.
• To start a return, [use this form / email us at this address] with your order number.
• Refunds go back to your original payment method within [5–10] business days of us receiving the item.

Read them back. Every one answers a question completely, with no follow-up available. That is the test for the whole page: could somebody reply to this sentence asking for a clarification? If so, the clarification belongs in the sentence.

Who pays to send it back is the question behind most returns tickets, and it is the one most policies bury in the fifth paragraph or leave out entirely.

Put it in the first screen. Whichever way you have decided, say it outright, and state the exception for faulty or damaged goods in the same breath. A customer who knows the answer either proceeds or does not. A customer who does not know asks you — and then waits, which is worse for both of you than an answer they did not love.

The same goes for the cost. If return shipping comes out of the refund rather than being charged separately, say so here rather than letting somebody discover it when the money lands. Surprises at refund time are how a resolved return becomes a complaint.

A perfect policy nobody can find does nothing. Four places:

The footer. Table stakes, and where people look first.

The FAQ page. As its own question, not a buried link.

The product page. Near anything about fit or sizing, where the doubt actually occurs.

The order confirmation email. The one most stores miss. It is the email customers keep and search for weeks later, which makes it the highest-value link on this list — the same logic as putting the tracking link at the top of the shipping email.

A clear policy page is not only for customers. It is the thing anybody — a new hire, a VA, an AI assistant — reads in order to answer on your behalf. A vague policy cannot be delegated, because whoever you delegate to has to come back and ask you what it means.

That is why AI handles return-policy questions well when the policy is specific and badly when it is not: it can read your terms back accurately, but it cannot invent the rule you never wrote down. Tighten the page and the same work covers your customers, your inbox and anything answering for you.

If you are the only person answering right now, the one-person support setup shows where the policy page sits in a stack you can actually maintain.

Open your returns page. Find the three questions you get asked most about returns. Check whether the page answers all three in the first screen, in words you would use out loud.

Usually it answers one. Fixing the other two is an afternoon, and it is the lowest-effort support improvement available to you.