# Returns Communication

## Overview

You can send automated communication to customers for all events within the returns process (for example: return registration, drop-off confirmation, and return receipt). The feature also enables the tracking of returns packages and displaying their return status in parcelLab’s tracking plugin.

<div align="left"><figure><img src="https://1156682959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LPf1Lv1YUuLYva6LrXQ%2Fuploads%2F5MDlV5L1fMqSoEjKHnzW%2Fdressforless_ReturnDropOffThanksEmail.png?alt=media&#x26;token=02334cc0-4f49-446b-88b9-dbb1f192847c" alt="Return Email with CTA button to the corresponding Return Status Page" width="375"><figcaption><p>Return Email with CTA button to the corresponding Return Status Page </p></figcaption></figure></div>

<figure><img src="https://1156682959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LPf1Lv1YUuLYva6LrXQ%2Fuploads%2FO1H4SzmQnQ7HuHVwn7gr%2Fdresforless_ReturnTrackingPage.png?alt=media&#x26;token=d5e938e4-d9c4-4034-9f3f-c35fedbe1a75" alt="Return Status Page with delivery status updates"><figcaption><p>Return Status Page with delivery status updates</p></figcaption></figure>

### Key Benefits

With parcelLab’s <code class="expression">space.vars.Product\_ReturnsComms</code> feature, you can extend your proactive communication throughout the returns process. By sending notifications during returns, you can keep your customers updated on the status of their return, decrease the number of ‘Where is my return?’ inquiries, and use the additional touchpoints to recover revenue.

## Configuring the <code class="expression">space.vars.Product\_ReturnsComms</code> Feature

The following sections describe the configuration required for the <code class="expression">space.vars.Product\_ReturnsComms</code> feature.

### Customer Requirements

To configure returns communication, you need to provide the following information to parcelLab:

* Return tracking numbers
* Original order number
* Corresponding customer data, including email address
* Content of the returns communication, including the types of notifications (refer to the [Sample Returns Communication Flow](#sample-returns-communication-flow) section for examples)

The feature can be configured to adapt to returns processes that include but are not limited to the use cases described in the following sections.

#### parcelLab <code class="expression">space.vars.Product\_ReturnsPortal</code> with Label Generation

If you are using parcelLab’s <code class="expression">space.vars.Product\_ReturnsPortal</code> with label generation, no action is needed to send additional data. Since the returns tracking labels are provided to your customer via the parcelLab <code class="expression">space.vars.Product\_ReturnsPortal</code>, the connection between the return parcel and original order is automatically established. This connection will enable the display of the list of returned items within the returns communication.

#### <code class="expression">space.vars.Product\_ReturnsPortal</code> without Label Generation

In setups where parcelLab does not automatically have the return tracking numbers (for example: if you provide pre-printed labels or use your own returns portal), you will need to send the following data to parcelLab:

* Return tracking number
* Original order number
* Carrier code (optional)

The connection between the return tracking number and the original order number is required to enable the display of the list of returned items within the returns communication. You can send us the required information via API, file transfer, or an event bus integration.

For information on how to send data to parcelLab, refer to the following pages:

{% content-ref url="<https://app.gitbook.com/s/m5MUhYrMmT0cei4QdxGn/orders/trackings-orders>" %}
[Trackings/Orders](https://app.gitbook.com/s/m5MUhYrMmT0cei4QdxGn/orders/trackings-orders)
{% endcontent-ref %}

{% content-ref url="<https://app.gitbook.com/s/m5MUhYrMmT0cei4QdxGn/data-elements/send-data/file-transfers>" %}
[File Transfers](https://app.gitbook.com/s/m5MUhYrMmT0cei4QdxGn/data-elements/send-data/file-transfers)
{% endcontent-ref %}

{% content-ref url="../platform/data-integration/event-bus-integration" %}
[event-bus-integration](https://docs.parcellab.com/docs/platform/data-integration/event-bus-integration)
{% endcontent-ref %}

{% hint style="info" %}
If you are using parcelLab for outbound delivery communication, please send the required data for returns using the same method.
{% endhint %}

### Implementation Process

When the data integrations for return tracking numbers and delivery status have been implemented, parcelLab will check if the required data is received in full. The notifications will be set up for the requested channels (for example: email and SMS) according to the agreed content and notification type.

## Sample Returns Communication Flow

parcelLab's <code class="expression">space.vars.Product\_ReturnsComms</code> feature can be customized to adapt to your existing returns process. The following sections highlight some examples of returns communication that can be set up based on the data sent to parcelLab.

{% hint style="info" %}
These examples illustrate the most typical returns communication notifications. For further information on how the feature can be set up for your returns process, please contact your parcelLab representative.
{% endhint %}

<details>

<summary>Return Registration</summary>

Return Registration notifications (for example: emails) can be triggered via parcelLab’s Returns Portal. This notification type can include, but is not limited to the following:

* QR code for return label
* List of items registered for return
* Drop-off location finder

<img src="https://1156682959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LPf1Lv1YUuLYva6LrXQ%2Fuploads%2Fc4VHs7NcPZC9Qc4Upd01%2FH%26MUK_ReturnPortalRegistrationEmail.png?alt=media&#x26;token=a07cb204-ea56-49fc-a5e7-94e88af18257" alt="Return registration email" data-size="original">

</details>

<details>

<summary>Return Drop-Off/Pickup Confirmation</summary>

Drop-off and pickup confirmation notifications are usually associated with the first scan into the carrier network. This notification type can include a link to the Return Status page for the parcel.

<img src="https://1156682959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LPf1Lv1YUuLYva6LrXQ%2Fuploads%2FRctbkDl7urmSVSkQnjtf%2FH%26MUK_ReturnDroppedOffEmail.png?alt=media&#x26;token=588352b4-e960-468d-9c14-22587cff98e1" alt="Return drop-off/pickup confirmation email" data-size="original">

</details>

<details>

<summary>Return Received</summary>

Return receipt notifications are associated with a confirmed delivery of the return parcel to your warehouse. This notification type can include the following:

* A link to the Return Status page for the parcel
* Information on next steps in the returns process (for example: refund)

<img src="https://1156682959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LPf1Lv1YUuLYva6LrXQ%2Fuploads%2FPnlbTFvImXCvnC1jLDtU%2FH%26MUK_ReturnDeliveredEmail%202.png?alt=media&#x26;token=e4e2db68-eadd-42e5-a713-979c1a0320dc" alt="Return received email" data-size="original">

</details>