This module allows you to define the carrier for receipt in the RMA creation wizard from the sales order.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you choose a reception carrier when creating an RMA from a sales order, so returned goods can be shipped back with a specific delivery method.
When you create a return (RMA) from a sales order, this module adds a "Reception Carrier" field to the RMA creation wizard. The field appears right after the operation field and is only shown when the company's RMA reception strategy is set to the RMA method.
The list of carriers you can pick from is filtered automatically: only carriers that are available for the customer's shipping address and the sales order are offered, and only carriers belonging to the wizard's company. If no shipping partner is set, all company carriers are shown.
When the RMA records are created from the wizard lines, the selected reception carrier is copied onto each generated RMA, so the return is linked to that carrier from the start.
This module works together with the RMA sales and RMA delivery modules and touches the RMA creation wizard for sales orders (sale.order.rma.wizard and sale.order.line.rma.wizard). It adds no new menus or reports; the change is visible inside the existing RMA wizard screen.
Depends on
Required by other modules
Models and fields (2)
- sale.order.rma.wizard · extends an existing modelcompany_id, reception_carrier_id (Reception Carrier), rma_reception_strategy, available_reception_carrier_ids
- sale.order.line.rma.wizard · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/rma.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.