Here is everything that goes in an ecommerce return policy, plus the copy-paste version.

• The 7 clauses every policy needs, a clause-by-clause breakdown of what each one should say, and a full fill-in-the-blank template you can paste into your site today.
• A 30-second test for whether your policy actually answers customer questions or just sends them to the phone.
• Written for founders and Heads of CX at $10M-$100M Shopify brands running a paid helpdesk and a visible phone line.

Most return policies read like they were written by a lawyer who has never talked to a customer. They cover the store legally and answer almost nothing the customer actually wants to know. So the customer does the obvious thing. They call.

I went through a week of return-status call transcripts before writing this template. The pattern was hard to miss. Almost every return call traced back to a line the policy left out, or buried so deep nobody scrolled to it.

A good return policy is not a legal document. It is the answer to the questions your customers would otherwise call your support team about. Write it that way and a real chunk of your "where's my order" and "where's my refund" volume just stops.

If you run customer experience at a Shopify brand doing $10M-$100M, you already know the Monday return backlog. This is how to write the policy so it does some of that work for you. Book a 30-min call and we'll show you which of your return calls a clearer policy would have caught.

Why your return policy is a phone-call generator

Returns are not a small slice of your support load. Ecommerce return rates average around 20%, and spike to 30% during the holiday season (ShipBob). One in five orders comes back, and the ecommerce return statistics only get heavier in Q4. Every one of those is a potential ticket, and a good share of them become phone calls.

Here is the part that gets missed. The call usually isn't about the return itself. It's about a detail the policy didn't make obvious.

A vague return policy doesn't just frustrate customers, it converts them into inbound calls your CS team has to answer the same way over and over. When we read return-related call transcripts across the 50+ Shopify brands on Ringly, the two clauses that drive the most calls are the ones most policies leave out: how to actually request a return, and when the refund lands. Every other clause is scannable. Those two send people to the phone.

That matters more than it sounds. More than 60% of consumers read a return policy before they buy (ShipBob), so the policy is doing conversion work and support work at the same time. And when a customer can't get a clear answer and calls, the math gets ugly fast: 85% of callers who can't reach a person never call back, and 62% switch to a competitor (PCN).

Return-status calls are WISMO's twin. WISMO ("where's my order") already runs 30-40% of tickets, and over half at peak (Salesforce). "Where's my refund" rides right behind it. Both come from the same root cause: the customer can't self-serve the answer, so they pick up the phone. The fix for both starts in the policy text. If you want the order-side version of this, our guide to WISMO calls covers it.

The 7 clauses every return policy needs

A complete return policy answers seven questions before the customer has to ask. Miss one and that question becomes a call. Here is each clause, what it should say, and the call it prevents. (This post is about the policy text itself. If you want to cut the number of returns in the first place, that's a different job, covered in how to reduce product returns.)

1. The return window

State how many days the customer has, and when the clock starts. The expectation floor is 30 days (ShipBob). Plenty of brands run 14, and premium brands stretch to 60 or 90. Apple holds a 14-day window, IKEA runs 365 (Shopify).

The detail that prevents calls: name the start date. "30 days from the delivery date" is cleaner than "30 days from purchase," because it kills the "but it just arrived" argument before it happens. Ambiguity on the window is one of the most common reasons people call to ask if they still qualify.

2. Item condition

Spell out what condition an item has to be in to come back. The standard is unused, in original packaging, with tags attached, and proof of purchase.

Then list what disqualifies a return. Worn, washed, opened hygiene seals, opened supplements. Be specific. A customer who reads "must be unused" and isn't sure whether their situation counts will call to find out. A customer who reads the exact disqualifier won't.

3. Who pays return shipping

This is the most-scanned line in the whole policy, so make it unmissable. 79% of customers won't buy from a store that charges return shipping (ShipBob), which means this clause is doing real conversion work, not just support work.

You have three sane options. Free returns (best for conversion, hardest on margin). Customer-paid (protects margin, costs you sales). Or the hybrid: free return shipping on exchanges only, customer-paid on refunds. The hybrid steers people toward exchanges, which keeps the revenue. A good returns app can enforce whichever rule you pick automatically. Whichever you pick, state it in one plain sentence. If you're weighing how generous to go, our breakdown of whether a generous returns policy actually makes you money runs the numbers.

4. Refund, exchange, or store credit

Tell the customer what they get back and what choices they have. The default is a refund to the original payment method. Offer exchange and store credit as the friendlier paths, since both keep the revenue inside your brand.

Make the choice explicit in the policy. "Choose a refund, an exchange, or store credit" reads better than making the customer guess which one they're allowed to ask for.

5. Exceptions and final-sale items

This is the clause that prevents your angriest calls. List everything that can't be returned: sale and clearance items, personalized or custom products, intimate or hygiene items, perishables, opened consumables.

A customer who buys a final-sale item, then tries to return it, then finds out at the worst possible moment, is the customer who calls upset and posts about it. The exception clause, stated up front and repeated on the product page for final-sale items, is cheap insurance against that exact scenario. WashCo, a Shopify brand we launched recently, deflected 85% of its calls once the routine answers were available without a human, and clear exception rules are a big part of why those calls never needed a rep.

6. How to request a return

This is the clause most policies leave out, and it's the single biggest call driver we see. Don't just say "contact us." Give the literal steps.

• Where to start. A returns portal link, or the exact email address to write to.
• What to include. Order number, the reason for the return, and a photo if the item arrived damaged.
• What happens next. "We'll send a prepaid label or instructions within one business day."

When this clause is missing, the customer who's ready to return has no path, so they call to ask for one. When it's present and specific, they self-serve. For the refund email side of the handoff, our refund email generator writes the template, and if your reps field these by phone, customer service scripts keep the answers consistent.

7. The refund timeline

State how long a refund takes after you receive the item. 72% of online customers expect a refund credit within 5 days (ShipBob), so this is the expectation you're managing. Name an actual number.

"Once we receive your item, refunds are processed within 5 to 7 business days" answers the question. Add the bank-delay caveat too ("your bank may take a few extra days to post it"), because that gap is what generates the second call, the one that comes after you've already issued the refund. Both of those "where's my refund" calls disappear when the timeline is on the page.

Copy-paste ecommerce return policy template

Here's the full template. Fill in the brackets, drop it on your returns page, and you've covered all seven clauses. If you'd rather generate a custom version, our return policy generator builds one for you.

Returns and refunds

We want you to love what you ordered. If something isn't right, here is exactly how returns work.

Return window. You have [30] days from the delivery date to start a return.

Condition. Items must be unused, in their original packaging, with tags attached. [Opened supplements, personalized items, and final-sale items] cannot be returned.

Who pays shipping. We cover return shipping on exchanges. For refunds, return shipping is [$X / deducted from your refund].

What you get back. Choose a refund to your original payment method, an exchange, or store credit.

Exceptions. [Sale and clearance items, personalized products, and opened hygiene or consumable items] are final sale and cannot be returned.

How to start a return. Go to [returns portal link] or email [returns@yourbrand.com] with your order number and the reason. We'll send a prepaid label or instructions within [1 business day].

When you get your refund. Once we receive your item, refunds are processed within [5 to 7] business days to your original payment method. Your bank may take a few extra days to post it.

Questions. Call or text us at [number] or email [support@yourbrand.com]. We answer [24/7].

Two notes on using it. First, keep the bold labels. Most customers don't read the policy top to bottom, they scan for the one line they need, so the labels are how they find it. Second, mirror the same wording on your product pages for anything final-sale. The policy and the PDP should never disagree, because when they do, the customer calls to find out which one is true.

"My customers also feel like it's a normal person. They feel like they can communicate if they have questions."
— Claudia Droge, TechCraft Studio

For the Shopify-specific version of these rules, including how the policy interacts with your returns app and refund settings, see our Shopify return policy best practices. For the broader process around the policy, the handling, the routing, the follow-up, see our ecommerce returns best practices. And if your returns operation itself needs work, not just the policy text, start with ecommerce returns management.

The 30-second readability test

Once you've written the policy, run it through one test. Hand it to someone who's never seen it and ask them to find three answers: how many days do I have, do I pay for return shipping, and how do I start a return. If they can't get all three in 30 seconds, the policy will keep generating calls.

A return policy that fails the 30-second scan test is a policy your phone line is paying for. The fix is almost always formatting, not content. Use bold labels, short lines, and one idea per line.

Then make sure the policy is actually where customers look:

• Footer link on every page, labeled "Returns" or "Returns and refunds."
• Product page, especially for final-sale or non-returnable items.
• Order confirmation email and the post-purchase flow, since that's when buyer's remorse hits.
• Returns portal, so the steps live next to the action.

A policy buried two clicks deep doesn't reduce calls, because nobody finds it before they reach for the phone. The clearer it is and the more places it lives, the fewer "how do returns work" calls hit your team. That ties straight into ecommerce customer retention, since a smooth return is one of the strongest reasons a customer comes back.

What it costs to keep answering these calls by phone

Even a perfect policy doesn't take return calls to zero. Some customers will always want to confirm their refund is on the way, or ask about an edge case the policy didn't anticipate. The question is who handles those, and at what cost.

Take a typical $50M Shopify brand running a 6-rep CS team:

A big slice of that 6-rep load is repeatable: return-status checks, refund-timeline questions, "how do I start a return." Those are exactly the calls a clear policy plus an AI phone agent can absorb, which frees your reps for the genuinely hard calls. It's the same lever that makes the rest of your ecommerce customer service cheaper to run.

If returns are a real chunk of your phone volume, book a 30-min call and we'll do the math live on your actual call data.

Frequently asked questions

What should an ecommerce return policy include?

Seven clauses: the return window, item condition, who pays return shipping, refund versus exchange versus store credit, exceptions and final-sale items, how to request a return, and the refund timeline. Miss any one and that question turns into a support ticket or a phone call. The "how to request" and "refund timeline" clauses are the most commonly omitted and the biggest call drivers.

How many days should a return window be?

30 days is the expectation floor, since that's what most online customers expect (ShipBob). Plenty of brands run 14 days, and premium brands stretch to 60 or 90 to signal confidence. Whatever you pick, state the start date clearly, ideally "from the delivery date," to avoid disputes about when the window opened.

Should customers pay for return shipping?

It depends on your margins, but be aware that 79% of customers won't buy from a store that charges return shipping (ShipBob). A common middle ground is free return shipping on exchanges only and customer-paid on refunds, which protects revenue while staying competitive. Whatever you choose, state it in one plain sentence near the top of the policy.

Refund, exchange, or store credit, which should I offer?

Offer all three and let the customer choose. The default is a refund to the original payment method, but exchanges and store credit keep the revenue inside your brand, so lead with those as the friendly options. Making the choice explicit in the policy stops customers from calling to ask what they're allowed to request.

Where should I display my return policy?

In your site footer on every page, on product pages (especially for final-sale items), in the order confirmation email, and inside your returns portal. A policy buried two clicks deep doesn't reduce calls, because customers reach for the phone before they find it. The clearer and more visible it is, the more support volume it absorbs.

Can AI handle return and refund-status calls?

Yes. Return-status and refund-timeline questions are highly repeatable, which makes them ideal for an AI phone agent. Across 50+ Shopify brands, Ringly resolves about 73% of inbound calls autonomously at roughly $0.42 per resolved call, and escalates the genuinely complex ones to your team. A clear policy deflects the easy questions; the AI handles the ones that still come in.

Talk to us

If return and refund-status calls are eating your phone line, a 30-min call is the fastest way to see what a clear policy plus an AI phone agent would deflect. We'll pull your recent return calls, run the math on what they're costing you, and show you what's recoverable.

The 3-layer guarantee.

1. Live in 14 days or it's free until launched.
2. 65% resolution in 90 days or we refund the last 3 months of subscription fees.
3. We keep working free until we hit 65%.

Ruben (Ringly co-founder) takes these calls personally.

Book a 30-min call →