Skip to content

[18.0][ADD] add rma_batch#499

Merged
OCA-git-bot merged 8 commits intoOCA:18.0from
acsone:18.0-rma_batch-sbj
Feb 10, 2026
Merged

[18.0][ADD] add rma_batch#499
OCA-git-bot merged 8 commits intoOCA:18.0from
acsone:18.0-rma_batch-sbj

Conversation

@sbejaoui
Copy link
Copy Markdown
Contributor

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.

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.

refs: #473

@sbejaoui sbejaoui force-pushed the 18.0-rma_batch-sbj branch 2 times, most recently from cc77f26 to e073a5d Compare October 31, 2025 11:15
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.

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.

refs: OCA#473
Copy link
Copy Markdown
Contributor

@marielejeune marielejeune left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Nice new feature.

Code review only. I plan to do a functional review soon.

@OCA-git-bot
Copy link
Copy Markdown
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@yvaucher
Copy link
Copy Markdown
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Copy Markdown
Contributor

On my way to merge this fine PR!
Prepared branch 18.0-ocabot-merge-pr-499-by-yvaucher-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit ff545fa into OCA:18.0 Feb 10, 2026
7 checks passed
@OCA-git-bot
Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at a35e6af. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants