A Clean Workflow for Handling Withdrawal Requests

Handling withdrawal requests badly is expensive: missed deadlines, inconsistent refunds, and no paper trail when something is disputed. Handling them well is mostly about having a workflow that anyone on the team can run the same way every time. This tutorial lays out a four-stage process — intake, acknowledge, refund, log — with SLAs and a checklist you can adopt as-is.

This article is general information, not legal advice.

Why you need a defined workflow

The EU right of withdrawal comes with hard timeframes. In broad terms, customers generally have 14 days to withdraw and up to a further 14 days to return the goods; you must refund within 14 days of being informed (you may withhold the refund until goods are returned or proof of return is provided). Miss the disclosure entirely and the withdrawal window can stretch to 12 months. Deadlines this specific do not survive ad-hoc handling. They need a repeatable process.

Stage 1 — Intake

Goal: capture every request in one place with everything you need to act.

• Every withdrawal should enter through a single channel — ideally the self-service form, not scattered across email, chat, and DMs.
• Capture order reference, customer contact, order/delivery date, and timestamp at intake.
• Timestamp is critical. It starts your refund SLA clock and proves the request date.

SLA: requests are registered the moment they arrive. With a self-service form this is automatic; with email, log it into your system the same business day.

Using Blockly — Right of Withdrawal collapses this stage to zero manual effort: the persistent, no-login button feeds every request into one dashboard with a timestamp already attached, so nothing gets lost in an inbox.

Stage 2 — Acknowledge

Goal: confirm receipt on a durable medium, fast.

• Send a confirmation email that references the order, states the request is received, and explains next steps and the refund timeframe.
• Make it a durable record (email), not just an on-screen message.
• If the customer must return goods, include return instructions and the address here.

SLA: acknowledge within 24 hours. Blockly's automated legal confirmation email does this instantly, which also removes the risk of a rep forgetting.

Stage 3 — Refund

Goal: refund the right amount, within the deadline.

• Refund the price of the goods plus the original standard delivery cost. You are generally not required to reimburse premium shipping upgrades beyond the standard option.
• The customer typically bears the cost of returning the goods, unless you agreed otherwise or failed to inform them of that.
• You may withhold the refund until you receive the goods back or the customer provides proof of return.
• Refund using the same payment method the customer used, unless they agree to another.

SLA: process within 14 days of being informed of the withdrawal (subject to the return-of-goods condition above). In practice, aim to refund within a few business days of receiving the return to stay comfortably inside the window.

Stage 4 — Log

Goal: leave proof you can produce on demand.

• Record what happened and when: request date, acknowledgment date, refund date, and amount.
• Store it somewhere durable and retrievable, not in a rep's personal inbox.
• Be able to generate a per-order report if an authority, payment provider, or customer disputes the handling.

Blockly maintains the dashboard and produces PDF audit reports, so this stage is a byproduct of the workflow rather than extra admin.

The SLA summary

• Intake: registered on arrival (auto with a form).
• Acknowledge: within 24 hours, by email.
• Refund: within 14 days of being informed; sooner once goods are returned.
• Log: recorded at each stage, retrievable indefinitely.

The repeatable checklist

Print this and hand it to whoever handles requests:

• [ ] Request captured in the central system with a timestamp.
• [ ] Order verified and within the withdrawal window.
• [ ] Confirmation email sent within 24 hours.
• [ ] Return instructions provided (if goods must come back).
• [ ] Goods received or proof of return obtained.
• [ ] Refund issued for goods + standard delivery, same payment method.
• [ ] Refund date and amount logged.
• [ ] Audit record complete and retrievable.

Common failure points to watch

• Multiple intake channels. Requests in DMs and chat get missed. Funnel everything to one place.
• Silent processing. No acknowledgment means the customer opens a chargeback while you are "working on it."
• Refunding the wrong amount. Forgetting original standard shipping is a frequent, avoidable complaint.
• No record. Handling it correctly but being unable to prove it is nearly as risky as not handling it.

Wrapping up

A clean withdrawal workflow is four repeatable stages with clear SLAs and a checklist anyone can follow. Automate the intake, acknowledgment, and logging so your team only has to make the judgment calls and process the refund on time.

Want the intake, confirmation, and audit trail handled automatically? Set up Blockly — Right of Withdrawal and run this workflow on autopilot.