OdooWiki OCA HUB

RMA Repair Lot

rma_repair_lot folder_open OCA/rma open_in_new
RMA License: AGPL-3

This module adds lot compatibility in repair orders and RMAs.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Automatically carries the lot or serial number from an RMA over to the repair order created from it, so the repaired item keeps its traceability.

This module is a small bridge between RMA (return merchandise authorization) handling and repair orders. It does not add any new screen, menu or button; it only changes what happens behind the scenes when a repair order is generated from an RMA.

When an RMA is linked to a specific lot or serial number, that same lot is now automatically filled in on the repair order that is created from the RMA. In practice, the user no longer has to re-enter the lot or serial number manually on the repair order.

  • The rule applies only when the RMA actually has a lot or serial number recorded; if there is none, nothing is copied.
  • It affects the rma model and the values used to create the related repair order.
  • It relies on the lot functionality of RMAs and on the RMA-to-repair link provided by the base modules it depends on.

Because the module installs automatically together with its dependencies, users of RMA and repair with lot tracking get this behaviour without any extra configuration. No reports, emails, scheduled jobs or validation rules are added by this module.

Depends on

rma_repairrma_lot
Models and fields (1)
  • rma · 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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

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.