Refund & Cancellation Policy: An Ecommerce Launch Signal

If you sell anything online — a product, a digital download, or an app subscription — buyers and regulators expect to find a clear refund, return, or cancellation policy before they pay. A missing or hard-to-find policy is a common source of friction for a launching store: payment processors flag it, marketplaces query it, and consumers who can't see their rights are quicker to file chargebacks. The refund-policy requirement for ecommerce isn't one rule; it's a pattern that recurs across consumer-protection regimes, usually centered on a buyer's right to change their mind and get a refund within a defined window. Surfacing the policy is cheap and removes a recurring source of pre- and post-launch risk.

What LaunchTrust checks

LaunchTrust's refund_policy detector is a presence-only signal with positive polarity — a refund/return/cancellation policy is something you want the scan to find. It inspects the HTML of the page you submit and looks for two kinds of evidence:

1. A policy link. It scans href attributes for URLs referencing refund, return, or cancellation concepts — including non-English forms such as iade / cayma (Turkish), widerruf / rückgabe (German), remboursement / rétractation (French), and devolución / reembolso (Spanish). A footer link like /refund-policy matches here.
2. Policy wording in the page text. If no qualifying link is found, it looks for phrases such as "refund policy," "return policy," "returns and refunds," "right of withdrawal," "right to cancellation," "money-back guarantee," plus localized equivalents like "cayma hakkı," "widerrufsrecht," and "política de devolución."

How to read the result:

• Detected — a refund/return/cancellation link or clear policy wording was found. A matched link reports at info severity; matched body wording at low. Both mean "the signal is present."
• Not detected — neither a qualifying link nor policy wording was found on that page. Reported at medium severity, since consumer and e-commerce rules generally expect such a policy to be reachable.
• Unable to determine — if LaunchTrust can't fetch or read the page (network error, blocked request, empty response), it reports that it couldn't check rather than guessing.

Two limits worth knowing: the scan reads the single page you submit, so a policy that lives only on a separate page won't count unless that page is linked from (or is) the scanned page; and the detector confirms that a policy link or wording exists — it does not read the policy's contents or judge whether the terms meet any specific law.

Why it matters

A reachable refund and cancellation policy maps to expectations across major markets:

• European Union. Under EU consumer-protection law, most distance (online) sales carry a consumer right of withdrawal — commonly a 14-day cooling-off period to cancel and be refunded — and traders must inform buyers of that right before purchase. Some goods and services (custom-made items, or digital content the buyer agreed to start downloading) can be excepted, so treatment depends on what you sell.
• United Kingdom. The UK's distance-selling rules for online consumer contracts likewise center on a cancellation window and a duty to give clear cancellation and refund information up front.
• Türkiye. Turkish distance-selling regulation includes a withdrawal right (cayma hakkı) for online purchases and expects sellers to disclose the conditions, period, and procedure for exercising it.

Beyond statute, payment ecosystems care too: card networks and processors routinely require a visible refund/return policy to reduce disputes, and in-app-purchase platforms set their own refund handling you should reference rather than contradict. A policy that's present and easy to find reduces rejection risk at onboarding and disputes later.

A concrete example

Either a matching footer link or matching body copy flips the signal to detected:

<footer><a href="/refund-policy">Refunds &amp; Returns</a></footer>
<p>Right of withdrawal: cancel within 14 days of delivery for a full refund.</p>

A checkout page that mentions price and "Buy now" but contains no refund link and no policy wording flips it to not detected.

How to address it

1. Write a plain, specific policy. State the cancellation/return window (e.g. a 14-day cooling-off period where it applies), what's refundable, any exceptions (custom goods, started digital downloads), who pays return shipping, and how long refunds take.
2. Make it reachable from the page that sells. Add a clearly labeled footer link — /refund-policy, /returns, or a localized slug — so it's one click from your product, pricing, and checkout pages.
3. Localize for the markets you serve. Selling into the EU, UK, or Türkiye? Present the policy and link label in the relevant language; the detector recognizes localized terms, and so will your customers.
4. Link, don't bury. A distinct, named policy is easier to find than one hidden only inside a long Terms of Service block.
5. Re-scan after publishing. Confirm the live page actually exposes the link or wording, since staging and production footers can differ.

Check this in 30 seconds

Paste your store, pricing, or checkout URL into LaunchTrust's free scanner. It reports whether a refund/return/cancellation link or policy wording was detected, not detected, or unable to determine on that page — alongside related signals like subscription and auto-renewal disclosure and your terms-of-service link. A fast way to catch a missing policy before a processor or marketplace does.

FAQ

Does a "detected" result prove my store meets the law? No. A detected result only means the scan found a refund/return/cancellation link or policy wording on that page. It does not read the policy's terms, judge whether they satisfy any specific law, and it is not legal advice or certification. Treat it as a signal to confirm with your own review.

Will the scan read my policy and tell me if the terms are correct? No. The detector checks for the presence of a policy link or policy language. Whether your withdrawal window, exceptions, and refund timing meet a given jurisdiction's rules is outside what this presence-only signal evaluates.

My policy is on a separate page — why was it not detected? LaunchTrust reads the single page you submit. If the policy lives on another URL the scanned page doesn't link to, the signal can show "not detected." Add a footer link to the policy from the page you're scanning, then re-run.

Do digital products and subscriptions need a refund policy too? Often yes, though treatment differs — some jurisdictions allow exceptions for digital content a buyer agreed to access immediately, and subscriptions add auto-renewal and cancellation expectations. Disclosing your terms clearly is the safer default; see the subscription and auto-renewal disclosure check for the recurring-billing side.

Compliance aid, not legal advice. LaunchTrust reports signals, not a verdict or certification.