Most returns guides treat a return like a package moving backward through a warehouse. Get the label printed, get the box back, restock it, issue the refund, done.
That's half the job. The other half is the phone.
Every return you accept creates a customer who now wants to know one thing: where's my money. They check their email, see nothing, and call. If you run a $10M to $100M Shopify brand with a real support team and a visible phone number, you already feel this. The post-holiday return spike is the seasonal spike that breaks your staffing, and most of those calls are the same question over and over.
This is the build, in order. Write the policy, pick the stack, set up the portal, decide your refund logic, handle the support wave, then measure it. The fifth step is the one almost every guide skips, and it's the one that actually decides whether your returns process feels good or feels like a hold queue.
We run AI phone support for 50+ Shopify brands, and a big share of the calls we answer are returns-driven. If your phone goes to voicemail after 6 p.m. during return season, book a 30-min call and we'll show you how much of that backlog is just "where's my refund."
This post in 30 seconds.
- The full returns build in 6 steps: policy, stack, portal, refund logic, the support wave, and measurement.
- The step everyone skips: returns create a second wave of calls (WISMR, "where's my return") that no portal answers on its own.
- Built for founders, COOs, and Heads of CX at $10M-$100M Shopify brands running a paid helpdesk and a visible phone line.
In this post:
- Why a returns guide has to include the phone
- How I built this guide
- Step 1: write a return policy that prevents calls
- Step 2: pick your returns stack
- Step 3: set up the self-serve portal
- Step 4: decide refund vs exchange vs store credit
- Step 5: handle the support wave
- Step 6: measure whether it works
Why a returns guide has to include the phone
Returns are not a rounding error anymore. The average ecommerce return rate hit roughly 19% to 20% in 2026, two to three times the brick-and-mortar rate, according to 2026 benchmark data from Eightx. Apparel runs around 25%, with shoes north of 31%. Beauty sits near 12%, supplements closer to 7%, pet around 10%. Whatever you sell, one in five to one in eight orders is coming back.
And each one costs you. Processing a single return runs $10 to $65 once you count reverse logistics, inspection labor, restocking, and write-offs, per OneCart's 2026 returns analysis. Only about 48% of returned items get resold at full price. So the financial hit is real before a single human says a word.
Here is the part the warehouse-only guides miss: every return also generates a support contact, and a chunk of those land on your phone line. You already know WISMO, "where is my order," which can be up to half of inbound support calls at around $5 each to resolve, per Salesforce. Returns create the twin of that call: WISMR, "where is my return," or more bluntly, "where is my refund." The customer can't see the box arrive at your warehouse, can't see it get inspected, can't see finance cut the refund. So they call. The anxious ones call twice.
A returns process that ignores this leaves money on two tables. You pay to move the box, and then you pay reps to field calls about a box your system already knows the status of. A good ecommerce returns process closes both.
How I built this guide
I'm Ruben, co-founder of Ringly. I've been running phone support for Shopify brands for the last few years, including 50+ brands live on Ringly right now. The steps below come from real implementation work, not from re-reading competitor blogs.
For this guide I did two things. First, I set up and ran returns flows on real Shopify stores, from the policy settings through the portal to the refund. Second, and this is the part nobody else has, I went through the return-related call transcripts across the brands we run and counted what people were actually calling about.
- I tracked which return calls were just status checks. The single biggest returns-driven call type was WISMR, the "where's my refund" call. Almost none of them needed a human. The customer wanted a number and a date.
- I logged where the calls clustered. They spiked in the two weeks after a sale and hard after the holidays, exactly when a support team is already underwater.
- I checked what a self-serve portal alone solved. Portals cut the form-filling calls. They did not stop the "I returned it five days ago and I'm worried" calls, because those callers want reassurance, not a form.
So when this guide gets to the support step, it isn't theory. It's the call pattern I watched across real stores, with real resolution numbers behind it.
Step 1: write a return policy that prevents calls
Your return policy is the first support tool you own, and most brands write it as legal cover instead of as a script. Do it right and it answers the question before the customer picks up the phone. 84% of shoppers read the return policy before they buy, and 92% will buy again when the returns experience is easy, per Easyship's returns research.
Five decisions make up the policy. Make each one on purpose.
| Policy decision | Common 2026 choice | Why it matters |
|---|---|---|
| Return window | 30 days from delivery | 30 is the standard buyers expect; under 14 reads as hostile |
| Who pays return shipping | Free for exchanges, fee for refunds | Nudges toward exchanges, protects margin |
| Item condition | Unused, original packaging | Keeps resale value, cuts fraud disputes |
| Exclusions | Final sale, perishables, intimates | Stops the calls you can't win |
| Default resolution | Exchange or store credit first | Keeps the revenue instead of refunding it |
Be specific about when the window starts. "30 days from delivery" creates far fewer disputes than "30 days," because the customer and your rep are reading the same clock. If you need a starting point, Ringly has a free return policy generator and a library of return policy examples you can copy from.
A vague policy doesn't save you a decision, it just moves that decision to a phone call. Put the policy on the product page, the checkout page, and the order confirmation email. Every place it appears is a call it prevents. For the deeper version, our guide on writing an ecommerce return policy walks through the wording line by line.
Step 2: pick your returns stack
You have two paths: Shopify's native return rules, or a dedicated returns app on top of them. The right call depends on volume.
Shopify's built-in return rules live under Settings, then Policies, then Return rules. You set the window, the return shipping cost, and which items are final sale. For a brand doing a few returns a day, that plus a manual refund is genuinely enough. Don't pay for software you don't need yet.
Once returns become a daily grind, a dedicated app earns its fee. Here's the honest landscape.
| Tool | Best for | Entry price |
|---|---|---|
| Shopify return rules | Low volume, simple policies | Included with Shopify |
| AfterShip Returns | Cheap entry, global carriers | From $9/mo |
| Loop Returns | Shopify DTC, exchange-first | $97-$447/mo and up |
| ReturnGO | Flexible policy, instant exchange | From $147/mo |
AfterShip is the budget door, with the widest carrier coverage if you ship internationally. Loop is the Shopify-native heavyweight built around pushing exchanges instead of refunds, which is why high-AOV apparel brands like it. ReturnGO leans into instant exchanges, where the replacement ships before the return arrives, and it works across platforms if you're not Shopify-only.
Pick the tool that matches your return reason, not the one with the longest feature list. If your returns are sizing-driven, exchange-first software pays for itself. If they're defect-driven, you want strong inspection and data, not a fancier exchange flow. Our roundup of the best returns management software and our list of the top Shopify returns apps go tool by tool.
One thing to be clear about: none of these tools answer your phone. They run the form and the label. The calls about that form are still yours, which is step 5.
Step 3: set up the self-serve returns portal
The portal is where the customer starts the return without emailing or calling you. This is the friction killer, and it's worth getting right.
A good portal does four things:
- Authenticates the order. Customer enters an order number and email, the portal pulls the order. No back-and-forth to verify who they are.
- Applies your policy automatically. Items outside the window or marked final sale get blocked at the portal, not after a rep has already promised a refund.
- Generates the RMA and label. The return authorization and prepaid label come back instantly, so the customer can drop the box that day.
- Sets the resolution path. Refund, exchange, or store credit, chosen by the customer inside the rules you set.
Behind the portal, set up a processing zone with a target. The brands that handle returns well inspect and resolve inbound returns within 24 to 48 hours of arrival. That speed is not just operational tidiness. Every day a return sits uninspected is a day the customer wonders where their money is, and a day closer to them calling.
If you offer instant exchanges, you cut the wait entirely. The replacement ships on return initiation, the customer's anxiety drops, and the "where's my exchange" call never happens. That single move can remove a real slice of your returns-related contacts. Pair the portal with proactive ecommerce order tracking so the return trip is as visible as the original delivery.
Step 4: decide refund vs exchange vs store credit
Resolution is where margin lives or dies. A refund hands the money back. An exchange or store credit keeps the revenue and keeps the customer. So your default should bias toward keeping the sale, without making the customer feel trapped.
A simple rule of thumb:
- Defect or our error: instant refund or replacement, no friction, you pay shipping. This is reputation insurance.
- Sizing or changed mind: offer an exchange or store credit first, with a refund available if they insist. Sweeten the credit (a small bonus) to make it the easy choice.
- Outside policy: store credit as a goodwill gesture, case by case, not as a default.
Build a fraud gate into this step. Return fraud, things like wardrobing and empty-box returns, runs 10% to 15% of total return volume, per MakeMyReceipt's 2026 retail returns report. You don't need to treat every customer like a suspect, but flag repeat high-return accounts and require inspection before refund on flagged orders.
The faster and clearer the resolution, the fewer follow-up calls it generates. A refund that lands in 2 days with an email confirmation produces silence. A refund that takes 10 days with no update produces a phone call, maybe two. Our guides on ecommerce refunds and Shopify exchanges cover the mechanics for each path.
Step 5: handle the support wave (the step everyone skips)
Here's where the build usually ends and reality begins. You've got a clean policy, a good app, a self-serve portal, and fast refunds. Customers still call.
They call because returns are emotional in a way a normal purchase isn't. The money is already theirs in their mind, and they can't see it coming back. A portal answers "how do I start a return." It does not answer "I sent it back five days ago, where's my refund," because that caller doesn't want a form. They want a person to tell them a number and a date. That's WISMR, and it's the single biggest returns-driven call type I see across the brands we run.
Two things fix it together. First, proactive status updates at every stage: return received, return inspected, refund issued or exchange shipped. Each notification removes a reason to call. Second, a live channel for the callers who still pick up the phone anyway, because some always will, and they're disproportionately your repeat buyers.
That second piece is where Ringly fits. Ringly.io is AI phone support for Shopify brands. Instead of hiring a seasonal phone team every January, the AI answers inbound calls 24/7 and handles the routine returns calls: where's my refund, how do I return this, did you get my package back. It pulls the order from your Shopify store, reads the return status, and tells the customer the number and the date they called for. Across 50+ brands, the AI resolves about 73% of calls on its own at roughly $0.42 per resolved call. The genuinely tricky ones escalate cleanly to Gorgias, Richpanel, Reamaze, or whatever helpdesk you already run.
TechCraft Studio, a brand on Ringly, handles 88% of its calls without a human. And WashCo, a Shopify brand we launched, recovered $22,664 in attributed revenue in its first 7 days on the phone, because the AI was rescuing calls a voicemail box used to swallow.
"My customers also feel like it's a normal person. They feel like they can communicate if they have questions."
Claudia Droge, TechCraft Studio
Run the math on the seasonal spike. Take a $50M Shopify brand running a 6-rep CS team:
| Line item | Today | With Ringly |
|---|---|---|
| 6 reps × $4K loaded per rep | $24,000/mo | n/a |
| Ringly Enterprise (~$5K/mo) | n/a | $5,000/mo |
| Net monthly CS spend | $24,000/mo | $5,000/mo |
| Monthly savings | n/a | $19,000/mo |
| Annual savings | n/a | $228,000/yr |
That's roughly 70% of your returns-season calls (the WISMR, the WISMO, the how-do-I-return) routed to the AI. The other 30%, the genuinely complex calls, still go to your team, who now have time to actually solve them instead of reading tracking numbers off a screen.
If returns season turns your phone line into a voicemail graveyard, book a 30-min call and we'll do the math live on your numbers.
For the channel-specific playbooks, see our guides on WISMO calls, 24/7 ecommerce phone support, and using an AI receptionist for ecommerce.
Step 6: measure whether your returns engine works
You can't fix what you don't watch. Most brands track the return rate and stop there. The return rate tells you how many came back. It doesn't tell you whether your process is good or whether it's quietly costing you repeat buyers.
Track these six, monthly:
| Metric | What it tells you | Healthy direction |
|---|---|---|
| Return rate | Volume coming back | Stable to down, by category |
| Refund cycle time | Days from return received to refund issued | Under 48 hours |
| WISMR contact rate | % of returns that generate a "where's my refund" contact | Down as updates improve |
| Support deflection | % of return calls resolved without a human | Up |
| Return-to-exchange ratio | How much revenue you keep vs refund | Up |
| Repeat purchase after return | Did they come back | Up (this is the whole game) |
The two that move together are WISMR contact rate and support deflection. Tighten your status updates and the contact rate falls. Add a live AI channel for the contacts that remain and your deflection rises, so the calls that do come in stop eating rep hours. Our breakdown of customer service KPIs for ecommerce and first-call resolution gets specific on targets.
The brands that win returns aren't the ones with the lowest return rate, they're the ones whose customers come back after returning. A smooth return is one of the strongest loyalty moments you get, if you don't blow it on a voicemail box. For the full data picture, our 2026 ecommerce return statistics page has the benchmarks to compare yourself against, and our broader guide to ecommerce customer service ties returns back into the wider support operation.
Frequently asked questions
How do I set up returns for my online store? Start with a clear return policy (window, who pays shipping, condition, exclusions, default resolution), then turn on Shopify's native return rules under Settings, Policies, Return rules, or add a dedicated returns app if volume is high. Add a self-serve portal so customers initiate returns themselves, and plan for the support calls that returns still generate.
What should my return window be? Thirty days from delivery is the 2026 standard and what most buyers expect. Anything under 14 days reads as hostile and drives disputes. Some brands extend to 90 days, which can lift conversion because longer windows reduce purchase anxiety.
Who should pay for return shipping? Cover shipping when the return is your fault (defect or wrong item), and consider a small fee on change-of-mind refunds. A common move is free shipping on exchanges and a deducted fee on refunds, which nudges customers toward keeping the revenue with you.
Should I refund, exchange, or give store credit? Default toward exchange or store credit to keep the revenue, with a refund available if the customer insists. Reserve instant no-friction refunds for defects and your own errors. Sweetening store credit with a small bonus makes it the easy choice for changed-mind returns.
What's the best returns app for Shopify? It depends on your return reason. Loop Returns is strong for exchange-first DTC brands, ReturnGO for flexible policies and instant exchanges, and AfterShip for cheap entry and global carriers. For low volume, Shopify's native return rules are enough.
Does a returns portal stop the phone calls? No. A portal cuts the "how do I start a return" calls, but it doesn't answer the "where's my refund" calls, because those callers want reassurance, not a form. You need proactive status updates plus a live channel to handle the ones who call anyway.
How do I reduce return-related support calls? Send a status update at every stage (received, inspected, refunded), resolve returns within 24 to 48 hours, and offer instant exchanges so the wait disappears. For the calls that remain, an AI phone agent can answer order and refund-status questions 24/7 and escalate the rest.
How does AI phone support fit into a returns process? It handles the support wave that returns create. Ringly answers inbound calls 24/7, pulls the order and return status from Shopify, and resolves routine "where's my refund" and "how do I return this" calls automatically, escalating complex cases to your helpdesk. Across 50+ brands it resolves about 73% of calls on its own.
Talk to us

If you run a $10M-$100M Shopify brand and your phone line drowns every return season, a 30-min call is the fastest way to see how much of that backlog is just refund-status calls your system could answer on its own.
The 3-layer guarantee.
- Live in 14 days or it's free until launched.
- 65% resolution in 90 days or we refund the last 3 months of subscription fees.
- We keep working free until we hit 65%.
Ruben (Ringly co-founder) takes these calls personally.






