OdooWiki OCA HUB

Route Planning RMA Delivery Integration

route_planning_rma_delivery folder_open OCA/route-planning open_in_new
Uncategorised License: AGPL-3

Route Area Delivery Compatibility with RMA.

The "Delivery route area" and "Reception route area" fields will be displayed (in the RMA form and wizards) only if the selected carrier is of the "Route Planning" type (as explained in route_planning_delivery); in that case, it will be mandatory to define a route area.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

When a return (RMA) uses a Route Planning carrier, this module shows and requires a Route Area field on the RMA form and on the return/delivery wizards, and clears it automatically for other carrier types.

This module links return merchandise authorisations (RMAs) with route planning carriers. When the carrier chosen for a return or a delivery is of the "Route Planning" type, a Route area field becomes visible and mandatory; for any other carrier type the field is hidden and automatically emptied.

Where it appears: - On the RMA form, the delivery route area and reception route area fields are shown and required only when the related carrier is a Route Planning carrier. - In the "Choose delivery carrier" wizard for an RMA, the Route area field appears after the carrier and is restricted to route planning users. - In the RMA wizard, the sale order RMA wizard and the stock return wizard, the reception route area field follows the same show/hide and required rules.

Automatic behaviour: - The reception route area is computed from the reception carrier; if that carrier is not a Route Planning carrier, the field is reset to empty. - The delivery route area is computed from the carrier; if it is not a Route Planning carrier, it is reset to empty. - When the carrier wizard is opened, the route area is pre-filled from the RMA (reception area when the RMA is confirmed, delivery area otherwise), and the chosen area is written back to the correct field on the RMA.

The module touches rma, rma.choose.delivery.carrier, rma.rma.wizard, sale.order.rma.wizard and stock.return.picking.

Depends on

route_planning_deliveryroute_planning_rma_salerma_sale_delivery
Models and fields (5)
  • rma · extends an existing modelcarrier_delivery_type (Carrier delivery type), reception_route_area_id, reception_carrier_delivery_type (Reception carrier delivery type)
  • rma.rma.wizard · extends an existing modeldelivery_type, reception_route_area_id
  • stock.return.picking · extends an existing modelreception_route_area_id, reception_carrier_delivery_type
  • sale.order.rma.wizard · extends an existing modelreception_route_area_id, reception_carrier_delivery_type
  • rma.choose.delivery.carrier · extends an existing modeldelivery_type, route_area_id (Route area)

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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation 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/route-planning.

terminal Installation and usage

No verified information

Installation 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.

info

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.