Roadmap - Githubissues

OCA / rma

Odoo for Return Merchandise Authorization (RMA)

GNU Affero General Public License v3.0

78 stars 206 forks source link

Roadmap #127

Closed max3903 closed 2 years ago

max3903 commented 7 years ago

Support service products
Integrate Vendor RMA
Repair/Replace on site
Carrier integration (label)
Support different responsibilities distributions
Instructions
POS integration
Refurbished product (replaced by another product)
Flexible process/steps
RMA Portal
Script for CSR calls
Quality integration / Problems
Reporting

pedrobaeza commented 7 years ago

Very good roadmap. Do you have code already for this?

max3903 commented 7 years ago

@pedrobaeza Nope. These are the ideas collected at the end of my Odoo Experience presentation.

pedrobaeza commented 7 years ago

OK, let's see if there are volunteers for implementing this roadmap.

LoisRForgeFlow commented 7 years ago

We have some implementation regarding some of these points:

Problem tracking and QC integration: https://github.com/OCA/manufacture/pull/199
Refurbishing: https://github.com/OCA/manufacture/pull/225

However we use a different base rma implamentation, you can have a look at: https://github.com/eficent/stock-rma I think we have addressed with it also the following points of your list:

Integrate Vendor RMA
Flexible process/steps

I just wanted to provide these implementations to try to reach some agreement and reduce the parallel works as much as possible.

lukebranch commented 5 years ago

I've had a request for a feature for an RMA flow where the customer may send back a single part/component of an assembled product (in this case a drone), where a single part may have a fault and require a replacement/repair/different product.

Before starting any work on it though, is this a feature that anyone else has already built (or has on a roadmap), or is interested in?

github-actions[bot] commented 2 years ago

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.