Dropshipping Returns and Refunds: Policy Wording and AI Replies

Treat every dropshipping return as your own: the customer bought from you, so you owe the refund even when the supplier will not take the goods back. Write the policy around what each supplier actually accepts, set a refund-only limit for cheap items, and let AI draft replies you approve before they are sent.

The trouble is the gap between what you promise and what the supplier will credit you. A shopper who is told "return it within 30 days" will not care that your supplier's warehouse refuses returns, and a processor such as Stripe keeps its original fee when you refund. So the order of work matters: supplier terms first, policy second, reply templates third.

Follow me on Instagram@sagnikteaches

Where the money and the promise come apart

In a dropshipping store you take the payment, the supplier ships, and the customer's contract is with you. Three separate agreements sit behind one sale: the buyer's agreement with your store, your agreement with the supplier, and the payment provider's rules. A refund touches all three, and they rarely line up.

Connect on LinkedInSagnik Bhattacharya

Take a desk lamp sold for $34. Your supplier charged $11 for the lamp and $4 for shipping. Your card processor took a fee on the $34 when the order was paid. If the lamp arrives broken and you refund the full $34, the sale is gone, but the $15 you paid the supplier and the processor's fee are already spent, so everything rests on whether the supplier credits that $15. Best case it does, and you are out only the fee and the ad spend that found the buyer. Worst case it credits nothing, and the order has cost you $15 plus the fee and the ad spend, with nothing earned.

Subscribe on YouTube@sagnikteaches

Stripe's refund documentation says its processing fees from the original transaction are not returned when you refund (other providers set their own rules, so check yours). That is why returns are a margin question as much as a customer-service one, and why the policy should be written from the money outwards.

Read each supplier's terms before writing your policy

Open a spreadsheet and give every supplier one row. You are collecting six facts, and each one decides a line in your policy.

• Accepts returns at all? Yes, no, or only for faulty goods.
• Return address. A real address the buyer can post to, or none. Note whether it is somewhere a buyer would pay heavily to post a parcel to.
• Who pays return postage. Often the buyer, which makes a return of a $12 item pointless.
• Credit for faulty, wrong or damaged items. The claim window in days and the evidence needed, usually photos or a short video.
• Credit for change-of-mind returns. Often none, or a restocking deduction.
• Time to credit. How long between you filing the claim and the money or credit arriving.

Here is a filled-in row for a made-up supplier, purely as an illustration of the level of detail:

Two rows like this and you will already see the pattern: the supplier's window is shorter than the one you want to offer. Your public window can be longer than the supplier's, but then you are carrying the difference as your own cost. Decide that deliberately rather than by accident.

Return address problems and how to solve them

The return address is where dropshipping policies most often fall apart. The common situations are below, each with a workable answer.

The supplier refuses returns

Do not write "returns accepted" on the page and hope. Either say plainly that returns are accepted only for faulty or wrong items, or promise a refund without return for items below a set value. The policy must match what you can actually deliver.

The supplier's address exists but is far away or costly

If posting a $14 item back costs the buyer $18, a return is absurd. Offer a refund-only outcome for the whole product line. Do not give the buyer that address as a courtesy: customers who post parcels to it and get nothing back become chargebacks.

You hold the stock yourself for some lines

Mixed stores sell some items from a small home or storage stock and the rest by dropship. Give your own address for the first group only, and make the product page say which group each item belongs to. A single policy page can carry two short sections, headed by how the item ships.

The parcel comes back to the wrong place anyway

Buyers sometimes return an item to the sender label they were given in the box. Add a line to your confirmation emails: "Please do not return an item before we confirm it. Unapproved parcels may not be accepted." Pair it with an AI-drafted reply for the moment a stray parcel shows up (see the templates below).

Refund-only rules: the number that decides them

A refund-only rule means you refund the buyer without making them return the goods. It sounds generous and it is, but it is often the cheapest option. The test is simple arithmetic: compare where each outcome leaves the order once the customer has been sorted out.

Illustrative figures for a $34 lamp with a $15 landed cost, before ad spend ("fee" is the processing fee you do not get back):

A workable rule many small stores settle on is a value threshold. Under a limit you choose, say $25 landed cost, a faulty-item claim is refunded with no return and a photo is enough. Above it, you ask for the return or at least a photo of the damage, and file the supplier claim before you refund. The threshold is yours to set: look at your last three months of refund tickets, take the median item value and the median supplier credit, and put the limit where returning costs more than it saves.

One practical safeguard: refund-only should not become a loophole. Ask for a photo or short video on every refund-only claim for faulty goods, keep a count per customer, and flag anyone with three or more refund-only claims in a quarter for your own review. That is a rule you apply by hand to a short list, not something to automate.

Policy wording that matches what you can deliver

A returns page needs to answer four questions in plain words: what can come back, by when, who pays, and what the buyer gets. Everything else belongs below the fold. Here is wording for a store with one overseas supplier and a refund-only limit, written to be adapted. It is not legal advice, and where you sell to consumers in places with statutory rights, those rights apply on top of anything the page says.

Returns and refunds

If your order arrives damaged, faulty or not as described, tell us within 14 days of delivery. Send your order number and a photo or short video of the problem. We will confirm what happens next within 2 working days.

For items under $25 we usually refund you in full and you keep the item, so there is nothing to post back. For items over $25 we may ask you to return it. We will give you a returns address and cover the postage if the fault is ours. Please do not send anything back before we confirm, because unapproved parcels may not reach us.

If you simply change your mind, tell us within 14 days of delivery and we will explain your options. We are not able to accept change-of-mind returns on every product, and each product page says which apply.

Refunds go back to your original payment method. Most arrive within 5 to 10 working days of approval, depending on your bank.

The page quotes the price the buyer paid, because buyers cannot see your landed cost. Your internal limit can be more generous than the page, as the lamp example below shows, but never less generous.

Read that against your supplier row. "14 days" for the buyer and "7 days" from the supplier means you must file claims fast, so record the delivery date the moment a ticket arrives. If your supplier gives only credit notes, replace "refund" in your workflow with a step to buy a replacement from another source. The page promises an outcome, not a method.

Two wording traps are worth removing: "all sales final" on goods that could be faulty, which many buyers are entitled to challenge anyway, and "we will refund you as soon as we receive the item" when you have no address to receive it. Both create complaints that your own page started. Have a qualified adviser read the finished page for the markets you sell into, because consumer rules vary and a template cannot know which apply.

Sorting tickets so AI helps without deciding

AI is a good clerk and a poor decision-maker. Use it for three things: classify an incoming message, draft a reply in your tone, and pull the facts you need to check (order number, delivery date, product). You make the money decision.

A practical sort has six case types, each with a default outcome you set in advance:

1. Damaged or faulty on arrival. Evidence request, then refund or replacement per your threshold.
2. Wrong item. Photo of the label, then replacement or refund; claim from the supplier.
3. Not as described. Needs your judgement: is the listing misleading, or is the buyer's expectation off?
4. Changed my mind. Follow the product's stated policy; many dropship products carry a smaller promise.
5. Late or lost parcel. This is a delivery issue, not a returns one; check tracking first. The chatbot tutorial on order tracking and returns covers that boundary.
6. Anything involving a chargeback, legal threat, safety concern or allergy or skin reaction. Straight to you, never an AI draft sent unseen.

For the sorting step, paste the message into a chat assistant (ChatGPT, Claude or Gemini all work) with a standing instruction. A Project in ChatGPT or Claude holds your policy and tone notes so you do not repaste them each time. Custom GPTs are scheduled to stop running on 11 December 2026, so use a Project rather than building one.

You are drafting replies for a small online store that uses dropship suppliers.

Policy (use only this, never invent terms):
- Faulty, damaged or wrong item: report within 14 days of delivery with a photo.
- Under $25 item value: full refund, buyer keeps the item. Over $25: we may ask for a return.
- Change of mind: depends on the product page; say we will check and reply within 2 working days.
- Never promise a refund date beyond "5 to 10 working days after approval".
- Never give a returns address; the owner will provide one if needed.

For each customer message I paste, output:
1. CASE TYPE (one of: damaged, wrong item, not as described, change of mind, late or lost, escalate)
2. MISSING FACTS (order number, delivery date, photo, anything else needed)
3. DRAFT REPLY, under 120 words, warm and plain, with [first name] and [your name] as placeholders.
4. ONE LINE for the owner: what decision I need to make.

One ticket, start to finish: the cracked lamp base

Here is a made-up customer message and what a well-instructed assistant gives back. Figures and wording are illustrative.

The customer writes: "Hi, the lamp you sent arrived with the base cracked right across. Order 10482. I want my money back."

CASE TYPE: damaged
MISSING FACTS: photo or video of the crack; delivery date (not given)
DRAFT REPLY:
Hi [first name], I'm sorry the lamp arrived cracked. To sort this quickly, could you send a photo or short video showing the damage, and tell me the date it arrived? Once I have that I'll confirm your refund or a replacement within 2 working days. There's no need to send the lamp back unless I ask. Thanks, [your name]
OWNER DECISION: item value $34 is over the $25 limit, so a return may be needed. Check the delivery date is within 14 days, then choose refund, replacement or return; file the supplier claim today.

What would you fix? The draft is right to ask for the photo before promising anything. But the reply and the owner line contradict each other: the reply tells the customer there is no need to send the lamp back, while the owner line says a return may be needed. The cause is the instruction. It says "item value", so the assistant measured the $34 sale price, while your rule is about landed cost, and the lamp's landed cost is $15, under the $25 limit. Change the instruction to "Under $25 landed cost (shown in the order notes)" and the two lines agree: no return needed, which also suits a supplier with no usable return address. Silent mismatches like this one are why the owner line exists, and why you read it before pressing send.

The outcome for the owner: delivery was 5 days ago, within window. The photo shows a clear fault. Refund $34, file a supplier claim within the 7-day window for the $15 landed cost, and wait. If the supplier credits, the order costs you the processing fee and the ad spend; if not, it costs you $15 more. Record both outcomes in a column, because after twenty tickets you will see the true cost of each supplier.

Reply templates AI can draft for the awkward cases

These are the moments store owners dread. Each template below is a starting point you tune in your own voice; ask the assistant to produce a version for your store using the policy above, then edit.

Buyer wants to return something the supplier will not take

Before: "Our policy doesn't allow this." After: "Thanks for letting me know. This product ships directly from the manufacturer, who does not take returns for change of mind, so I can't offer a postal return. What I can do is [partial refund of X, or a discount on a future order]. Would that help?" The second version states the limit, gives the reason in one clause, and puts an option on the table. It also avoids over-promising.

A parcel arrives at your door unannounced

Draft a reply that confirms receipt, explains that the return was not approved, and says what you will do next. For example: "Thanks for sending this. We hadn't approved a return, but now that it has arrived I'll look at your order and write to you within 2 working days." Decide in advance whether you will refund these. The safer rule is to treat an unapproved arrival as a normal return request and apply the policy.

The buyer disputes the charge with their bank

Do not draft this one with AI and send it unseen. A chargeback response goes to the payment provider with evidence, such as the order, tracking and your policy page at the time of the sale. An AI assistant can help you assemble the list of evidence, but you check every attachment. If the buyer is willing, a refund before the dispute completes is often simpler than contesting it.

The mistake that cost a store two weeks of supplier credit

As an illustration, take a store that promised a 30-day return window and refunded promptly, but filed supplier claims in batches at month end. Its supplier required claims within 7 days of delivery. Every claim older than a week was rejected, and the owner absorbed the cost without noticing until a spreadsheet showed 11 rejected claims in a month. Nothing in the tickets showed it: the customers were happy, the refunds were fast, and the loss was invisible.

The fix was mechanical. Add a "claim by" date (delivery date plus the supplier's window) to every damaged or wrong-item ticket the moment it arrives, and review the list every morning. AI can fill that date in from a pasted tracking page, but the review is a human habit. Pair it with a monthly look at the pattern of faults per product; our tutorial on spotting patterns in complaints, returns and defects shows how to do that with a simple export.

Working out what returns really cost you

Do one sum a quarter. Take your orders, refunds and supplier credits for the period. Illustrative figures for a store with 600 orders in a quarter:

• Revenue: 600 orders at an average of $38 = $22,800
• Refunds issued: 42 orders, averaging $34 = $1,428 (7% of orders)
• Supplier credits received: 17 of those, averaging $14 = $238
• Processing fees lost on refunded orders: about 42 times $1.30 = $54.60 (assuming a fee of about $1.30 per $38 order; use your own rate)
• Net cost of returns: $1,428 minus $238, plus $54.60 = $1,244.60

That is about 5.5% of revenue, and it is the figure to price into your margins. If you are running ads, the returns cost has to come out of the profit per sale, not out of thin air. If a supplier's claim rate is far below the rest, look at their terms or switch products. The ecommerce operations tutorial covers how to compare suppliers on this kind of data.

Putting AI on the replies without losing control

Set up the workflow in four steps and keep it for a month before widening it.

1. Week 1. Paste each incoming returns message into your Project and read the classification and draft. Edit before sending. Note every time the assistant got the case type wrong.
2. Week 2. Add the corrections to your standing instruction as one-line rules, such as "A cracked item under $25 landed cost never needs a return".
3. Week 3. Let the assistant draft straight into your helpdesk or inbox as saved drafts. You still press send.
4. Week 4. Count the drafts you sent unedited. If it is over 80% across at least 40 tickets, think about auto-sending only for the lowest-risk type, such as acknowledging a request, and keep refund decisions with you.

If you later put the same policy into a store chatbot, build the flows deliberately; designing the returns flow and guardrails that stop a bot promising what you do not offer cover how. For a wider tour of other jobs, eight jobs a small store can hand over puts returns in context.

How to check the policy works in practice

A policy is only proven by real tickets. Take your last ten returns requests and run each through the page as if the buyer had only that page to go on. For each one, ask whether the page would have told them what to do, whether the outcome you gave matches the page, and whether the supplier terms allowed your outcome. Any ticket where the answer is no points to a line to change.

Then check three numbers monthly: refund rate (refunded orders over total orders), claim recovery rate (supplier credits over refunds that were claimable) and median time to first reply. If the refund rate for one product runs well above the rest, it is a product problem, not a policy one. Fix the listing, drop the product or change the supplier. If claim recovery is low, you are filing late or without the right evidence.

If the number of reply drafts that need heavy editing stays high, the instruction is missing a rule. Add it, test it on five old tickets and move on. That small loop, written down, is most of what a returns workflow needs.

Questions store owners ask about dropshipping returns

Can I send customers a supplier's address for returns?

Only if the supplier has agreed in writing to accept returns at that address, and the customer can reach it affordably. Many suppliers refuse returns or sit in a warehouse the buyer cannot post to cheaply. If that is your situation, offer a refund without return, a partial refund, or a replacement instead.

Do I get my money back from the supplier when I refund a customer?

Not automatically. It depends on the supplier's own terms: faulty, wrong or damaged goods are often credited when you send photos within a set number of days, while changed-mind returns usually are not. Read those terms before you write your own policy, and record the claim window per supplier.

Should AI send refund replies without my approval?

No. Let AI draft the wording and sort the case type, but approve every refund or return decision yourself, at least until the drafts have matched your decisions on a few dozen tickets in a row. Money leaves your account on a refund, and a wrong promise is hard to take back.

Is a refund-only rule legal?

A rule that you refund without collecting the goods is a business choice and usually generous to the buyer. What you must not do is remove rights buyers have by law, such as the right to a remedy for faulty goods. Have a qualified adviser read your policy for the places you sell to.

Further reads

• How to Automate Returns and Refunds With Clear AI Rules — Turn the refund-only limit into written rules AI can follow.
• Ecommerce AI Chatbot Examples: 7 Store Conversations to Copy — Seven store conversations you can adapt, including returns.
• AI Size Recommendation for a Clothing Brand From Charts and Returns — Cut size-related returns at the source with fit data.
• Best AI Tools for a Small Ecommerce Store: 7 Worth Paying For — Which paid AI tools a small store actually uses.
• AI Fit Shoes Plugin: Can a Size Finder Cut Returns for a Shoe Shop? — How shoe size finders work, what data they need, and a before-and-after method to test whether one cuts your returns before you pay.
• Clothing Return Policy Template: Write One With AI and Check It — A decision sheet, an AI drafting prompt that audits itself, fourteen legal checks and twelve test scenarios for a clothing shop's return policy.
• Abandoned Cart Recovery in WooCommerce: Plugin Setup and AI Copy — Install a free cart recovery plugin, set consent and timing, have AI draft three emails, and measure what the sequence really recovers.
• Candle Troubleshooting Replies: Tunnelling, Sooting, Weak Scent — Cause lists, care wording, replacement rules and reply templates for tunnelling, sooting and weak scent, drafted with AI.
• Chargeback Response Template for Online Stores, Drafted With AI — Reason-code mapping, an evidence checklist and a response template you can fill with AI, plus the rule that nothing gets invented.
• Dropshipping Product Pages: Rewrite Supplier Copy With AI — Turn copied supplier descriptions into unique, accurate dropshipping product pages, with prompts, a spec check and a duplicate test.
• Dropshipping Product Photos: Replace Supplier Images Safely — Replace borrowed supplier images with AI-assisted product photos without misleading buyers, breaching image rights or inflating returns.
• Dropshipping Profit Margin: A Spreadsheet AI Can Audit — One product, one spreadsheet: contribution margin per order after ads, fees, refunds and chargebacks, break-even ROAS and an AI audit of the formulas.
• Ecommerce Store Audit Checklist: Run It With ChatGPT or Claude — A page-by-page store audit you can run in an afternoon: what to screenshot, what to export, how to rank the fixes and what AI cannot see.
• Free Shipping Threshold: Set It From Your Average Order Value — A worked order-export example: find your average order value, price the shipping you give away, and test two thresholds with ChatGPT or Claude.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Stripe refund documentation (docs.stripe.com) and OpenAI's custom GPT retirement FAQ, read 5 November 2026. Supplier terms, prices and figures in the worked examples are illustrative; check your own suppliers' published terms.