In everyday shop language, people often say: “The customer wants to send something back.”
But that usually means more than just the physical return. Several things are often involved at the same time: withdrawal, return, return shipment, refund, warehouse, support and accounting.
A withdrawal is the customer’s declaration:
“I want to undo this contract.”
In short:
Withdrawal: The customer declares that the contract should be undone.
Return: The goods are sent back.
The two can belong together, but they are not the same thing. This distinction becomes particularly important in view of the new withdrawal button.
From 19 June 2026, the electronic withdrawal function becomes relevant for many online contracts. It is primarily about the digital start of the withdrawal – not automatically the entire returns process.
What is a withdrawal?
A withdrawal is the declaration that a customer wants to undo a contract.
In an online shop, for example, it might look like this: someone orders a product.
After the purchase, they change their mind.
They declare: “I withdraw from this purchase.”
Important: the withdrawal is first of all a declaration:
- no parcel yet
- no return label yet
- no inspection of the goods yet
- no refund yet
The withdrawal is the first step. It says: this contract should be reversed.
The new withdrawal button is about exactly this first step. Consumers should be able to submit their withdrawal declaration through an electronic withdrawal function. The entry point must be clearly labelled, for example with “Withdraw from contract” or equally clear wording.
The withdrawal button concerns the withdrawal first, not the entire returns logistics process.
Our overview explains what the electronic withdrawal function means for WooCommerce shops in general.
Link:
Withdrawal Button 2026: What WooCommerce Shops Need to Know
What is a return?
A return is the physical shipment of the goods back to the shop.
In other words, the practical part:
- Pack the goods.
- Send the parcel.
- Check receipt in the warehouse.
- Assess the condition.
- Prepare the refund.
A return can follow a withdrawal. In many shops, this happens every day: the customer withdraws, the goods come back, the shop checks them and issues a refund.
Even so, the return is not the withdrawal itself.
In short:
Withdrawal = declaration.
Return = sending the goods back.
Or even more simply: the withdrawal starts the process. The return brings the goods back.
This distinction may sound small, but it makes a big difference in day-to-day shop operations.
Why “return it” is often too vague
Example: a customer orders three products from a WooCommerce shop:
- a standard product
- a personalised product
- a digital product
A few days later, they write:
“Hello, I would like to return this.”
That sounds clear at first. But it is not.
The shop now has to clarify:
- Which order is involved?
- Does it concern all items or only part of the order?
- Can the personalised product be withdrawn from at all?
- Are there special rules for the digital product?
- Do goods need to be sent back?
- Has the withdrawal already been declared unambiguously?
- Who handles the case internally?
This shows the problem: “Return it” is everyday language. For the shop workflow, that is often not precise enough.
Only once the withdrawal has been recorded clearly can the rest of the process continue sensibly: return shipment, inspection, refund or support communication.
What the withdrawal button actually solves
The term “withdrawal button” sounds small. But it can quickly create the wrong expectation. Some people assume it means they need a complete returns portal.
Not necessarily.
The withdrawal button does not automatically handle:
- shipping labels
- warehouse inspection
- refunds
- the entire returns workflow
It mainly concerns the digital start of the withdrawal. In other words, the moment when customers declare:
“I withdraw from this contract.”
Further steps can follow afterwards, for example:
- organise the return shipment
- inspect the goods
- prepare the refund
- close the case internally
But that is the downstream process.
The withdrawal button first ensures that the withdrawal can be declared online. The idea is that withdrawing online should be similarly easy to concluding the contract online.
What does this mean for WooCommerce shops?
WooCommerce stores a great deal of information that can be important for a withdrawal:
- orders and customer data
- items, quantities and statuses
- email addresses and guest orders
That is why the withdrawal should not run somewhere alongside the shop.
If a customer simply writes: “I want to return this”, someone in the shop first has to work out exactly what they mean.
With a simple order, that may be resolved quickly. With multiple items, variations, digital products or personalised products, it becomes much less clear.
The withdrawal should be recorded clearly first:
- Which order is affected?
- Which items are being withdrawn?
- Was the withdrawal confirmed unambiguously?
- Where does the case go internally?
Only then do the next steps follow: return shipment, inspection, refund or internal coordination.
A good WooCommerce process therefore does not simply cover the “return”. It starts earlier: with a clear withdrawal declaration.
How Widerrufsmanager helps
The Widerrufsmanager for WooCommerce starts at exactly this point.
It is not a traditional returns portal. It is designed to map the withdrawal process technically within WooCommerce.
That means:
- Customers start the withdrawal in the shop.
- The order is verified.
- Items can be selected.
- The withdrawal is confirmed.
- The case appears in the WooCommerce backend.
This records the withdrawal as a case of its own before the subsequent steps begin.
This helps shop operators keep withdrawal and return more clearly separated:
- The withdrawal is declared unambiguously.
- The order is linked.
- The affected items are visible.
- Further internal processing is clearer.
In short:
Widerrufsmanager handles the withdrawal.
Not every detail of the return.
And that distinction is important. Anyone who sees the withdrawal button merely as a returns issue is thinking too late in the process. The decisive step happens earlier: at the withdrawal declaration.
What Widerrufsmanager does not replace
This should also be clear: Widerrufsmanager does not replace individual legal advice. It does not make a blanket decision about which products in your specific shop are eligible for withdrawal. Nor does it automatically replace your entire returns logistics process.
Shop operators should also have the following checked:
- whether the withdrawal information needs to be updated
- which products or services are excluded from the right of withdrawal
- how returns and refunds are organised internally
- which legal texts are suitable for the shop
Widerrufsmanager provides the technical foundation for recording and processing withdrawals in WooCommerce in a more structured way. Legal assessment and the organisational follow-up processes remain the responsibility of the shop operator, legal adviser or legal-text provider.
Conclusion: first the withdrawal, then the return
Withdrawals and returns often belong together in day-to-day shop operations. Even so, they should not be mixed up.
The withdrawal is the declaration.
The return is the shipment back.
The new withdrawal button mainly concerns the first step: customers should be able to declare their withdrawal online. For WooCommerce shops, it is therefore important to link this process clearly to the order and make it possible to handle it internally.
That is exactly what the Widerrufsmanager for WooCommerce is built for.
Widerrufsmanager starts with the withdrawal – not the parcel label.
It helps you link the withdrawal declaration clearly to the WooCommerce order and process it internally.