How to Handle a Refund Request Without Losing Money

When a customer asks for a full refund after you have done most of the work, you usually don't owe them all of it back. A fair refund is what they paid, minus the value you have already delivered. That covers materials you bought for their job, money you paid out to subcontractors, and the hours you put in at your agreed rate. If the work was done properly and the scope was agreed, that is the number. Your reply should be short and calm. It should state the policy, offer one specific thing, and give a date.

The rest of this article covers how to work that number out, what to say for each kind of refund request, when to just pay up and move on, and how to set things up so the next request takes ten minutes instead of a ruined weekend.

The short answer: what you actually owe

Three things decide your obligation, in this order:

1. The law where you operate. Some sales come with a legal right to cancel. You can't sign that away (more on this below).
2. What the customer agreed to. Your contract, quote, invoice terms or checkout page.
3. Whether you delivered what you promised. If the work is defective or incomplete, they may have a fair claim whatever your policy says.

If the law gives them no special right, your terms are clear, and the work matches the scope, then you owe them the unearned part of what they paid. Nothing more. If one of those three is missing, especially written terms, your position is weaker. You will probably end up settling somewhere in the middle.

This is general information, not legal advice. If a single refund is worth more than a few thousand dollars, pay for an hour with a local attorney before you reply.

Sort the request before you reply

Most refund requests fall into one of three types. Each one needs a different first response. Work out which type you have before you write a word.

The point of sorting first is that you stop making the decision while you're angry. "Unhappy with the result" is the only type where you may be at fault. It is also the only type where the right first move is to offer more work, not less money.

The math: what you have earned versus what they paid

Here is a hypothetical. A cabinet painter quotes a kitchen at $4,000. That is $1,000 for materials and setup, plus $3,000 of labor estimated at 40 hours, which works out to $75 an hour. The customer paid a $1,000 deposit and a $1,000 progress payment. With 28 hours done, they ask for a full refund.

In this case the customer owes the painter $1,000, not the other way round. If they changed their mind, the honest answer is "no refund is due". You might still decide to waive the $1,000 balance to close the job cleanly.

If they are unhappy with the result, the numbers stay the same, but your first move changes. Offer to fix the specific doors they don't like before anyone talks about money.

Run the same calculation whenever someone asks. Most owners never do. They assume the customer's number is the starting point. It isn't. Your number is the starting point.

When hours are hard to count

If you price by project rather than by hour, use milestones instead: design approved, materials ordered, first fitting done. Then give each milestone a percentage of the total in your contract. "Materials ordered = 30% earned" is far easier to defend than a rough guess at hours after the fact.

Decide what is non-refundable before the job starts

"Certain costs are non-refundable" protects you from almost nothing. A customer can't argue with a line they never saw, and a card network won't accept one either. Put a real figure next to each item, in writing, before work begins.

Tie the deposit to something real. A deposit that covers materials actually ordered is easy to defend. A "non-refundable" deposit on a job you never started and spent nothing on is not. That is especially true if a customer disputes it with their card issuer. Whether and how much to charge as a deposit is worth deciding before you write the rest of the policy.

Pick one refund window and say what starts the clock

A refund window answers the question "how long can they come back?" Without one, a customer can ask for money back six months later, and you have nothing written to point to.

Pick one length:

• 7 days suits digital products, one-off sessions, and anything used up quickly.
• 14 days suits most service work. It's long enough to spot a real problem and short enough to close the job.
• 30 days suits physical products and work where problems take time to show up.

Then name the start of the clock. Pick one, and only one:

• the date of final delivery
• the date of the last service visit
• the invoice date

Write it as a single sentence: "Refund requests must be made within 14 days of final delivery." That sentence goes into your contract, invoice and website, word for word.

Set your no-argument ceiling

Some refunds are not worth having a view on. If a customer asks for $60 back on a $400 job, an hour of your time spent arguing costs more than the $60. That is before the one-star review.

Pick a dollar amount you will refund immediately, with no questions and no investigation. In our experience, a workable starting point is roughly one hour of your billed rate, or about 5–10% of your average job value, whichever is lower. Here are some examples:

Write the number on a sticky note. When a request comes in under it, refund it the same day and politely ask what went wrong. You'll learn more from the answer than you'll lose on the refund.

Above the ceiling, you work out the number and make a first offer.

Choose your default first offer

Once a request is over your ceiling, your opening offer should be one of these three. Decide in advance which one you lead with for each request type.

A sensible default is:

• Unhappy with the result: redo first, partial cash only if the redo fails or they refuse it.
• Changed their mind: refund the unearned portion only. Offer a credit if you want the relationship.
• Job stopped halfway: final statement showing earned versus paid, with any balance refunded or invoiced.

A redo nearly always costs you less than cash. Your labor costs you less than the price you charge for it. A redo also lets you finish with a customer who is satisfied rather than one who is still angry.

The four-sentence reply

Everything above leads to one message. Keep it to four sentences:

1. Acknowledge the request without agreeing or arguing.
2. State the policy they already agreed to.
3. Name the one thing you will do.
4. Give a date.

Here is an example for a customer who changed their mind:

Thanks for letting me know you'd like to stop the project. Under the agreement we signed on March 3, materials and completed work are billed and the remaining balance is refundable. I've attached a statement showing $2,100 of completed work and $900 of materials against the $2,000 you've paid, so no refund is due and I'm happy to waive the $1,000 difference. I'll drop off the remaining materials by Friday, March 21.

And for an unhappy customer:

I'm sorry the finish on the upper doors isn't what you expected. Our agreement covers corrections to work that doesn't match the approved sample. I'd like to come back and redo the four doors you photographed, at no charge. I can be there Tuesday, March 18, at 9am.

Don't write a paragraph about how hard you worked or what the materials cost. Long replies read as defensive and invite a long reply back.

Save your versions where you can paste them from your phone in under a minute. If you want the full set worked out for you, The Refund Policy Playbook has fill-in reply templates for all three request types. It also has a decision tree that takes you from "they asked for a refund" to the exact offer and wording, plus policy wording you can drop straight into a contract.

When they threaten a chargeback

A chargeback, or card dispute, is when the customer asks their card issuer to reverse the payment instead of asking you. Here's what happens next:

• The money is usually pulled from your account straight away and held while the dispute is decided.
• Your processor charges a dispute fee. At the larger processors it's often around $15 per dispute, though some charge nothing and rules on returning the fee vary. Check your processor's dispute page for the current figure.
• You get a fixed number of days to submit evidence. Miss the deadline and you lose by default.
• Cardholders commonly have up to 120 days from the transaction to dispute. Sometimes it's longer for services delivered after the payment date.
• Many processors, including Stripe, keep the original processing fee even when you refund voluntarily. Refunding early doesn't fully reverse the cost, but it avoids the dispute fee.

Decide your dispute line in advance:

• Below the line: refund it. The fee, your time and the hold on the money aren't worth it.
• Above the line: submit evidence, if you have a signed scope and proof of delivery.

A common choice is to set the dispute line somewhat above your no-argument ceiling, often in the $150–$500 range for small service businesses. Too many disputes can also put your merchant account at risk with some processors. That's another reason to settle the small ones quickly.

If a customer says "I'll just dispute it", don't take the bait. Reply with the same four sentences. Then make sure your evidence folder is ready.

Build the evidence folder before you need it

If you win a dispute, it will be because of your documents. If you lose one, it will usually be because you didn't have them. Keep a file for every job, from day one:

• Signed scope or quote, with the price and refund terms visible
• Dated change approvals, even when they're just a text saying "yes, go ahead"
• Before and after photos, with dates
• Delivery confirmations or a signed completion note
• The full text and email thread with the customer
• Receipts for materials bought for this job

Pick one place everything lives, such as a folder per job in Google Drive, or the job record in Jobber, Housecall Pro or whatever field-service tool you use. Use the same structure every time. The test is whether you can pull a complete job file in ten minutes.

Change approvals matter more than most owners realize. Many "unhappy with the result" requests are really about work the customer asked for verbally and then forgot. Getting changes approved in writing heads off a lot of refund requests before they start.

Check the rules you don't control

Your policy can't override the law, and it can't override the terms of a platform you sell through. Check these before you publish anything:

• The FTC Cooling-Off Rule. For many sales made at the buyer's home or at a temporary location, such as a trade show or a hotel room, the buyer has three business days to cancel for a full refund. There are dollar thresholds and exemptions. Home-service businesses that sign contracts at the kitchen table should read the FTC's guidance directly.
• Your state's consumer rules. Many states have their own rules on home improvement contracts, deposits, cancellation rights and how refund policies have to be shown. Search your state attorney general's consumer protection pages for your trade.
• Platform and marketplace terms. If you sell through Etsy, Amazon, Thumbtack, Upwork or similar, their refund and dispute rules may apply on top of yours. Sometimes theirs win.
• Your processor's rules. Stripe, Square and PayPal each publish how they handle refunds, disputes and fees. Read the current version.

If any of these give the customer more than your policy does, the law or platform rule wins. Write your policy to match it.

Put the policy in three places and track every refund

A refund policy the customer never saw is worth very little. Put the identical wording in three places:

1. Your contract or quote, which the customer signs or accepts. What else belongs in a service contract covers the rest.
2. Your invoice or checkout page, next to the price.
3. Your website, on a page you can link to.

Identical means word for word. If your website says 30 days and your contract says 14, a customer will quote whichever suits them, and a card issuer may side with them.

Then log every refund for 90 days, with a reason code: unhappy result, changed mind, stopped halfway, or other. A spreadsheet with five columns is plenty: date, customer, job value, refund amount, and reason. Review it monthly. Patterns tell you what to fix:

Record refunds properly in your books too, not as a mystery deduction. Simple bookkeeping from day one shows how to keep that clean for tax time.

If you'd rather not build all of this from a blank page, The Refund Policy Playbook walks through each step with templates. It includes the policy wording, the evidence folder checklist, and recovery paths for when a request has already turned into a review, a dispute or a demand letter.

The short version

• You usually owe back what they paid minus the value delivered, meaning materials, subcontractors and completed work. Not the full amount.
• Sort the request first: unhappy with the result, changed their mind, or job stopped halfway. Only the first one might be your fault, and its first response is a fix, not cash.
• Set a no-argument ceiling and refund anything under it the same day. Above it, lead with a redo or credit before cash.
• Reply in four sentences: acknowledge, state the policy, name one action, give a date.
• Keep an evidence folder for every job, and decide your chargeback line before you need it.
• Put identical wording in your contract, invoice and website. Check federal, state and platform rules, and review your refund log monthly.