Shopify Returns: 16 Customer Service Scripts

Returns Customer Service Scripts for Shopify (Email + Chat, 2026)

TL;DR: Effective Shopify returns scripts include templates for refund denials, exchange offers, and lost-package scenarios across both email and chat channels. Forthroute streamlines the entire returns and exchange process for Shopify merchants, automating reverse logistics workflows so your team can handle refunds, RMAs, and customer communications more efficiently.

Last updated: November 2026

TL;DR. 16 plug-and-play CS scripts for Shopify returns — refund denials, exchange offers, lost-package handoffs. Free swipe file.

If you operate returns at scale on Shopify, this guide is one of 25 spokes inside the Shopify Returns Management Hub — start with the pillar for the operator-level overview, then come back here for the deep dive on shopify returns customer service scripts. The short answer to "What customer service scripts should my team use for Shopify returns?": work the framework below, ship the policy wording, and instrument the metric we call out at the end.

Script principles

• Answer the question first. Put the status, the date or the next step in the first sentence.
• Use the customer's details. Order number, item and dates, so they don't have to look anything up.
• Link to the policy, don't paste it. Quote only the line that applies.
• Give one next step and a date. "We'll update you by Thursday" is better than "soon".
• Keep promises you control. Promise when you will issue a refund, not when a bank will show it.

16 swipe-file scripts

Replace the bracketed parts with your own details. Each script is short enough for email or chat.

Starting a return

1. How do I return something? "You can start a return here: [portal link]. Enter your order number and email, choose the item and tell us why. You'll get the next steps by email straight away."

2. Outside the return window. "Thanks for getting in touch. Order [number] was delivered on [date], which is outside our [number]-day return window for a change of mind. If the item is faulty or not what you ordered, reply with a photo and we'll look at it."

3. Item that can't be returned. "[Item] is one of the products we can't take back for a change of mind, because [reason]. If it arrived faulty or damaged, send us a photo and we'll sort it out."

4. Which option should I pick? "If you'd like a different size or colour, choose exchange and we'll hold one for you. If you'd rather have your money back, choose refund. Both are free to choose."

Labels and shipping

5. Sending the label. "Your return is approved. Your label is attached [or: show this QR code at a [carrier] drop-off point]. Please send the item within [number] days so we can process it quickly."

6. Who pays for shipping? "Because the item [arrived damaged / isn't what you ordered], we'll cover the return shipping. For change-of-mind returns, [the label cost of [amount] comes off your refund / you send it back yourself]."

7. Label not working. "Sorry about that. I've made a new label for you: [link]. If the drop-off point still can't scan it, reply here and I'll arrange another way to send it."

Refunds and exchanges

8. Where is my refund? "We received your return on [date] and issued your refund of [amount] on [date]. Banks usually take a few business days to show it. If it isn't there by [date], reply and we'll check with our payment provider."

9. Exchange item out of stock. "The [size/colour] you picked has sold out since you started the return. I can [offer another option] or refund you in full. Which would you prefer?"

10. Partial refund. "We've refunded [amount] for [item]. The remaining [amount] wasn't refunded because [reason, as set out in our policy: link]. If you think we've got this wrong, reply with any photos and we'll take another look."

Problems in transit

11. Return lost on the way back. "Thanks for letting us know. I've opened a trace with [carrier] and will update you by [date]. You won't lose out because the parcel went missing on its way to us."

12. Order marked delivered but not received. "Sorry it hasn't turned up. Tracking shows delivery on [date] at [time]. Could you check with neighbours and your building's mail area? I've also asked [carrier] for proof of delivery and will reply by [date]."

Discrepancies and flagged returns

Use neutral wording here. A flag or a mismatch is a reason to look more closely, not proof that anyone did something wrong, and the decision stays with your team.

13. Returned item doesn't match the order. "We received your return, but the item inside doesn't match what we sent for order [number]: we received [description]. Could you check whether a different item was packed by mistake? Photos of what you sent would help us sort this out."

14. Condition differs from the description. "Thanks for sending this back. When we checked it, we found [condition]. Our policy covers [conditions]: [link]. Can you tell us what happened, or send a photo from before it was posted? We'll review it with that information."

15. Return held for review. "Your return for order [number] is with our team for a manual check before we process it. This is a normal step for some returns, and we'll update you by [date]."

16. Asking for more evidence. "To finish reviewing your return, could you send [photos of the item / the packaging / the serial number]? Once we have them we'll decide within [number] business days and let you know straight away."

Tone-of-voice guardrails

• Write the way you'd speak to a customer at a counter: plain, polite and short.
• Say sorry once when something went wrong on your side, then fix it.
• Never imply a customer is lying. Describe what you found ("the item we received is...") rather than what you think they did.
• Avoid internal terms such as RMA numbers, dispositions or risk scores unless the customer needs them.
• Match the channel: one or two sentences in chat, a little more in email.

Escalation triggers

Hand a conversation to a senior person or a manager when:

• the customer mentions a chargeback, a legal right or a complaint to a regulator;
• a return is flagged for review, or the item received doesn't match the order (scripts 13 to 16);
• the refund or replacement is above an amount your team agreed in advance;
• a carrier claim or lost parcel has not been resolved by the date you promised;
• the customer has written twice without the problem moving forward.

When you escalate, tell the customer who will reply and by when.

Measuring resolution time

Measure the parts of a return separately, because each has a different owner: from request to approval, from approval to the item arriving, from arrival to the refund or exchange being issued, and from issue to the money showing for the customer. The last part depends on the payment provider, not your team. Track the number of messages per return too: if a script keeps leading to a second question, rewrite it.

FAQ

What customer service scripts should my team use for Shopify returns?

Yes — and the framework above gives you the operator answer in under 700 words. 16 plug-and-play CS scripts for Shopify returns — refund denials, exchange offers, lost-package handoffs. Free swipe file.

How does this affect refund cycle time on Shopify?

Most operators see refund cycle time drop from 7-9 days to 3-5 days once the rules above are in place. The biggest single lever is auto-approval for low-risk, low-value returns.

Does Forthroute support shopify returns customer service scripts natively?

Yes. Forthroute ships with the rule engine, customer portal, and Shopify-native integration the framework above assumes. Pricing is free — see pricing.

Where does this fit in the broader Returns Management Hub?

This spoke is one of 25 inside the Shopify Returns Management Hub. The pillar covers the full operator overview; come back to this spoke when you specifically need to solve shopify returns customer service scripts.

Next step

If you want the full operator playbook across all 25 spokes, the Shopify Returns Management Hub stitches them together. If you want to ship this in one afternoon on Shopify, install Forthroute — it's free.

Personalizing Scripts by Return Reason

One of the most common mistakes Shopify teams make is using a single script template across all return scenarios. A customer returning an item because it arrived damaged needs a different tone and outcome path than one returning for a wrong size or change of mind.

Before you deploy any script, map your most common return reasons and write distinct language for each.

For damage claims, lead with acknowledgment and urgency: "We're sorry this arrived in that condition. Here's what we'll do next." Damage almost always warrants a refund or replacement without friction—the customer didn't cause the problem. For fit or sizing returns, you have more room to offer exchanges first: "We'd love to help you find the right fit. Would you like to try a size up/down, or would you prefer a refund?" This keeps inventory moving and often converts to a sale rather than a lost dollar.

For change-of-mind or preference returns, your script can acknowledge buyer's remorse without judgment while gently introducing store credit or exchange incentives. The key is matching script tone to customer intent. A customer who received the wrong item is frustrated; a customer who impulse-purchased and reconsidered is usually just being practical.

Handling Common Edge Cases in Real Time

Your team will encounter scenarios that don't fit neatly into your default rules. A customer claims an item never arrived but tracking shows delivery.

A return was initiated but the package vanished in transit. A customer disputes the condition of the returned item. Having pre-written language for these edge cases reduces decision fatigue and prevents inconsistent responses.

For lost-in-transit returns, a good script acknowledges the situation, explains your investigation window (usually 3–7 business days), and sets clear next steps: "We'll contact the carrier and follow up with you by [date]. If we don't recover it, we'll process a refund/replacement without making you wait." This shows you're taking action and removes uncertainty.

For condition disputes on inbound returns, transparency matters more than defensiveness. "We received your return, and the condition doesn't match what we expected. Can you help us understand what happened during shipping?" This opens dialogue rather than shutting it down. Often you'll learn the item was damaged further in transit, or you'll discover a genuine mistake on your end.

Measuring Script Effectiveness: What Metrics Matter?

You can write beautiful scripts, but if you're not tracking how they perform, you won't know what to improve. Three metrics reveal whether your scripts are working: refund-to-exchange conversion rate, time from initiation to resolution, and repeat-return rate among scripted interactions.

Refund-to-exchange conversion tells you whether your exchange language is landing. If customers almost always choose refunds, your script either isn't making exchanges appealing or you're not offering the right alternative SKUs. Track which product categories or sizes convert to exchanges most often—that's where your script is working.

Resolution speed matters for brand trust. Slow refunds frustrate customers even if the outcome is fair. Log timestamps from return initiation through refund posting to identify bottlenecks. Are scripts getting customers to commit to returns faster? Are scripted responses reducing back-and-forth emails?

Repeat-return rate among customers who received a scripted response compared to those who got ad-hoc replies can reveal whether consistency builds confidence or whether certain scripts encourage future returns.

Why Your Scripts Need Review Cycles

Scripts decay. What works for your spring collection may feel off-brand or clumsy for holiday sales.

Every season, revisit scripts for language clarity, brand voice alignment, and policy updates. Collect feedback from your CS team—they'll catch awkward phrasing faster than anyone. If a script consistently gets pushed back or reworked by team members, it's a sign the wording doesn't match your actual process.

Build script review into your quarterly operations cadence, the same way you'd review return policy or shipping thresholds. One outdated or tone-deaf script can undo months of good customer service work.