This optional feature allows you to automatically issue a full refund to a customer without requiring them to return the product, when the criteria that you define are met. In some cases, returnless refunds may make economic sense if the cost of return shipping is relatively high. You can configure rules that will trigger an automatic refund for eligible returns, instantly closing out the return request.
You can also offer returnless refunds for specific products in your inventory.
Upload the file on the Return Attribute Overrides page after completing the template
The newly configured rule will apply to all orders from that time onward. You can add multiple Returnless Refund rules at the same time.
To edit an existing rule, click on the rule, choose Edit, modify the settings, and click Save.
To delete a returnless refund rule, click on the rule, click Delete, and confirm you want the rule deleted.
No – all the rules for returnless refunds need to be set up by you. Amazon will not create any rules on your behalf.
No – any return request for a product that qualifies for returnless refunds based on the rules that you have set will be automatically authorised. You do not have to take any action.
No – a refund equal to the value of the product cost will be automatically provided to the customer for a return that qualified for a returnless refund. You do not have to take any action.
Customers will get the message: “We are processing your refund. You don’t need to return the item back to us!” Customers will automatically get a refund back to the original payment method in 5-7 business days, and the refund will be charged to your seller account.
All out-of-policy return requests will continue to come to you for manual authorisation. They will not be granted a returnless refund.
All returnless refunds can be tracked in the Returns Report. Go to Seller Central > Reports > Returns Report.
All rules need to be mutually exclusive. So if you have a rule that is a subset of another rule, then you will get an error: “Edited rule is conflicting with rule: [Name of Rule]”.
This will generate an error when setting up Rule 2 as it is completely a subset of Rule 1 (i.e. any request that falls within Rule 2 will also apply under Rule 1, thus Rule 2 is unnecessary).