The confirmation of receipt for withdrawals: what belongs in it and how it sends itself

When people talk about the Withdrawal Button, it's all about the button: visible, clearly labelled, mandatory from 19 June 2026. What tends to get lost is the step right after it – the confirmation of receipt. This is exactly where many stores trip: they get the button working somehow, but underestimate the duty behind it.

This post explains what the confirmation of receipt is, what legally belongs in it, why it can't be handled by hand – and how it goes out automatically in your Shopify store. If you sell into Germany or the wider EU, this is the part of the new rules most likely to catch you out.

What the confirmation of receipt is – and isn't

When your shopper submits a withdrawal through the Withdrawal Button, they make a binding legal declaration. The law requires you to confirm receipt of that declaration without undue delay – on a durable medium, usually by e-mail. That confirmation is the confirmation of receipt (in German, the Eingangsbestätigung).

Its purpose is to prove receipt (Zugang): it documents that the withdrawal declaration reached you, and when. That makes it your own evidence in a dispute, not just a courtesy to your shopper.

It matters just as much what the confirmation of receipt is not:

• It is not an approval. You can't "accept" or "decline" a withdrawal – it's effective the moment it's submitted. The confirmation only documents receipt.
• It is not a refund confirmation. The repayment is a separate, later step.
• It is not a return confirmation. A withdrawal isn't a return request – even though both ultimately lead to goods coming back. Why that distinction matters is covered in our post on withdrawal vs. return.

What legally belongs in it

The law doesn't prescribe wording, but it does prescribe substance. A solid confirmation of receipt should cover these points:

• Confirmation that the withdrawal declaration was received – clear and unambiguous, not buried between marketing.
• The date and time of receipt. The timestamp is the core: the deadlines for unwinding the contract run from it.
• A reference to the order or the contract concerned, so the case can be assigned unambiguously.
• A durable medium. The e-mail must be such that your shopper can store it and retrieve it unchanged – a fleeting notice on a web page isn't enough.

The tone can be friendly; the function stays legal. In case of doubt this e-mail is your evidence. It has to go out reliably – for every single withdrawal, no exceptions.

Why doing it by hand isn't an option

In theory it sounds manageable: a withdrawal comes in, you write a confirmation back. In practice that fails on three counts.

Withdrawals don't keep office hours. They arrive at night, on weekends, on public holidays, while you're away. "Without undue delay" doesn't mean "Monday morning". Confirm by hand and you produce exactly the gaps that get expensive in a dispute.

The timestamp has to be right. If you only confirm hours or days later by hand, you dilute your own proof. Clean documentation is created at the moment of receipt – not when you next open your inbox.

People forget. A single overlooked declaration is enough for a legal violation. And in Germany, a breach of the new withdrawal duties can draw a cease-and-desist letter (an Abmahnung). A process that depends on someone paying attention isn't a process – it's a risk.

How the confirmation of receipt sends itself

This is exactly what the ZackReturns withdrawal module is built for. It treats the withdrawal separately from the returns management – because in law it's something different – and automates the duty behind it:

• Instant confirmation of receipt. The moment your shopper submits the withdrawal through the button, the confirmation goes out automatically – regardless of the time or day of the week.
• Capture with a timestamp. Every withdrawal is logged with the date and time of receipt. The proof is created automatically, not after the fact.
• Legally sound documentation. The whole case is recorded in a GDPR-compliant way – from receipt through the confirmation to further processing.
• Deadline and exception checks. The module automatically checks the deadlines and flags exceptions such as B2B orders or vouchers.

That turns the confirmation of receipt from an item on your to-do list into an automatic step that runs just as reliably on every withdrawal.

Confirmation of receipt ≠ refund

One last common slip: the confirmation of receipt isn't the end of the case. It only confirms that the declaration arrived. What follows is the actual unwinding of the contract – refunding the purchase price, including the standard outbound shipping cost, within the deadline, once the conditions for it are met.

Documenting both cleanly and separately is the heart of a legally sound withdrawal process: first the evidenced receipt, then the evidenced refund. Automate both and you never have to worry about either timestamp again. For the full picture of the 2026 obligation, see our post on the EU Withdrawal Button arriving 19 June 2026 and our Withdrawal Button page.

---

This post provides general information and is not legal advice. Please have the implementation – including the wording of your confirmation of receipt – reviewed by a lawyer.

Want the confirmation of receipt cleanly automated before 19 June? ZackReturns is currently in open beta – book a free setup call: we'll look at your store together and set up the withdrawal module with you. About 20 minutes, no strings attached, directly with the founder.