Skip to content
Order Genie is live on the Shopify App Store — 50 free chats, forever →
Order Genie 11 min read

How to Write a Shopify Return Policy Customers Follow

Most return policies list the rules and stop there. What to write, in the order a buyer needs it, and the emails no page can stop.

ShopAppsLab The team building Order Genie
A card whose top three rows are filled in and checked, and whose bottom three are empty dashed outlines

You can have a returns page and still get this email:

Hi — I’d like to send the blue one back. What do I need to do?

The page answered whether they can return it. It did not tell them how, so they asked. That gap is where most returns support volume lives, and it is not a policy problem — it is an instructions problem.

A returns page has an unusual double life. Before the sale it is a confidence document: someone hovering over the buy button reads it to find out what happens if the size is wrong. After the sale it is a set of instructions: someone with a parcel in their hallway reads it to find out what to do next. Most pages are written entirely for the first reader, in the voice of a contract, and then handed to the second one.

Here is how to write one that serves both — and an honest account of the messages it will never stop.

Rules answer “can I?” — the email asks “how?”

Almost every returns page on the internet is a list of rules. How many days, what condition, which items are excluded. Those rules are necessary and they belong at the top.

But a buyer who has decided to return something has already moved past “can I”. Their questions are now entirely practical: do I need to tell you first, where does it go, do I print something, who pays for the postage, and when do I get my money. If the page stops at rules, every single one of those becomes a message.

So think of the page as two halves that both have to be written:

  • The rules — what qualifies, and on what terms. Read before the sale
  • The process — the numbered steps a person follows, alone, at 10 PM. Read after delivery

The second half is the one that removes work from your week, and it is the half that is usually missing.

The four rules, written so nobody has to check

Four facts decide whether a buyer needs to contact you before they can act. Say all four plainly and near the top.

1. How long they have, and from when.

The start date matters as much as the number. “30 days” from the order date is a different offer from 30 days from delivery, and a customer who is guessing will write to ask.

You have 30 days from the day your order is delivered to start a return.
We use the delivery date on the carrier’s tracking, so a slow delivery never eats into your window.

2. What condition the item has to be in.

Be concrete about the thing you will actually reject something for, because vagueness here is what makes people ask for permission first. “Unused” means nothing to someone who tried a jacket on in front of a mirror.

Items should be unworn, unwashed, and back in their original packaging with the tags still attached. Trying something on is completely fine.

3. Who pays the return postage.

The single most re-read line on the page, and the one we come back to below.

4. How the refund comes back, and when.

Refund to the original payment method is the expectation; anything else — store credit, an exchange only — has to be stated in the rules, not discovered at the end.

One caution rather than legal advice: consumer law where your buyers live may set a minimum return window and decide who pays postage for a change of mind, and it does not care what your page says. If you sell into the EU or the UK, check the rules that apply to distance selling before you copy a policy template written for a US store.

Who pays return postage is the line people re-read

This is a business decision disguised as a policy sentence, and it is worth deciding deliberately, because all three answers are defensible and each one costs you something different.

  • You pay — the fewest emails and the highest return rate. People do not ask permission before returning something that is free to return. It is the strongest conversion argument you can put on a product page, and it shows up as a direct line on your margin
  • The customer pays — fewer returns, more hesitation before the sale, and more messages, because people negotiate. Expect “would you cover it this time?” and decide in advance what your answer is
  • You pay when it is your fault — the common middle. Wrong item, faulty, damaged in transit: on you. Changed their mind or ordered the wrong size: on them

Whichever you choose, write it as one unambiguous sentence and put the cost next to it if the customer is paying:

Return postage is paid by you unless the item arrived faulty or we sent the wrong thing, in which case we cover it and send you a prepaid label.

The version that generates work is the one that leaves it open — “return shipping may be the responsibility of the customer” tells a person nothing except that they should ask you.

Then write the part most pages skip: the steps

This is the half that converts a returns page from a document into a piece of support automation. Number the steps, keep them to one line each, and make sure a person can finish all of them without you.

How to return something

  1. Reply to your order confirmation email with your order number and which items you are sending back.
  2. We reply within one business day with the return address and, where it applies, a prepaid label.
  3. Pack the items with the packing slip inside and send them off.
  4. Tell us the tracking number so we can watch for it.
  5. We inspect and refund within 2 business days of the parcel arriving.

Even that — a plain five-line list with no returns portal behind it — removes most of the “what do I do now?” messages, because the buyer’s next action is never ambiguous.

Two details are worth getting right. Say where the request goes, in one specific place: replying to the order email, one address, or one form. Offer three routes and you will receive them on all three plus social. And name what you need in the first message — order number, which items, and why. Half of returns correspondence is a merchant asking for information the customer would happily have sent first time if the page had asked for it.

If you run a returns portal or an app, the steps get shorter, not unnecessary. “Go here, enter your order number and email, follow the prompts” is still the sentence that has to be on the page.

Refunds run on two clocks, and only one is yours

“I sent it back — where is my refund?” is one of the most common returns messages, and it is almost always caused by a page that quotes a single number.

There are two clocks. Yours: from the parcel arriving to the refund being issued. Theirs: from the refund being issued to the money appearing on the statement, which is the bank’s business and takes days longer than most people expect. Publish both, separately, and the message stops:

We refund within 2 business days of your return arriving with us. Your bank then takes a few more days to show it on your statement — that part is out of our hands, but you will have an email from us the moment we send it.

Then actually send that email. A refund notification is the cheapest support message a store can send, and it pre-empts a question that would otherwise arrive twice — once when the parcel is delivered to you, and again a few days later.

Decide about exchanges before someone asks

Exchanges are where a good returns page quietly falls apart, because the question “can I swap it for a medium?” has no answer on most sites.

You have two honest options and either is fine, but the page has to say which one:

  • Refund and re-order. Simpler for you, and the customer gets their size immediately instead of waiting for the return to land. Say so explicitly, and say it kindly — worded well, this is not a refusal
  • A real exchange. More work per order and it needs stock reserved, but it keeps the sale. If you offer it, say what happens if the replacement costs more or less

We do not process exchanges. For a different size or colour, place a new order so it ships straight away, and send the original back for a full refund using the steps above.

Three sentences, and an entire category of message disappears.

Where the page has to sit

A returns policy that only exists in the footer is found by people who already suspect the answer is bad. Put the substance at the two moments the question actually forms:

  • On the product page, near the buy button — the window and who pays postage, in a line, not a link. This is a conversion asset, especially for anything with a size
  • In the delivery confirmation email — the one message that reaches a customer at the exact moment they are opening the box
  • In your FAQ, in the customer’s own words — “Can I return this?” and “How do I send something back?” find people that a link titled Refund Policy does not

We went through the full list of placements, and why the footer link is the last line of defence rather than the strategy, in the shipping policy post — the same logic applies here, at different moments.

What a returns page can never answer

Be clear about the limit, because it is the same limit every policy page has. Your page answers generic questions. It cannot answer order-specific ones, and those keep arriving no matter how well you write:

  • “Did you receive my return? I sent it last week”
  • “Where is my refund for order #1234?”
  • “The label you sent me does not work”
  • “Can I still cancel? I ordered an hour ago”

Every one needs a lookup against a real order — the same wall the shipping page runs into with “where is my order?”, and the same split we described in the five emails you answer over and over — page work removes the general questions and leaves you a smaller, more specific inbox. That is the realistic win, and it is a good one.

Where we come in, briefly. Order Genie is the AI Order Agent we build at ShopAppsLab. It sits on your storefront, looks the order up in your store, and answers “where is my order?” — plus the shipping, returns and FAQ questions that tend to follow it — 24/7, without you in the loop. When a message is a decision rather than a lookup — a refund, an address change, a parcel that is actually lost — the conversation is handed to you with the full transcript. It starts free with 50 chats a month, and paid plans begin at $9. If you would rather keep answering by hand, everything above still works on its own — that is the honest version.

Worth repeating from the shipping post, because it matters more here: during setup it imports the refund and shipping policies you wrote on Shopify and shows you what it read. A page that never says who pays return postage does not become a clear answer because something automated is reading it out. The writing comes first either way.

The one paragraph to write first

If you do nothing else today, write the four rules as a single paragraph and put it on your product page, above the fold:

30 days from delivery. Unworn, tags on, original packaging. We pay return postage if the item is faulty or we picked the wrong one; otherwise it is on you. Refunds go back to your original payment method within 2 business days of the parcel reaching us.

Four sentences. It answers the pre-purchase question, it sets the terms before anyone has to ask, and it is the piece you will paste into every returns email you write from now on.

The steps can come next week. The rules are what is costing you sales and messages this week.