# Return Merchandise Authorization Management - Link with MRP Kits

This module enables RMAs for kits, wich isn’t compatible with the base modules. In the backend side, we can return separate component while in the frontend side, customers can return the whole kit and the proper RMAs will be generated.

Table of contents

- Usage
- Known issues / Roadmap
- Bug Tracker
- Credits
  - Authors
  - Contributors
  - Maintainers

## Usage

To use this module, you need to:

1. Make a a sale order with a kit on it and deliver its components.
2. Go to the portal view for the order and launch the RMA wizard.
3. You’ll see a line for the kit.
4. There will be a limit of kits to return that should much the number of kits delivered.
5. Once you validate the wizard with the number of kits to deliver, you’ll have as many RMAs as components those kits have with the proper quantities for each one.
6. If you refund the components, the kit in the sale line will be used as the reference.

## Known issues / Roadmap

We compute the kits from the original demanded quantity in the sale order. If this quantity was to change, we could loose the right components per kit reference. So this should be very present. Also, v12 has a very poor support for delivered quantities, that is very improved in v13 with the introduction of the link to the BoM line in the stock moves. That approach could lead to errors as well, as the BoM line could change in the future loosing again the original components per kit reference. Anyway, is to be considered in that version to use the same rules so they fail for the same reasons.

Some extra features would be nice to have:

- Add actions constraints to disallow actions on single components.
- Show kit components in the portal wizard.
- Allow to make an RMA directly from a kit product.

## Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

## Credits

### Authors

- Tecnativa

### Contributors

- Tecnativa:
  - David Vidal
- Michael Tietz (MT Software) <mtietz@mt-software.de>

### Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainer:

This module is part of the OCA/rma project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.