> 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/minimum-value-return-and-maximum-value-return.md).

# Minimum Value Return and Maximum Value Return

Steer customers towards alternative actions for returns that are valued below or above a defined threshold.

## Overview

Minimum Value Return and Maximum Value Return options can be configured for your <code class="expression">space.vars.Product\_ReturnsPortal</code> to prevent label generation and direct customers to alternative actions (for example: keeping an item or contacting customer service).

The **Minimum Value Return** feature can be used to inform customers that a return is not required and offered randomly based on the configured probability to prevent fraudulent returns. This information will be displayed on the confirmation page of the <code class="expression">space.vars.Product\_ReturnsPortal</code> when the selected items are priced lower than the defined value.

The **Maximum Value Return** feature allows the definition of a different process in case the price of the selected items is higher than the defined value.

#### Key Benefits

Both features can be used to streamline return processes for items. For low-value items, using the Minimum Value Return feature can reduce the cost of processing the return and reduce return volume in your warehouses. For high-value items, the Maximum Value Return feature can be used to direct customers to specific actions to ensure the safe return of expensive products.

## Configuring the Minimum Value Return Feature

The following sections describe the configuration required for the Minimum Value Return feature.

{% hint style="info" %}
The Minimum Value Return feature can be configured based on compensation methods.
{% endhint %}

### Customer Requirements

For the feature to work, you need to provide the following:

* The value threshold of the item to trigger the alternative action (for example: $10).
* The text to be displayed on the return confirmation page.
* The probability for triggering the threshold in percentage (for example: 20%).
* The compensation method for which the feature should be activated (for example: refund).
* The maximum number of low-value returns that can be registered per customer within a 90-day period.

### Implementation Process

To activate this feature, please contact your parcelLab representative with the information specified under the [Customer Requirements](#customer-requirements) section.

## Configuring the Maximum Value Return Feature

The following sections describe the configuration required for the Maximum Value Return feature.

{% hint style="info" %}
The Maximum Value Return feature can be configured based on compensation methods.
{% endhint %}

### Customer Requirements

For the feature to work, you need to provide the following:

* The value threshold of the item to trigger the alternative action (for example: $1000).
* The text to be displayed on the return confirmation page.
* The probability for triggering the threshold in percentage (for example: 60%).
* The compensation method for which the feature should be activated (for example: refund).

### Implementation Process

To activate this feature, please contact your parcelLab representative with the information specified under the [Customer Requirements](#customer-requirements-1) section.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parcellab.com/docs/retain/returns-portal/features/minimum-value-return-and-maximum-value-return.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.