> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/retain/returns-portal/features/right-of-withdrawal.md).

# Right of Withdrawal Support

## Overview

The <code class="expression">space.vars.Product\_ReturnsPortal</code> can be used as the customer-facing destination for online right-of-withdrawal requests. In the standard setup, withdrawal is handled as a normal return registration with a configured `Withdrawal` return reason.

Customers select the eligible item or items, submit the request, and receive confirmation and instructions with retailer-approved wording. The submitted withdrawal details can then be sent to your systems through the same return registration and RMA/export channels used for other returns.

{% hint style="warning" %}
This page is for information purposes only and does not constitute legal advice. You remain responsible for deciding whether, where and how an online withdrawal function must be offered, and for approving all legal wording shown to customers.
{% endhint %}

## Customer Experience

A typical withdrawal journey can be configured as follows:

1. The customer selects a withdrawal link or button on your website, app or communication.
2. If the link is personalized, the customer can be taken directly into the <code class="expression">space.vars.Product\_ReturnsPortal</code>. For public website entry points, the customer identifies the order using the configured login details, such as order number and email address.
3. The portal displays eligible items based on your return period, country, product and item-eligibility configuration.
4. A `Withdrawal` return reason can be shown for eligible items and configured as the default reason, so selected items can proceed without an additional reason-selection step.
5. The customer submits the withdrawal request as a return registration and receives confirmation plus return instructions.

For full-order withdrawals before delivery, the confirmation wording can instruct the customer to refuse delivery where this is appropriate for your legal and operational process. After delivery, the customer can receive the normal return label, QR code or return instructions configured for your portal.

## Configuration Options

The standard setup uses existing <code class="expression">space.vars.Product\_ReturnsPortal</code> configuration:

| Configuration area                                                                                          | How it supports withdrawal requests                                                                                                                                          |
| ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Return Reasons](/docs/retain/returns-portal/features/return-reasons.md)                                    | Add a dedicated `Withdrawal` reason, map it to your internal return reason code, translate the label and optional note, and configure it as the default reason where needed. |
| [Return Periods](/docs/retain/returns-portal/features/return-periods.md)                                    | Define the period during which the withdrawal reason should be available. Periods can be configured by country or other setup criteria.                                      |
| [Item Eligibility](/docs/retain/returns-portal/features/non-returnable-items-and-already-returned-items.md) | Hide excluded products or display them as non-returnable according to your legal and operational setup.                                                                      |
| Confirmation and instructions                                                                               | Adapt the confirmation page and email wording for acknowledgement, return shipping, refund timing and delivery-refusal instructions where required.                          |
| RMA/export data                                                                                             | Send the selected withdrawal reason, item details and quantities through the same configured return data channels as other return registrations.                             |

Additional actions, such as calling a retailer endpoint to attempt stopping fulfillment before shipment or opening a customer-service ticket, require a custom integration.

## Portal Versions

Both Returns Portal versions can support the standard setup of a configured withdrawal return reason.

For Returns Portal v2, wording can be customized through the template and translation configuration. For Returns Portal v1, wording and popup behavior can be adapted as portal customization where required.

## Customer Requirements

To configure this flow, provide the following information to parcelLab:

* The markets and countries where the withdrawal option should be available.
* The approved wording for the withdrawal link or button, portal reason label, confirmation page and email.
* The return reason code and translations to use for withdrawal.
* The withdrawal period and any country-specific or product-specific exclusions.
* The return shipping instructions, refund timing wording and delivery-refusal wording you want to show customers.
* The RMA/export, ticketing or endpoint requirements for notifying your internal systems.

## Implementation Process

When parcelLab has the required information, the withdrawal flow can be configured and tested in your <code class="expression">space.vars.Product\_ReturnsPortal</code>. Testing should verify that the withdrawal reason is shown only for eligible items, that the default reason behavior works as expected, and that the submitted return registration is received by your configured data channels.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parcellab.com/docs/retain/returns-portal/features/right-of-withdrawal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.