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 processing complete when all configured conditions across the applicable policy rules are fulfilled.
This feature is currently in beta and not yet available to all merchants. Apply to join the beta.
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.
- 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
When refunds are involved, the refund condition is fulfilled once the issued refund amount is equal to or greater than the balance.
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.
Enabling Auto-Mark as Done
To configure Auto-Mark as Done:
- Click EXPAND ALL to configure an existing policy rule.
- Click the pencil icon on the right of the policy rule.
- Open the RMA Handling Process section.
- Choose AUTOMATIC in the Mark as Done setting.
- Select one or multiple triggers.
- Define whether the automation should execute immediately or after a delay (in hours or days).
- Click the save icon to save your changes.
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.