The goal of this module is to introduce an RMA Batch — a container that groups several RMAs belonging to the same return event. It allows users to manage all related RMAs together, ensuring that shared information (customer, responsible, team, tags, date) stays synchronized and that batch actions apply consistently across all linked RMAs.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Group several RMAs from the same return event into a single RMA Batch, so shared data (customer, responsible, team, tags, operation, location) stays synchronized and batch actions apply to all linked RMAs at once.
This module adds a new "RMA Batch" container that groups several RMAs belonging to the same return event. Users can create batches from the new Batches menu (under the RMA menu) or automatically when a return with more than one RMA is created from the return picking wizard.
On the batch form, users set the customer, shipping and invoice addresses, requested operation, default location, responsible, tags and company. While the batch is in Draft, these values are automatically copied to every linked RMA, and the team is derived from the responsible. A status bar drives the workflow with buttons: Mark as Ready, Confirm, Cancel and Set to Draft; confirming or cancelling the batch also confirms or cancels all its RMAs. A smart button shows the number of RMAs and opens the filtered list.
Business rules: all RMAs in a batch must belong to the same customer (otherwise a validation error is raised), and a batch cannot be deleted if it contains RMAs that are not in draft state. Batch references are generated automatically from a sequence (prefix RB). Access rules limit users to their own batches, while managers see all, and multi-company rules apply.
Depends on
Required by other modules
Models and fields (3)
- rma · extends an existing modeltag_ids, user_id, batch_id (RMA Batch), partner_id, operation_id
- rma.batch · new modeldate, name (Reference), state (Status), rma_ids (RMA), tag_ids (Tags), team_id (RMA team), user_id (Responsible), count_rma, company_id (Company), partner_id (Customer), location_id, operation_id (Requested operation), partner_invoice_id (Invoice Address), partner_shipping_id (Shipping Address)
- stock.return.picking · 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
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0Creating an RMA Batch Manually
- Go to Returns: RMA Batches.
- Click New to create a batch.
- Fill in general information such as:
- Add one or more RMAs in the RMA tab.
Batch States
- Draft: The batch is being prepared; RMAs can be added or edited.
- Ready: All information is complete and the batch is ready for confirmation.
- Confirmed: The batch and all contained RMAs are confirmed together.
- Cancelled: The batch and its RMAs are cancelled.
Automatic Batch Creation from Stock Returns
When performing a Return Picking with Create RMA = True:
- If the return involves only one product, a single RMA is created (no batch).
- If multiple RMAs are created, the system automatically groups them into a new RMA Batch in the Confirmed state.
You can view the created batch under Returns: RMA Batches or access it from any linked RMA.
No verified information in OCA: Installation, Configuration.
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.
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.