How to Set Up WooCommerce Refunds and Returns for Beginners

A customer who wants their money back is one of the fastest ways to find out whether a store was actually built with refunds in mind, or whether that got left for later. If there’s no clear policy and no obvious process, a routine return turns into a back-and-forth over email that eats far more time than it should — and often ends with a refund given anyway, just later and with more friction than necessary.

In most stores I set up, refunds and returns get treated as an afterthought right up until the first support ticket forces the issue. WooCommerce already has the tools built in — a policy page, order-level refund controls, and email notifications — they just need to be configured deliberately rather than left on their defaults. There’s also a legal floor underneath all of this that a lot of store policies quietly ignore.

The Legal Floor: EU and UK’s Mandatory 14-Day Right of Withdrawal

If you sell physical goods to consumers in the EU or UK, a 14-day return window isn’t a courtesy you’re choosing to offer — it’s a legal minimum under the EU Consumer Rights Directive (and the UK’s equivalent Consumer Contracts Regulations), and it applies regardless of what your own returns policy page says. The clock starts from the day the customer (or someone they designate) receives the goods, not the day they ordered. A policy that promises less than 14 days to an EU or UK customer isn’t enforceable against that right; a policy that promises more is fine, since the 14 days is a floor, not a ceiling.

This matters for how you write the policy page below. “Returns accepted within 30 days” is a store choosing to be generous on top of the legal minimum — good practice, but worth knowing it’s a choice, not the whole of what applies. If your customer base is entirely outside the EU/UK, this specific rule doesn’t bind you, but it’s worth checking your own jurisdiction’s consumer protection law for an equivalent, since several other countries have adopted similar cooling-off periods.

Digital Products Are a Legal Exception — If You Set It Up Right

The same directive carves out a specific exception for digital content that isn’t delivered on a physical disc or drive — exactly the kind of downloadable product covered in my guide on selling digital downloads in WooCommerce. A customer’s right to withdraw can be forfeited the moment they start downloading, but only if three specific conditions were met first: the customer gave express, informed consent to start the download immediately (rather than waiting out the 14 days), the customer separately acknowledged that starting the download means losing the right to withdraw, and the store confirmed all of this in writing.

In practice, this means a checkout checkbox along the lines of “I agree to immediate access to this digital product and acknowledge I lose my right of withdrawal once download begins” isn’t optional legal decoration — it’s the specific mechanism that makes “digital products are non-refundable once accessed” actually hold up. A store that grants instant digital access without this consent step is still technically bound by the 14-day window on digital products too, whatever the policy page says.

Writing the Policy Page

WooCommerce creates a Refund and Returns Policy page automatically during setup, but it ships with placeholder text that needs replacing. Cover the return window in days (remembering the 14-day floor above), which items qualify and which don’t (final sale or personalised items, for example), who pays return shipping, and how long a refund takes to appear once approved. Specific numbers beat vague language every time; “returns accepted within 30 days” settles more disputes before they start than “reasonable return period.”

A policy nobody can find might as well not exist. Add the page to the site footer menu so it’s visible from every screen, and check that WooCommerce > Settings > Advanced has the correct page selected under “Endpoints,” since this is what powers the automatic link WooCommerce places near the checkout button.

Configuring WooCommerce’s Refund Tools

Open the order in WooCommerce > Orders and select “Refund” to see both options. Automatic refunds route the money back through the original payment gateway — Stripe and PayPal both support this directly from the order screen, and it’s the faster option for the customer. Manual refunds record that a refund happened without moving money through the gateway, useful when a refund was already issued outside WooCommerce (a bank transfer, for instance) and the order simply needs to reflect that. Using manual refunds for a genuine gateway refund breaks the payment record, so match the option to what actually happened.

WooCommerce automatically sets an order to “Refunded” once a refund is processed through the order screen, and this status update is also what triggers the customer’s refund confirmation email — make sure WooCommerce’s email settings are configured correctly, since leaving orders on “Processing” after a refund confuses both stock reports and the customer, who never gets told the refund actually went through.

Handling a Return Request Without Losing a Day

A simple contact form or a dedicated support email both work for smaller stores — the point is having one clear channel stated on the policy page, rather than customers guessing whether to use the contact form, a social media message, or a live chat widget. Ask for the order number in every return request; without it, matching a request to the right order takes far longer than it should. Reply within a day where possible — slow responses turn a routine return into a negative review far more often than the refund itself does.

Physical products follow the standard 14-day window above at minimum. Digital products — downloads, licence keys, courses — can be treated as non-refundable once accessed, but only with the consent checkbox described earlier actually in place. Customised or made-to-order items often need a shorter window or no returns at all, since they can’t be resold once made — state each case separately on the policy page rather than writing one line and hoping it covers every product type by implication.

Practical Tips

• Keep return instructions to a short numbered list on the policy page — customers skim this under stress, not read it carefully.
• Record why each refund was issued, even briefly. A running note of refund reasons shows up patterns — a product with a recurring sizing complaint, for instance — worth acting on.
• Process a test refund on a low-value order before launch, so the first real one isn’t also the first time the process gets tested.
• If you sell across both the EU/UK and other regions, keep the 14-day language specific to where it legally applies rather than writing one global policy that either overstates or understates your obligations depending on the customer’s location.

Common Mistakes

• No visible refund policy at checkout, leaving hesitant shoppers to abandon their cart rather than ask.
• Marketing digital products as “non-refundable once accessed” without the express-consent checkbox that actually makes that exception legally hold up for EU/UK customers.
• Applying the same return rules to digital products as physical ones, which creates disputes over downloads that were already accessed.
• Refunding before checking what actually went wrong, which can hide a shipping or product issue that keeps repeating.
• Forgetting to account for original shipping costs in the refund amount, which creates confusion when the total doesn’t match what the customer expects.

When to Use This vs Alternatives

Built-in WooCommerce refund tools cover most small and mid-sized stores without any extra cost or complexity. A dedicated returns management plugin becomes worth considering once return volume is high enough that manually processing each one in the order screen is eating real time — typically stores handling dozens of returns a week rather than a handful a month. Those plugins add customer-facing return request forms, return shipping labels, and automated approval rules, but they’re overhead a low-volume store doesn’t need yet.

Conclusion

A clear policy page, correctly configured refund settings, and one consistent request channel cover refunds and returns for most WooCommerce stores without needing a plugin — but for EU and UK stores, the 14-day withdrawal right and the digital-content consent exception aren’t optional extras on top of that, they’re the legal baseline the policy page needs to reflect accurately. Get this in place before launch, following the step-by-step guide to building a WordPress website, and see WooCommerce’s own refunds documentation for gateway-specific detail once the basics are set up.