[RFC] RMA with no product return from customer about rma

[florian-dacosta]

Yes, that is the idea, with computed (but editable) field akretion@f6014fe#diff-3d6f82bd3aa96a98f1dd5cd6389cb926247243353dda39dc5bbf9924b53c98cbR30)
Indeed, I my cases, the company usually do not ask the customer to return the product, but it does in some rare case. I also think it has to be possible to choose per RMA.
I've changed a bit the description in my previous comment to make it clear

[chienandalu]

Hi, @florian-dacosta

I think you could play with locations in order to achieve these requirements.

I myself received recently a replacement piece of a good without having to send back the broken piece!

In this case, you could make a sort of scrap location hanging from the RMA one. This way, you're scrapping the product from the customer location and then replacing it for another unit in your warehouse, wich is is indeed what is happening.

You can play with locations and rules in order to make more complex flows. In the end, the RMA only minds if its linked return picking is done or not.

[florian-dacosta]

Hello @chienandalu
Thanks for the hint.
Indeed, it could be kind of a workaround, but still, it adds quite a lot of steps, for something useless in that case.
If the product is not really returned, the user won't want to do the whole reception process in order to do a replacement.
He won't understand it and it would be time consuming
Mostly if it is a common case or the most common case in the firm.

I'll check some more the module to see if we could make it optional

[chienandalu]

I'll check some more the module to see if we could make it optional

In that case, I would add a check like "Scrap in customer location" that would do the thing. We should avoid showing the option for return to customer. Maybe an extra scrapped state to manage it?

[florian-dacosta]

@chienandalu

I am not sure I get your idea with the "scrap in customer location" stuff.
But, I dug a bit more into the rma module, and it seems to me we could quite easily manage both cases (process with and without reception from customer).

The idea would be to

• Add a configuration at company level so RMA manages or not the reception step by default.
• Allow to modify the default value directly on RMA to change behavior for specific cases
• At RMA confirmation, if reception step is by-passed, we go directly to received state without creating the reception step.
  Else, we do as today, we go to confirmed state and wait for the reception to be done.
• Display the return to customer only if the reception step is not by passed.
  Here is a quick poc akretion@f6014fe

I'd still need to

• make the company configuration easy.
• Rename at least the "received" state to something that could be ok for both process. (something like "ready" or something)
• make sure there are not other impact and if yet, solve it

It seems quite simple to me and allow us to manage both case without doing a revolution in the module. What do you think?

[pedrobaeza]

I prefer to have the granularity per RMA, not per company (although you can set a default per company).

[pedrobaeza]

Great then. I think that can be. @chienandalu your last call.

[chienandalu]

Ok, let's see that in an PR 👍

[florian-dacosta]

Nice, I'll do a complete PR in the next few days, thanks for the feedback

[chienandalu]

Any news @florian-dacosta ?

[florian-dacosta]

Well, I was a bit optimist in my previsions! I still plan to do it, but it is not yet very urgent and I was kind of waiting the 14.0 PR to be cleaned/ready before proposing a PR on top of it.

[github-actions]

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.