A refund policy is part of what people buy, even if they never use it. Here is how to write a short, fair one in fifteen minutes, and where AI helps.

A good refund policy for a small business is short, specific, and written for the customer on her worst day. It says what happens when something is not a fit, how to ask, and how fast you will answer. Write it before you need it, because the way you handle an ending is something customers remember longer than the sale.
Most of us design the happy path in loving detail. The sales page gets four drafts. The welcome email gets a gif debate. The refund policy gets copied from somewhere at midnight and pasted into a footer nobody reads, including you.
Then someone asks for her money back, and suddenly you are making it up in real time, a little defensive, typing and deleting in the school pickup line.
Because that is the moment the customer is paying the closest attention.
When things go well, she barely notices your systems. The download arrives, the session happens, the candle smells like the candle. When things go sideways, she notices everything: how long you took to reply, whether she had to explain herself twice, whether your tone changed once money was on the line.
A customer who asks for a refund and gets a fast, warm, clear answer often comes back. A customer who gets a vague policy and a three-day silence tells her friends, and she tells them in detail.
I'd go further: a clean exit is part of what people are buying, even when they never use it. Knowing there is a fair way out is what makes it easier to say yes in the first place.
Manufacturers have a name for this problem: reverse logistics. It is the planned route for everything that travels backward, the returns, the repairs, the products at the end of their life. For a long time it was treated as an annoying cost center. The companies that got serious about it learned that designing the way back changes how you design the way forward. If you know something might come back, you build it, track it, and explain it differently from the start.
You are not shipping refrigerators. But the principle shrinks down nicely. Every offer has a way back, whether you designed one or not:
None of that is administrative debris. It is part of the offer.
Keep it to what a frustrated person needs to know in thirty seconds:
Then check it against the rules you already live under. Marketplaces like Etsy, platforms like Shopify, and your payment processor each have their own refund and dispute settings, and consumer protection rules vary by where your customers live. Your policy has to sit inside those, not fight them. If you sell something higher stakes, a quick review from someone who knows the rules where you operate is money well spent.
Here is the test I like. Read your policy as the most tired version of your customer. She is annoyed, she is on her phone, and she has a toddler hanging off one arm. Does she know exactly what to do next? Does anything make her feel accused?
Watch for these:
A fair policy can still protect your time. "Refunds within seven days if you have not opened the second module" is fair. "All sales final, no exceptions, do not email us" is a sign on a door that says you are not sure you are worth trusting.
If you want help deciding what you are actually promising, my piece on making your operations match your promise is the natural next read. And if refund requests keep showing up because the work keeps growing, that is a scope problem wearing a refund costume; handling scope creep covers that one.
AI is good at the writing part of this, and it saves you from the midnight copy-paste.
Give it the backstory: what you sell, who buys it, what has gone wrong before, and the tone you want. Then ask it to:
What stays yours is everything that involves judgment. The rule itself. The exceptions you are willing to make. The moment a refund request is really a person having a hard time, and the right answer is a human reply, not a template. Automation is fine for the receipt. It is not fine for the customer who writes, "I'm so embarrassed to ask this."
Also, read every AI draft against your actual settings before you post it. A beautiful policy that promises something your checkout cannot do is worse than an ugly accurate one.
Set a timer and do this today:
That is it. You are not drafting terms of service for an airline. You are deciding, ahead of time, how you want people to feel when it is not a fit.
Endings shape trust. Most small businesses get exactly one chance to handle a disappointed customer well, and the ones who plan for it look calm when it happens. It is a small piece of building a brand people care about, and it is one of the few you can finish before lunch.
Yes, even if the answer is "no refunds." A written policy sets expectations before anyone pays, gives you a calm script when someone asks, and helps if a payment dispute ever comes up. Post it where customers can see it before they buy.
Cover who and what it applies to, how long someone has to ask, what they get (refund, credit, swap, or redo), how to ask, and how fast you will reply. Keep it short enough to read on a phone in thirty seconds.
It can be, especially for custom work or digital files that cannot be returned, as long as it is clear before purchase and allowed by your platform and local rules. Pair it with something you can offer, like a fix, a redo, or a credit, so it does not read as a closed door.
Reply quickly, thank her for telling you, and offer the clearest option you have. Ask one question about what went wrong so you can fix the cause, not just the transaction. A fast, warm answer often earns a second purchase.
AI can draft it and make it clearer, but you decide the actual rules and exceptions. Give it what you sell and what has gone wrong before, then check every line against your checkout and platform settings before you publish.
Learn AI with Belles
Start with the library, then keep building with new trainings, templates and tools, plus a monthly build and Q+A with Lily.
Keep reading
All articles