---
title: Auto-Mark as Done
description: "Auto-mark as done is a policy rule setting that automates marking a return request as Done. \nReturnGO considers the RMA processing as done when all the customer requests are fulfilled. \nIf any item included is set to be manually marked as done, then the entire RMA will need to be manually marked as done."
---

[Skip to content](https://support.returngo.ai/auto-mark-as-done#main-content)

English

Show submenu for translations

[Customer portal](https://support.returngo.ai/tickets-view?hsLang=en)

![ReturnGO Logo-1](https://support.returngo.ai/hs-fs/hubfs/ReturnGO%20Logo-1.png?width=198&height=30&name=ReturnGO%20Logo-1.png)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Customer portal](https://support.returngo.ai/tickets-view)
- Go to returngo.ai

 Go to returngo.ai

 Hello. How can we help you?

- There are no suggestions because the search field is empty.

1. [Knowledge Base](https://support.returngo.ai/?hsLang=en)
2. [Returns Management](https://support.returngo.ai/returns-management?hsLang=en)
3. [Automation](https://support.returngo.ai/returns-management?hsLang=en#automation)

# Auto-Mark as Done

Last Updated: May 26, 2026

*Auto-Mark as Done* is a policy rule setting that automates marking a return request as *Done* once all required actions in the RMA are completed, based on the conditions and schedules you define.

ReturnGO considers [**RMA**](https://support.returngo.ai/rma-card-details?hsLang=en) processing complete when all configured conditions across the applicable policy rules are fulfilled.

![](https://support.returngo.ai/hs-fs/hubfs/Auto-Mark%20as%20Done1-png.png?width=670&height=120&name=Auto-Mark%20as%20Done1-png.png)

**Note:** If any item included in the RMA is set to be manually marked as done, the entire RMA must be manually marked as done.

### How Auto-Mark as Done Works

*Auto-Mark as Done* is triggered when all configured conditions in the RMA are met. These conditions depend on the resolutions applied and the automation rules defined in the policy.

When multiple conditions or policy rules apply to the same RMA, ReturnGO evaluates them using *AND* logic. The RMA is marked as done only after all conditions across all applicable rules are fulfilled.

### What Triggers the Auto-Mark as Done Automation?

*Auto-Mark as Done* supports the following triggers. Each one marks the RMA as done when the specified condition is fulfilled:

- **Full validation:** All items in the RMA are fully validated with positive results.
- **Partial validation:** All items have a validation status, positive or negative. Useful when no further action is expected.
- **Full amount refund/payment:** The total refund or payment amount has been issued and processed.

**Note:** If you are using *refund* as a trigger, the RMA is marked as *done* only after the refund transaction receives a *success* status update.

- **Exchange released:** The draft order for an exchange has been released, and, if applicable, any price difference has been paid.
- **Other automation events:** Additional automated processes configured in your policies, such as custom workflow triggers.

You can configure *Auto-Mark as Done* to execute:

- Immediately, once all conditions are met, or
- After a defined delay, to align with other operational processes

**Note:** If multiple delays are configured, ReturnGO applies the longest delay to ensure predictable behavior.

### Resolution-Based Trigger Handling

The following resolution behaviors are evaluated as part of *Auto-Mark as Done* condition handling:

#### Variant or Product Exchanges

When all resolutions are exchanges, the exchange condition is fulfilled once the draft order is marked as *Released*.

- **If there is a price difference:** The RMA will be marked as done once the customer has paid the price difference and the draft order is marked as *Paid*.
- **If there is no price difference:** The RMA will be marked as done once the draft order is marked as *Released*.

#### Refunds

In order for an RMA to be marked as done after issuing a refund, ReturnGO waits for a *success* status update.

As long as the transaction is still in a *pending* status, the RMA is not marked as done.

**Balance calculation:**

Balance = (Total paid price + Rewards) - Fees

#### Mixed Resolutions

*Auto-Mark as Done* supports RMAs with mixed resolutions. The RMA is marked as done only after all configured conditions related to refunds, exchanges, and validations are completed.

### Requirements

This feature is available as an [**add-on**](https://support.returngo.ai/add-ons?hsLang=en)**.**

### Enabling Auto-Mark as Done

To configure Auto-Mark as Done:

1. Go to [**Settings \> Return Policy.**](https://app.returngo.ai/dashboard/settings/policy-rules)
2. Click **EXPAND ALL** to configure an existing policy rule.
3. Click the *pencil* icon on the right of the policy rule.  
   ![Configuring Auto-Approval](https://support.returngo.ai/hs-fs/hubfs/Configuring%20Auto-Approval.png?width=644&height=302&name=Configuring%20Auto-Approval.png)
4. Open the *RMA Handling Process* section.
5. Choose **AUTOMATIC** in the *Mark as Done* setting.  
   ![Auto Mark as done 3](https://support.returngo.ai/hs-fs/hubfs/Auto%20Mark%20as%20done%203.png?width=670&height=346&name=Auto%20Mark%20as%20done%203.png)
6. Select one or multiple triggers.  
   ![Auto Mark as done 4](https://support.returngo.ai/hs-fs/hubfs/Auto%20Mark%20as%20done%204.png?width=670&height=338&name=Auto%20Mark%20as%20done%204.png)
7. Define whether the automation should execute immediately or after a delay (in hours or days).
8. Click the *save* icon to save your changes.  
   ![Auto Mark as done 5](https://support.returngo.ai/hs-fs/hubfs/Auto%20Mark%20as%20done%205.png?width=670&height=326&name=Auto%20Mark%20as%20done%205.png)

**Note:** Repeat these steps for each policy rule you want to configure.

### Examples of Auto-Mark as Done

**1. Single Trigger: Partial Validation**

**Scenario:** An RMA contains two items, and *Partial validation* is selected as the trigger. Both items are validated (one returned, one not returned).

**Result:** Once all items have a validation status, ReturnGO automatically marks the RMA as *Done*, even if some items are negatively validated.

**2. Multiple Triggers: Partial Validation + Full Refund**

**Scenario:** An RMA contains two items, with *Partial validation* and *Full amount refund* selected as triggers. Both items are validated, and the total refund is issued.

**Result:** ReturnGO monitors both triggers and only marks the RMA as Done once all selected triggers are fulfilled. This ensures that the RMA does not close prematurely if, for example, the refund is still processing.

**3. Mixed Resolutions / Multiple Policy Rules**

**Scenario:** An RMA has one item to be refunded and one item to be exchanged. Two policy rules apply:

**Policy A:** Trigger on *Full refund* with 1-day delay

**Policy B:** Trigger on *Exchange released* with 3-day delay

The refund is issued, and the exchange is released.

**Result:** ReturnGO evaluates all triggers across both policies, applies the longest delay (3 days), and then marks the RMA as *Done*. This ensures that complex RMAs are marked as done only after every required action is completed.

- [Account & Setup](https://support.returngo.ai/account-setup?hsLang=en#main-content)

    - [Getting Started](https://support.returngo.ai/account-setup?hsLang=en#getting-started)
    - [Installing ReturnGO](https://support.returngo.ai/account-setup?hsLang=en#installing-returngo)
    - [Account Settings](https://support.returngo.ai/account-setup?hsLang=en#account-settings)
    - [Billing](https://support.returngo.ai/account-setup?hsLang=en#billing)
    - [Portal Customization](https://support.returngo.ai/account-setup?hsLang=en#portal-customization)
    - [Emails](https://support.returngo.ai/account-setup?hsLang=en#emails)
    - [FAQs](https://support.returngo.ai/account-setup?hsLang=en#faqs)
- [Returns Management](https://support.returngo.ai/returns-management?hsLang=en#main-content)

    - [Processing Returns](https://support.returngo.ai/returns-management?hsLang=en#processing-returns)
    - [Return Portals](https://support.returngo.ai/returns-management?hsLang=en#return-portals)
    - [Advanced Returns Management](https://support.returngo.ai/returns-management?hsLang=en#advanced-returns-management)
    - [Return Methods](https://support.returngo.ai/returns-management?hsLang=en#return-methods)
    - [Return Policy](https://support.returngo.ai/returns-management?hsLang=en#return-policy)
    - [Automation](https://support.returngo.ai/returns-management?hsLang=en#automation)
    - [Inventory](https://support.returngo.ai/returns-management?hsLang=en#inventory)
    - [Return Reasons](https://support.returngo.ai/returns-management?hsLang=en#return-reasons)
    - [Warranty Management](https://support.returngo.ai/returns-management?hsLang=en#warranty-management)
- [Return Resolutions](https://support.returngo.ai/return-resolutions?hsLang=en#main-content)

    - [Refunds](https://support.returngo.ai/return-resolutions?hsLang=en#refunds)
    - [Exchanges](https://support.returngo.ai/return-resolutions?hsLang=en#exchanges)
    - [Other Resolutions](https://support.returngo.ai/return-resolutions?hsLang=en#other-resolutions)
- [Return Shipping](https://support.returngo.ai/return-shipping?hsLang=en#main-content)

    - [Ship by ReturnGO](https://support.returngo.ai/return-shipping?hsLang=en#ship-by-returngo)
    - [Shipping Labels](https://support.returngo.ai/return-shipping?hsLang=en#shipping-labels)
    - [Shipping Settings](https://support.returngo.ai/return-shipping?hsLang=en#shipping-settings)
    - [QR Codes](https://support.returngo.ai/return-shipping?hsLang=en#qr-codes)
- [Shipping Integrations](https://support.returngo.ai/shipping-integrations?hsLang=en#main-content)

    - [Shipping Integrations](https://support.returngo.ai/shipping-integrations?hsLang=en#shipping-integrations)
    - [Shipping Aggregators](https://support.returngo.ai/shipping-integrations?hsLang=en#shipping-aggregators)
    - [Shipping Carriers](https://support.returngo.ai/shipping-integrations?hsLang=en#shipping-carriers)
    - [Drop-Off Services](https://support.returngo.ai/shipping-integrations?hsLang=en#drop-off-services)
- [Other Integrations](https://support.returngo.ai/other-integrations?hsLang=en#main-content)

    - [Helpdesk Integrations](https://support.returngo.ai/other-integrations?hsLang=en#helpdesk-integrations)
    - [3PL/WMS Integrations](https://support.returngo.ai/other-integrations?hsLang=en#3pl-wms-integrations)
    - [Fintech Integrations](https://support.returngo.ai/other-integrations?hsLang=en#fintech-integrations)
    - [Loyalty Integrations](https://support.returngo.ai/other-integrations?hsLang=en#loyalty-integrations)
    - [Marketing Integrations](https://support.returngo.ai/other-integrations?hsLang=en#marketing-integrations)
    - [ERP Integrations](https://support.returngo.ai/other-integrations?hsLang=en#erp-integrations)
    - [ReturnGO API](https://support.returngo.ai/other-integrations?hsLang=en#returngo-api)
- [Order Tracking](https://support.returngo.ai/order-tracking?hsLang=en#main-content)

    - [Order Tracking Portal](https://support.returngo.ai/order-tracking?hsLang=en#order-tracking-portal)
    - [Order Tracking Notifications](https://support.returngo.ai/order-tracking?hsLang=en#order-tracking-notifications)
- [Analytics](https://support.returngo.ai/analytics?hsLang=en#main-content)

    - [Analytics](https://support.returngo.ai/analytics?hsLang=en#analytics)
    - [Reports](https://support.returngo.ai/analytics?hsLang=en#reports)
- [Legacy Features](https://support.returngo.ai/legacy-features?hsLang=en)

[![Chill listening crop-3](https://support.returngo.ai/hs-fs/hubfs/RETURNGO%20BLUE.png?width=162&height=24&name=RETURNGO%20BLUE.png "Chill listening crop-3")](https://returngo.ai)

knowledge Base

Copyright © 2026, ReturnGO