Refund Policy Language That Reduces “Product Not As Described” Disputes (UK-Ready)

If you’re building a startup, it’s easy to think VCs only care about your pitch deck. Then a handful of “product not as described” disputes hit. Suddenly you’re spending evenings hunting screenshots instead of shipping product.

I’ve seen founders lose deals over simple signals. Slow refunds, messy wording, and angry emails look like weak operations. Investors read that as risk, even if your product’s solid.

Your refund policy language is one of those quiet signals. It tells customers what happens when things go wrong. It also tells investors if you run the business on process, not hope.

Why “Not As Described” Disputes Happen

“Not as described” disputes happen when a customer expected one thing and got another. The gap is often tiny. A missing cable. The wrong colour variant. A size that feels off.

Banks don’t read your intentions. They read the customer’s story and the evidence. If your wording sounds fuzzy, the bank fills in the blanks.

A good policy does two jobs at once. It sets clear expectations before purchase. And it gives a fast, fair route to fix issues after purchase.

Here’s the pattern I see most.

The 5 Biggest PNAD Triggers

Variants and options cause trouble when the product page shows one thing and checkout sends another.

Specifications cause trouble when key facts aren’t easy to find.

“What’s included” causes trouble when accessories feel assumed.

Condition causes trouble when “refurbished” reads like “new”.

Misleading “final sale” language causes trouble because it pushes customers toward their bank instead of your support team.

The Difference Between “Faulty” and “Not As Described”

In UK guidance, you must offer a full refund when an item is faulty, not as described, or doesn’t do what it’s supposed to do.

That’s why wording matters. If you write as if refunds are optional, you create friction. Friction turns into complaints. Complaints turn into disputes.

You can still run a firm policy for change-of-mind returns. But you can’t remove statutory rights with a sign, a clause, or a “final sale” label.

UK Rules You Can’t Write Around

UK law sets the floor. Your policy can be more generous. It can’t be tighter in a way that misleads people about their rights.

GOV.UK is blunt about it. It’s illegal to restrict or take away customers’ rights or to mislead them about their rights, like putting up “no refunds” signs.

That’s the first investor point too. If your policy looks like a rights trap, it’s a brand and compliance risk.

You also need the basics in your head.

The Consumer Rights Act 2015 backs the “as described” promise and includes a short-term right to reject with a 30-day time limit in many cases.

The Consumer Contracts Regulations 2013 cover distance selling and the cooling-off period for many online orders.

Online Orders: The 14-Day Cancellation Timeline (14 + 14 + 14)

GOV.UK sets out a simple flow for most distance selling. The customer has 14 days after receiving the item to cancel. They then have another 14 days to return it. You must refund within 14 days of getting the item back.

The Consumer Contracts Regulations also set refund timing rules and allow a refund when the goods are returned or when the customer shows evidence they sent them back.

This is where founders slip. They write “14 days returns” and think they’re safe. But the legal flow is about cancellation notice, return, and refund timing.

Why “No Refunds Under Any Circumstances” Backfires

It backfires in two ways.

First, it’s a legal and Trading Standards risk when it suggests rights don’t exist.

Second, it’s a dispute magnet. eBay’s own rights guidance calls out “No refunds” style restrictive statements and says goods should be as described, with automatic statutory rights.

There’s a third issue founders miss. Some Trading Standards guidance warns that slapping “your statutory rights remain unaffected” next to a restrictive line can still mislead when the message conflicts.

So the fix isn’t “add one sentence.” The fix is clear, non-contradictory wording.

Refund Policy Essentials: The Checklist

If your policy dodges key details, customers assume the worst. That’s when they screenshot your page and go to their bank.

Ambiguous policies invite disputes, and clear policies set expectations.

At minimum, your refund policy language should cover:

Time limit and returns window.

Return eligibility and item condition requirements.

Refund method and refund timeline.

Process steps and who pays shipping.

Exceptions, including sale items and final sale rules.

Exchanges, replacements, and store credit options.

Where the Policy Must Appear

Policy visibility is not a “nice to have.” It’s part of dispute prevention.

The key places are the product page near the buy button, checkout before payment, confirmation email after purchase, a searchable help centre, and account settings for subscriptions.

Founders should care for the same reason VCs care. If terms only show up after purchase, it looks like a trap.

Copy-and-Paste Language That Reduces PNAD Disputes

Customers don’t need poetry. They need clear outcomes.

“Full refund within 30 days” is clear, while “refunds may be available at our discretion” invites arguments.

Below are clauses I’ve seen cut PNAD disputes because they remove guesswork. Each one is written in plain English, with measurable steps.

Wrong Item or Missing Parts Clause

Good:

“If you received the wrong item or anything is missing, contact us within 7 days of delivery. Send a photo of the item and packaging. I’ll arrange a replacement or a full refund, and I’ll cover the return shipping.”

Risky:

“Contact us if there’s an issue and we’ll see what we can do.”

Why it works: it sets a time limit, asks for practical proof, and offers clear resolution options.

“Not As Described” Clause (Specs, Variants, and What’s Included)

Good:

“If the item isn’t as described, I’ll fix it fast. This includes mismatched specifications, wrong variant, missing accessories listed on the product page, or condition that doesn’t match the listing. Contact us within 30 days and include photos. I’ll offer a replacement or refund.”

Risky:

“Not as described claims may be rejected if the item differs slightly.”

Why it works: it defines “not as described” in the way customers actually experience it. It also forces you to keep product descriptions accurate.

Damage in Transit Clause

Good:

“If your order arrives damaged, contact us within 48 hours of delivery. Send clear photos of the damage, outer box, and label. I’ll offer a replacement or refund. Keep the packaging until I confirm the next step.”

Risky:

“Damage must be reported immediately or you lose your right.”

Why it works: it’s strict but realistic. It also builds evidence for carriers and card disputes.

Change of Mind Clause (Separate From Statutory Rights)

Good:

“Change-of-mind returns are accepted within 30 days of delivery if the item is unused and in original packaging. You can choose an exchange, store credit, or a refund. Return shipping is paid by the customer unless the item is faulty or not as described.”

Risky:

“No refunds for change of mind.”

Why it works: it’s clear, and it doesn’t look like you’re blocking rights. You can set stricter or more generous rules for change of mind, but you can’t reduce statutory rights for faulty goods or items not as described.

Sale Items and “Final Sale” Clause (Without Misleading Customers)

Customers have the same rights in a sale as at full price when goods are faulty or not as described.

Good:

“Sale items follow the same statutory rights as full-price items. For change of mind, sale items can be returned within 14 days of delivery unless marked ‘final sale’ on the product page and at checkout. Final sale does not apply to faulty goods or items not as described.”

Risky:

“No refunds on sale items.”

Why it works: it stops the classic “sale items are excluded” fight. It also reduces “restrictive statement” risk.

Language to Avoid (High Dispute-Risk)

Avoid lines that sound like a shrug.

“Refunds may be available.”

“Subject to our discretion.”

“Under any circumstances.”

Vague wording invites disputes because it creates room for argument.

Product Page Consistency: The Hidden Driver of PNAD

Your policy can’t rescue a vague listing.

Most “not as described” complaints start on the product page, not in the policy. The policy only decides whether the customer argues with you or goes straight to their bank.

Here’s what must be clear on listings if you want fewer disputes.

Specifications that matter, not filler. What’s included, in plain words. Condition, with grading for refurbished or used items. Sizing with measurements, not just “small” or “large.” Colour notes that admit screen variance without sounding slippery. Compatibility details for parts, accessories, and devices. Variants and options tied to model numbers, SKU, or clear labels.

“As Described” Checklist for Listings

Keep this simple and repeatable.

Put key specifications above the fold. Show variant photos that match the selected option. List what’s included in the box. Use model numbers and SKU where it helps buyers choose. If measurements are approximate, say “approx” next to the number, not hidden at the bottom. If the item is refurbished, state the grade and what that means. If batch or material variation can happen, name it and show a real example photo.

This is not about perfection. It’s about stopping surprise.

Handling Colour and Sizing Variation Without Misleading Customers

Say what’s true, but don’t use it as a shield.

Good:

“Colours can look slightly different on screens. I list the material, finish, and shade name, and I show photos in normal indoor light. If the item you receive doesn’t match the selected variant on your order confirmation, I’ll treat it as ‘not as described’.”

That last sentence matters. It keeps trust.

Returns Process That Deflects Disputes

Investors look for repeatable systems. Your returns process is one of the easiest systems to show.

Customers can use items the way they would in a shop during the cooling-off period, and you can ask for proof of purchase like a bank statement or packaging.

Fast response matters because customers calling their bank is faster than waiting for email replies.

Here’s the workflow I suggest for PNAD issues.

Reply fast. Ask for the right proof once. Offer a clear outcome. Confirm the timeline in writing. Close the loop with a refund or replacement confirmation.

Support Scripts for PNAD Complaints

Keep it calm and direct.

Script 1: Not as described

“Thanks for flagging this. I can see your order for [product] on 2026. If the item doesn’t match the listing or the variant selected, I can offer a replacement or refund. Please send 2 photos showing the item and label, and tell me what looks different. I’ll confirm the next step today.”

Script 2: Wrong item

“You’re right to raise this. Please send a photo of what arrived and the shipping label. I’ll ship the correct item or issue a refund. I’ll also tell you if I need the wrong item returned.”

Script 3: Damaged in transit

“I’m sorry it arrived like that. Please send photos of the damage, the outer box, and the label. I’ll offer a replacement or refund. Please keep the packaging until I confirm the return step.”

These scripts work because they’re action-focused. They also create a clean paper trail.

Refund Speed Targets and What Customers Should Expect

Slow refunds create disputes.

UK law sets clear legal refund timing for distance selling cancellations, including refunding standard delivery cost in many cases. The Consumer Rights Act also sets refund timing rules in some cases, including refund within 14 days of agreeing a refund, and paying back using the same means of payment unless the customer agrees otherwise.

So set a public target that’s realistic.

Example:

“Refunds are processed within 2 business days after approval. Your bank may take extra time to show it on your statement.”

That one line cuts repeat emails. Also worth noting: if a customer asks for money back before a transaction settles, voiding can be cleaner than refunding.

Abuse Prevention Without Sounding Hostile

Return abuse is real. But harsh wording can raise disputes and scare honest buyers.

Use neutral inspection language.

Good:

“I check returns on arrival. If the item shows use beyond what’s needed to check it, I may reduce the refund to reflect loss in value, where the law allows. I’ll explain the reason in writing and share photos.

This mirrors the idea in the Consumer Contracts framework that deductions can apply for unnecessary handling in some cases.

Also keep your proof rules fair. Proof of purchase can be more than a receipt, like a bank statement or packaging. That single line lowers friction and keeps customers from feeling trapped.

FAQs

Can I say “no refunds” in the UK?

In the UK, blanket “no refunds” wording can mislead customers about statutory rights. If goods are faulty or not as described, you must offer a remedy, including refunds in many cases. Official UK guidance also warns it’s illegal to restrict or mislead customers about these rights.

If you want to refuse change-of-mind returns in-store, say that clearly. Don’t use a blanket line that reads like “no refunds ever.”

What wording should I use instead of “no refunds”?

Use plain language that separates change-of-mind rules from statutory rights. A common safe line is “This does not affect your statutory rights,” paired with specific return rules like time limits, condition requirements, and refund methods. Avoid pairing that line with restrictive statements that contradict it.

A better approach is to write: “Change-of-mind returns: [your rules]. Faulty or not as described: your statutory rights apply.” Then keep the rest concrete.

What counts as “not as described”?

“Not as described” usually means the item doesn’t match the description, photos, specifications, selected variant, or stated condition. UK guidance treats “not as described” as a valid reason for remedies, including refunds in many cases. That’s why product descriptions, images, and “what’s included” lists must match reality.

If a customer selected “Blue, 128GB” and you sent “Black, 64GB,” that’s not a preference issue. That’s a mismatch.

Do customers need a receipt for a refund?

A receipt can help, but it’s not the only option. UK guidance says you can ask for proof of purchase, and it can include other evidence such as a bank statement or packaging. Clear policy language should explain acceptable proof so customers don’t feel blocked at the first step.

Write what you’ll accept. That one change cuts angry emails.

What’s the UK online cancellation timeline?

For many online, mail, or phone orders, customers can cancel within 14 days of receiving the goods. After they tell you, they usually get another 14 days to return the goods. You must then refund within 14 days of receiving the goods back, and standard delivery costs often apply.

If you fail to give required cancellation info, the Consumer Contracts rules can extend the cancellation window.

Where should the policy appear to cut disputes?

Place the key refund and returns terms where customers make decisions. Best practice is the product page near the buy button, the checkout before payment, and the order confirmation email after purchase. A searchable help centre also reduces repeat contacts and bank disputes.

This is also a founder habit worth showing investors. It signals clean operations.