-
-
Notifications
You must be signed in to change notification settings - Fork 225
[18.0][ADD] add rma_batch #499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sbejaoui
wants to merge
8
commits into
OCA:18.0
Choose a base branch
from
acsone:18.0-rma_batch-sbj
base: 18.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cc77f26 to
e073a5d
Compare
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
e073a5d to
9292345
Compare
marielejeune
approved these changes
Nov 3, 2025
Contributor
marielejeune
left a comment
There was a problem hiding this 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.
marielejeune
approved these changes
Nov 5, 2025
9b433b1 to
c2031f7
Compare
[IMP] rma_batch: set state as readonly in the rma_ids
…a batch to RMA lines
[IMP] Adds location_id to RMA Batch and propagate location_id from rm…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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