RMA reason about rma

[jbaudoux]

In fact, it serves two different purpose.
I use the operation to dictate what process should apply (return, refund, replace...) and which will create the right transfer (incoming, delivery or both, credit note...). In my use cases, it is the after-sales service that choose the right operation to apply.
The reason would explain the cause of this RMA like: wrong item delivered, customer don't want the product anymore, product has a defect, wrong product description... In the same spirit than https://github.com/OCA/sale-workflow/tree/16.0/sale_cancel_reason

[chienandalu]

Well, that's what the RMA operations are for. The module pre-creates three of them, but you can change them or add as many as you want to.

And customers in the sale portal can select them and even add notes per return line

[chienandalu]

I understand. There's a similar optional feature (group_rma_manual_finalization) for manual finalization reasons. Maybe you could propose a similar approach.

[jbaudoux]

I understand. There's a similar optional feature (group_rma_manual_finalization) for manual finalization reasons. Maybe you could propose a similar approach.

Can you provide the link to that module, I can't find it ?

[chienandalu]

It's in the rma module itself. Follow the code for this option:

rma/rma/models/res_config_settings.py

Lines 9 to 13 in eeb0672

	group_rma_manual_finalization = fields.Boolean(
	string="Finish RMA manually choosing a reason",
	help="Allow to finish an RMA without returning back a product or refunding",
	implied_group="rma.group_rma_manual_finalization",
	)

[jbaudoux]

I updated the issue with the proposed solution specifications