top of page

How Founders Write a Simple Refund Policy

19 hours ago
3 min read

Few early stage founders think about refunds until the first request arrives. Then the questions pile up. Should you say yes? How much should you return? What did you promise on the website?


A simple, written refund policy answers those questions before they are asked. It protects your cash flow, reduces arguments and shows customers that you stand behind what you sell. It does not need to be long. It needs to be clear.


Why a refund policy matters early


A refund policy is a promise. When it is clear, customers feel safer buying from a young company they have never heard of. That confidence can lift conversion rates, especially for a new brand without many reviews.


It also protects you. Without a written policy, every refund becomes a negotiation, and your team ends up making inconsistent decisions. A clear policy gives everyone the same answer and reduces the risk of disputes turning into chargebacks with your payment provider.


Decide what you will offer


Start by choosing the basic terms. These decisions depend on your product, your margins and what customers in your market expect.


The refund window


Pick a clear period, such as fourteen or thirty days from purchase or delivery. Shorter windows suit products that lose value quickly. Longer windows can be a selling point for higher priced items where buyers want reassurance.


The conditions


Explain what qualifies. For physical goods, you might require items to be unused and in their original packaging. For software, you might offer a full refund within a set period of the first payment, with no refunds for partial months after that. Be specific about anything that cannot be refunded, such as custom orders or final sale items.


The form of the refund


Say whether customers receive their money back to the original payment method, store credit, an exchange or a choice. Be clear about who pays for return shipping. Hidden costs are one of the fastest ways to lose goodwill.


Explain the process step by step


A policy is only useful if customers can follow it. Spell out exactly how to ask for a refund: the email address or form to use, the information to include, and whether a receipt or order number is needed.


Then set expectations on timing. Tell customers how quickly you will reply and how long it will take for the money to appear once a refund is approved. Bank processing times vary, so it helps to say that your part happens within a set number of days.


Check the law where you sell


Consumer protection rules differ from place to place, and your policy cannot take away rights customers already have by law. In the European Union and the United Kingdom, for example, many online purchases come with a fourteen day cancellation right. Some US states require businesses to display their refund policy clearly.


If you sell across borders or offer subscriptions, it is worth having a lawyer review your policy. A short consultation now costs far less than a dispute or a regulator's letter later.


Keep the policy short and readable. Use headings, simple sentences and everyday words. Avoid legal jargon unless your lawyer says a specific phrase is needed.


Make the policy easy to find. Link to it in your website footer, at checkout, in order confirmation emails and on your help pages. Customers should never have to hunt for it.


Keep your promise and learn from requests


Once the policy is live, follow it consistently. Train anyone who handles support so they apply the same rules. Where a situation falls outside the policy, decide on a fair approach and note it for the next update.


Track refund requests and the reasons behind them. A rise in returns for one product can reveal a quality problem, a misleading description or a gap in onboarding. Treated this way, refunds become useful customer feedback rather than simply lost revenue.


A simple refund policy is a small document with a big effect. Write it early, keep it fair, and let it work quietly in the background as your company grows.

Comments


Founder Podcast
Featured Founders
bottom of page