OCA/rma · 18.0
Rma Batch
rma_batch
Rma Batch
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.
Table of contents
Use Cases / Context
In many after-sales operations, customers often return multiple products at once, sometimes coming from different sales orders or deliveries.
In the base addon RMA, each product return creates a separate RMA
record.
When a customer sends back several items together, this leads to
multiple independent RMAs that must be processed, confirmed, and tracked
one by one.
This fragmented approach makes it difficult to manage and validate grouped returns, especially for companies handling large volumes of RMAs.
Usage
Creating 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.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Authors
- ACSONE SA/NV
Contributors
- Souheil Bejaoui <souheil.bejaoui@acsone.eu>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/rma project on GitHub.
You are welcome to contribute. To learn how please visit <https://odoo-community.org/page/Contribute>.





