Refund policy for small business: write one that holds

A refund policy for small business has one job that outranks all the others. When somebody asks for their money back, you already know what you're going to say, and they already know what to expect. Most of the templates you'll find online are written for shops that ship boxes back and forth. This one covers services and subscriptions too, and it spends most of its time on the part almost nobody writes about, which is what you do once the request is sitting in your inbox.

What a refund policy for small business really has to do

Three jobs, roughly in the order they come up.

• It calms people down before they buy. A stranger handing you money online wants to know what happens if this goes wrong. A plain refund policy on the product page removes the last reason to close the tab.
• It tells whoever answers the email what to say. If that person is you at 10pm, it stops you inventing a new rule every time. If it's a part-timer, it's the difference between a two minute reply and a phone call to you.
• It gives you something to point at. "Our refund policy is 30 days" ends a conversation that "well, normally, I'd say" keeps going for another twenty minutes.

Two of those three jobs are about your side of the counter. A refund policy written only for the customer is half a refund policy, and it's the half that leaves you answering the same question forty times a year.

On the legal side, federal law in the US doesn't force most businesses to offer refunds at all. States are a different story, and several of them care a great deal about whether your policy is posted where a customer can see it before they pay. California gives buyers an automatic 30 day refund right if nothing is posted. There are also narrow federal rules for particular kinds of sale, like the three business day cancellation window that covers a lot of door to door and pop up selling, explained in this federal consumer guidance. Check your own state before you publish, and if the sums involved are large, buy an hour of a lawyer's time.

Six decisions that make the refund policy

Writing it up is the easy bit. Deciding what it says is the work. Get these six settled and the wording takes fifteen minutes.

1. How long the window is. Fourteen, thirty and sixty days are the common choices. Pick a number you can live with during your worst week of the year, not your best one. A longer window sells more and costs more, and both of those effects are real.
2. What you hand back. Cash to the original card, store credit, an exchange, or a partial refund. You can mix them by situation, but write down which is which. Store credit keeps the money in the business and annoys a certain kind of customer enough that they'll say so in public.
3. What's excluded. Custom work, perishables, sale items, digital files already downloaded, services already performed. Say it in words a tired person understands. "Custom orders are final" beats "bespoke fabrications are non-returnable."
4. Who pays to send it back. If the item arrived broken or you shipped the wrong thing, you pay. Beyond that it's your call, and it's the single biggest cost lever in the whole refund policy. Restocking fees exist, they're legal in most places, and they make people furious when they arrive as a surprise. If you charge one, put the percentage in writing.
5. How fast the money moves. Give a number in business days and pad it. Customers forgive a refund that lands early far more readily than one that lands two days after you promised.
6. Who is allowed to say yes without asking you. Almost nobody writes this one down, and it decides how fast your customers get answers. Give whoever handles the inbox a dollar figure they can approve on the spot. Under $50, refund it and move on. Above that, check with you. A number like that does more for your response time than a week of training.

That last decision is the one that separates a refund policy that works from a document nobody uses. A rule your team isn't allowed to apply is just a longer route back to your phone.

Refund policy wording you can copy and adjust

Two versions, because a refund policy for a physical product and one for a service are different animals. Swap the numbers for your own and keep the plain language.

If you sell things:

We want you happy with what you bought. Return anything unused and in its original packaging within 30 days of delivery and we'll refund you in full, back to the card you paid with. Refunds go out within 5 business days of the item reaching us. If it arrived damaged or we sent the wrong thing, we cover the return postage. Otherwise the postage is yours. Custom orders and clearance items are final sale. To start a return, email us with your order number and we'll send instructions the same day.

If you sell services or a subscription:

Cancel within your first 14 days and we'll refund the whole amount, no questions. After that, we refund the unused part of the month you're in and stop billing straight away. Work that's already been delivered and signed off isn't refundable. Email us and we'll take care of it the same day.

Both are short on purpose. Every extra clause in a refund policy is another sentence somebody can read differently from how you meant it, usually at the worst possible moment.

Where to put your refund policy so people find it

A refund policy nobody can find is one you'll be retyping from memory forever. Five places, and the last one matters more than it sounds.

• The product or checkout page, in one line, with a link to the full version.
• The order confirmation email, where people go looking a week later.
• The receipt, printed or emailed.
• Your website footer, so it sits on every page.
• An article in your help center, written as an answer to the question people actually type, which is usually "how do I get a refund" rather than "refund policy."

That last one changes the economics. If the policy lives in a document on your desktop, every request becomes a conversation. If it lives in a published article, a good share of requests answer themselves before they ever reach you. Our guide to help center software covers how to get one up without a developer.

It also gives your chat assistant something honest to work with. In SupportifyGPT, hand written rules do the finding, matching what somebody typed against the articles you've published, and then a model writes the reply in sentences instead of handing over a list of links. It can only use what you wrote down. If your refund window isn't in an article anywhere, it says it doesn't know and passes the question to you, which is what you want from anything handling money questions at 2am. Anything new it drafts for your knowledge base waits for your approval before it goes live.

How to answer a refund request without a fight

The refund policy sets the rule. The reply decides whether the customer comes back. Four things, every time.

1. Answer fast. Same day beats a well crafted paragraph two days later. People escalate because of silence far more often than because of the answer.
2. Give the verdict in the first line. Yes or no, up front. Burying it under three sentences of throat clearing reads like bad news being smuggled in.
3. Give the reason once. One sentence. Repeating it three different ways sounds like you're arguing with yourself.
4. Say what happens next, with a date. "The $84 is back on your card by Friday" closes the ticket. "We'll process this shortly" starts a second one.

Our piece on handling customer complaints goes deeper on tone, and the same four rules apply when the answer is no.

Run the arithmetic before you dig in

Saying no to a small refund feels like defending the business. It often costs more than saying yes. Most card processors charge you a fee on every dispute a customer files, commonly somewhere between $15 and $25, and several of them keep that fee whether you win the dispute or lose it. The range is wide, so look up your own processor's schedule rather than trusting a figure in an article, this one included. Verified September 2026.

Add your own hour of paperwork, the fair chance you lose the goods anyway, and the review that tends to follow. A $40 refund you fought over can easily cost more than the $40 you held onto. If one does turn into a public complaint, our guide to responding to negative reviews is the next thing to read.

None of which means hand everyone their money back on demand. It means the cheap fight and the expensive one look identical at the moment you're choosing, and the arithmetic is the only way to tell them apart.

Four mistakes that make a refund policy useless

A refund policy for small business tends to fail in a small number of predictable ways. These four account for most of it.

• Writing it in legal language. If a customer can't tell from your policy whether they're getting their money back, they'll email to ask, and you've bought yourself the conversation the policy was meant to prevent. Read it out loud. If you'd never say it out loud, rewrite it.
• Publishing it once and never touching it. Products change, shipping costs change, the mix of requests changes. A refund policy written for the business you had three years ago quietly stops matching the one you run now.
• Different answers for different people. Customers compare notes, especially in the same town or the same online group. Two people who asked the same question and got two different answers is how a routine refund becomes a public argument about fairness.
• No time limit on goodwill. "We'll make an exception this once" without a date attached becomes the new normal for that customer. If you bend the refund policy, say plainly that it's a one time thing, and log it.

Keep a short exceptions log

Every policy gets bent. A long standing customer, a genuine mix up, a week where you'd rather refund than argue. Fine. Write each one down in a single line: the date, who it was, what you did, and why.

Two useful things follow. Your answers stay consistent, because next time somebody asks for the same favour you can see what you did last time instead of guessing. And after a few months the log starts telling you what to change.

If the same exception turns up four times, it has stopped being an exception. Put it in the refund policy and stop making that decision by hand.

That's the whole job. Six decisions, a short page in plain words, five places to publish it, and a log of the times you bent it. A refund policy for small business is worth about an hour of your time, once, and it pays that back the first busy week you have. More practical pieces like this one are in the SupportifyGPT blog, and if you want somewhere to publish the policy where customers and your chat assistant can both reach it, you can start a free 14 day trial. Every feature is on every plan, including the $15 one.