Odoo Community Association

Inter Company Module for RMA

Beta License: AGPL-3 OCA/rma Translate me on Weblate Try me on Runboat

Automatically create an Inter Company RMA so that it can be managed independently but still remain linked.

Table of contents

Use Cases / Context

If a company (Company A) sells products but uses dropshipping (Company B), when the customer makes an RMA with Company A, everything must be managed internally in another RMA with Company B.

Configuration

#. Configure the settings specified in purchase_sale_stock_inter_company. #. Edit the Dropship route (or delete it and create a new one) to keep only the rules linked to Company A, and set Company A as the route’s company. #. Create a product and select the Dropshipping route #. [Company A] Set Company B as the supplier in the Purchasing tab

Usage

#. [Company A] Create a sales order and use the previously created product. #. [Company A] Confirm the sales order. #. [Company A] The corresponding purchase order will have been created (confirm it if necessary). #. [Company A] Complete the sales order delivery note. #. [Company A] Create the RMA linked to the sales order. #. [Company B] The sales order RMA will have been created automatically and will be linked. #. The RMA from Company B will be confirmed automatically. #. Reception picking for RMA A will have Transit Location defined as the destination location. #. Reception picking for RMA B will have Transit Location defined as the origin location. #. When validating the reception picking for RMA B, the reception picking for RMA A will be auto-done first. #. When creating a delivery picking (return or replace) in RMA B, it will also be created in RMA A. #. The RMA B delivery picking will have Transit Location as its destination location. #. The RMA A delivery picking will have Transit Location as its origin location. #. When validating the RMA B delivery picking, the RMA A delivery picking will be automatically done. #. If RMA A is canceled, RMA B is automatically canceled. #. If RMA B is canceled, RMA A is automatically canceled. #. If RMA A is confirmed, RMA B is automatically confirmed. #. If RMA B is confirmed, RMA A is automatically confirmed. #. If RMA A is returned (using the return or replace button), RMA B is automatically returned. #. If RMA B is returned (using the return or replace button), RMA A is automatically returned. #. If RMA A is refunded, RMA B is automatically returned. #. If RMA B is refunded, RMA A is automatically returned.

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

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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:

victoralmau

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.