[RFC] Grouped deliveries for RMAs about rma HOT 14 CLOSED

+1 @florian-dacosta i think this will be great, to group all the lines on the same rma instead to have a single rma by line.

from rma.

This was done on purpose as a design principle, as:

1. It's not usual to return a lot of things at the same time.
2. Even in that case, each product/unit may have a different treatment (repair, refund, change...), so grouping them at that level will mean to need to handle 2 levels of things with a lot of information and duplication in both.
3. You already have the tools to refund/return in batch, just acting over the RMA list view and selecting them together.

from rma.

I don't really agree, I have multiple customers who receive multiple products at once, and have the same treatment.
But anyway, from the design, I don't see an easy way to group multiple RMA in one.

But, the main issue for me, is really about delivery, you can process all products one by one at RMA level, but when delivering, you do not want to send multiple pack to customer if you return/replace multiple products.

So I worked on a POC, in order to group the RMA only on the inventory/logistic level (with procurement group).
The idea is that when a RMA is created, it would get the same procurement group as other draft RMA for a same customer (criterias could be customizable). And so, it will get the same delivery order in case of return/replacement.
It is not perfect, but I think it can be a good workaround for this issue and it would be an optional module.

@pedrobaeza What do you think of such a module?

from rma.

But you already have that in current module. You just need to select all of the RMAs in the list, and click on Action > Return/Refund for doing them grouped. Have you tried?

from rma.

I got your point @pedrobaeza

This was done on purpose as a design principle, as:

1. It's not usual to return a lot of things at the same time.
2. Even in that case, each product/unit may have a different treatment (repair, refund, change...), so grouping them at that level will mean to need to handle 2 levels of things with a lot of information and duplication in both.
3. You already have the tools to refund/return in batch, just acting over the RMA list view and selecting them together.

but when you have to return a sale order with 5 lines or more (in some companies its more usual than you think to have this kind of returns), then you have to do the 5 receipts manually (this case is even worse if you use lots), i think the receipt can be the same for the 5 rma´s of the same order if done at the same time, and keep the isolated treatment you said at rma level to repair refund or replace.

I have to say that this case only happens on rma´s created from the sale order (rma_sale) if you do this from the delivery by return button and check create rma´s on the wizard only one receipt its created for all the rma´s

from rma.

AFAIK, you are able to also do the receipt all together with the same technique.

from rma.

I think it cant be done, and with lots i am sure that it cant be done.

from rma.

I'm talking about generating one single reception picking, that is covered by the module.

from rma.

Let me explain the case, steps to reproduce on runbot:
1 - create sale order with 3 lines and do the delivery
2 - create rma from rma button on sale order
3 - 3 rma are created and 3 diferent receipts are created
spected behaivor
3 rma should be created but only 1 receipt should be created

if its not clear i can make a video, as i said it only happens from rma button on sale order, if you try to do this from return button on delivery 3 rma are created and 1 receip

from rma.

Then that seems a bug. @chienandalu can you take a look?

from rma.

Then that seems a bug. @chienandalu can you take a look?

I'll do. You can assign me

from rma.

But you already have that in current module. You just need to select all of the RMAs in the list, and click on Action > Return/Refund for doing them grouped. Have you tried?

From what I see, the reception is always one picking per RMA.
The action in mass do not allow replacement not confirmation for now also if we really want to manage RMA per group, it is not really user friendly.
The module I may intend to do would be to also to improve the usability.
Maybe a smart button to check all RMA from a same (procurement) group, to be able to do this without always filtering manually.
I was wondering, in this grouping usability module about group RMA automatically at creation for 2 reasons :

1. Ease further mass action on all RMA from group and visibility right after creation
2. Be able to have some kind of consistency in RMA naming. Indeed, grouping at creation allows us to choose a name accordingly to the group. Instead of having RMA001, RMA002, etc...
   I could have RMA001-1, RMA001-2, RMA001-3 with a procurement group named RMA001.
   Then, on inventory side, I could search by origin RMA001 to find the right pickings, etc...

This may seem unnecessary, but it actually is a big usability improvement to be able to search for a unique reference in group of RMA.
Well anyway, I am not sure yet, but this is the kind of thing I would put in this additional grouping module

from rma.

About this issue i want to mention that it only happen with rma_sale when you try to create rma from RMA button on sale order.
The same way if you try to create rma from website (from a sale order with 3 lines as example) the created rmas (one for each line) on backend are created as draft and cant be confirmed on block at the same time, so if you try to confirm each rma one by one a single picking its created for each rma.
Let me know If it is not clear and I will make a more extended explanation.
B/R

from rma.

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

from rma.