===========================================
Return Merchandise Authorization Management
===========================================
..
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:8f36869aece97a0f6af8aa5d76b446e9cf0bd589d914c1f5e12c628e87317021
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
.. |badge1| image:: https://img.shields.io/badge/maturity-Production%2FStable-green.png
:target: https://odoo-community.org/page/development-status
:alt: Production/Stable
.. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png
:target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
:alt: License: AGPL-3
.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Frma-lightgray.png?logo=github
:target: https://github.com/OCA/rma/tree/17.0/rma
:alt: OCA/rma
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
:target: https://translation.odoo-community.org/projects/rma-17-0/rma-17-0-rma
:alt: Translate me on Weblate
.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png
:target: https://runboat.odoo-community.org/builds?repo=OCA/rma&target_branch=17.0
:alt: Try me on Runboat
|badge1| |badge2| |badge3| |badge4| |badge5|
This module allows you to manage `Return Merchandise Authorization
(RMA) <https://en.wikipedia.org/wiki/Return_merchandise_authorization>`__.
RMA documents can be created from scratch, from a delivery order or from
an incoming email. Product receptions and returning delivery operations
of the RMA module are fully integrated with the Receipts and Deliveries
Operations of Odoo inventory core module. It also allows you to generate
refunds in the same way as Odoo generates it. Besides, you have full
integration of the RMA documents in the customer portal.
**Table of contents**
.. contents::
:local:
Configuration
=============
If you want RMAs to be created from incoming emails, you need to:
1. Go to *Settings > General Settings*.
2. Check 'External Email Servers' checkbox under *Discuss* section.
3. Set an 'alias domain' and an incoming server.
4. Go to *RMA > Configuration > RMA Team* and select a team or create a
new one.
5. Go to 'Email' tab and set an 'Email Alias'.
If you want to manually finish RMAs, you need to:
1. Go to *Settings > Inventory*.
2. Set *Finish RMAs manually* checkbox on.
By default, returns to customer are grouped by shipping address,
warehouse and company. If you want to avoid this grouping you can:
1. Go to *Settings > Inventory*.
2. Set *Group RMA returns by customer address and warehouse* checkbox
off.
The users will still be able to group those pickings from the wizard.
Usage
=====
To use this module, you need to:
1. Go to *RMA > Orders* and create a new RMA.
2. Select a partner, an invoice address, select a product (or select a
picking and a move instead), write a quantity, fill the rest of the
form and click on 'confirm' button in the status bar.
3. You will see an smart button labeled 'Receipt'. Click on that button
to see the reception operation form.
4. If everything is right, validate the operation and go back to the RMA
to see it in a 'received' state.
5. Now you are able to generate a refund, generate a delivery order to
return to the customer the same product or another product as a
replacement, split the RMA by extracting a part of the remaining
quantity to another RMA, preview the RMA in the website. All of these
operations can be done by clicking on the buttons in the status bar.
- If you click on 'To Refund' button, a refund will be created, and
it will be accessible via the smart button labeled Refund. The RMA
will be set automatically to 'Refunded' state when the refund is
validated.
- If you click on 'Replace' or 'Return to customer' button instead,
a popup wizard will guide you to create a Delivery order to the
client and this order will be accessible via the smart button
labeled Delivery. The RMA will be set automatically to 'Replaced'
or 'Returned' state when the RMA quantity is equal or lower than
the quantity in done delivery orders linked to it.
6. You can also finish the RMA without further ado. To do so click on
the *Finish* button. A wizard will ask you for the reason from a
selection of preconfigured ones. Be sure to configure them in advance
on *RMA > Configuration > Finalization Reasons*. Once the RMA is
finished, it will be set to that state and the reason will be
registered.
An RMA can also be created from a return of a delivery order:
1. Select a delivery order and click on 'Return' button to create a
return.
2. Check "Create RMAs" checkbox in the returning wizard, select the RMA
stock location and click on 'Return' button.
3. An RMA will be created for each product returned in the previous
step. Every RMA will be in confirmed state and they will be linked to
the returning operation generated previously.
There are Optional RMA Teams that can be used for:
- Organize RMAs in sections.
- Subscribe users to notifications.
- Create RMAs from incoming mail to special aliases (See
configuration section).
To create an RMA Team (RMA Responsible user level required):
1. Go to *RMA > Configuration > RMA Teams*
2. Create a new team and assign a name, a responsible and members.
3. Subscribe users to notifications, that can be of these subtypes:
- RMA draft. When a new RMA is created.
- Notes, Debates, Activities. As in standard Odoo.
4. In the list view, use the cross handle to sort RMA Teams. The top
team will be the default one if no team is set.
Known issues / Roadmap
======================
- As soon as the picking is selected, the user should select the move,
but perhaps stock.move \_rec_name could be improved to better show
what the product of that move is.
- Add RMA reception and/or RMA delivery on several steps - 2 or 3 -
like normal receptions/deliveries. It should be a separate option
inside the warehouse definition.
Bug Tracker
===========
Bugs are tracked on `GitHub Issues <https://github.com/OCA/rma/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 <https://github.com/OCA/rma/issues/new?body=module:%20rma%0Aversion:%2017.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
Do not contact contributors directly about support or help with technical issues.
Credits
=======
Authors
-------
* Tecnativa
Contributors
------------
- `Tecnativa <https://www.tecnativa.com>`__:
- Ernesto Tejeda
- Pedro M. Baeza
- David Vidal
- Víctor Martínez
- Chafique Delli <chafique.delli@akretion.com>
- Giovanni Serra - Ooops <giovanni@ooops404.com>
- `APSL-Nagarro <https://www.apsl.tech>`__:
- Antoni Marroig <amarroig@apsl.net>
- Michael Tietz (MT Software) mtietz@mt-software.de
Maintainers
-----------
This module is maintained by the OCA.
.. image:: https://odoo-community.org/logo.png
:alt: Odoo Community Association
:target: https://odoo-community.org
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.
.. |maintainer-pedrobaeza| image:: https://github.com/pedrobaeza.png?size=40px
:target: https://github.com/pedrobaeza
:alt: pedrobaeza
.. |maintainer-chienandalu| image:: https://github.com/chienandalu.png?size=40px
:target: https://github.com/chienandalu
:alt: chienandalu
Current `maintainers <https://odoo-community.org/page/maintainer-role>`__:
|maintainer-pedrobaeza| |maintainer-chienandalu|
This module is part of the `OCA/rma <https://github.com/OCA/rma/tree/17.0/rma>`_ project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Raw data
{
"_id": null,
"home_page": "https://github.com/OCA/rma",
"name": "odoo-addon-rma",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": null,
"author": "Tecnativa, Odoo Community Association (OCA)",
"author_email": "support@odoo-community.org",
"download_url": null,
"platform": null,
"description": "===========================================\nReturn Merchandise Authorization Management\n===========================================\n\n.. \n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n !! This file is generated by oca-gen-addon-readme !!\n !! changes will be overwritten. !!\n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n !! source digest: sha256:8f36869aece97a0f6af8aa5d76b446e9cf0bd589d914c1f5e12c628e87317021\n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n\n.. |badge1| image:: https://img.shields.io/badge/maturity-Production%2FStable-green.png\n :target: https://odoo-community.org/page/development-status\n :alt: Production/Stable\n.. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png\n :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html\n :alt: License: AGPL-3\n.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Frma-lightgray.png?logo=github\n :target: https://github.com/OCA/rma/tree/17.0/rma\n :alt: OCA/rma\n.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png\n :target: https://translation.odoo-community.org/projects/rma-17-0/rma-17-0-rma\n :alt: Translate me on Weblate\n.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png\n :target: https://runboat.odoo-community.org/builds?repo=OCA/rma&target_branch=17.0\n :alt: Try me on Runboat\n\n|badge1| |badge2| |badge3| |badge4| |badge5|\n\nThis module allows you to manage `Return Merchandise Authorization\n(RMA) <https://en.wikipedia.org/wiki/Return_merchandise_authorization>`__.\nRMA documents can be created from scratch, from a delivery order or from\nan incoming email. Product receptions and returning delivery operations\nof the RMA module are fully integrated with the Receipts and Deliveries\nOperations of Odoo inventory core module. It also allows you to generate\nrefunds in the same way as Odoo generates it. Besides, you have full\nintegration of the RMA documents in the customer portal.\n\n**Table of contents**\n\n.. contents::\n :local:\n\nConfiguration\n=============\n\nIf you want RMAs to be created from incoming emails, you need to:\n\n1. Go to *Settings > General Settings*.\n2. Check 'External Email Servers' checkbox under *Discuss* section.\n3. Set an 'alias domain' and an incoming server.\n4. Go to *RMA > Configuration > RMA Team* and select a team or create a\n new one.\n5. Go to 'Email' tab and set an 'Email Alias'.\n\nIf you want to manually finish RMAs, you need to:\n\n1. Go to *Settings > Inventory*.\n2. Set *Finish RMAs manually* checkbox on.\n\nBy default, returns to customer are grouped by shipping address,\nwarehouse and company. If you want to avoid this grouping you can:\n\n1. Go to *Settings > Inventory*.\n2. Set *Group RMA returns by customer address and warehouse* checkbox\n off.\n\nThe users will still be able to group those pickings from the wizard.\n\nUsage\n=====\n\nTo use this module, you need to:\n\n1. Go to *RMA > Orders* and create a new RMA.\n2. Select a partner, an invoice address, select a product (or select a\n picking and a move instead), write a quantity, fill the rest of the\n form and click on 'confirm' button in the status bar.\n3. You will see an smart button labeled 'Receipt'. Click on that button\n to see the reception operation form.\n4. If everything is right, validate the operation and go back to the RMA\n to see it in a 'received' state.\n5. Now you are able to generate a refund, generate a delivery order to\n return to the customer the same product or another product as a\n replacement, split the RMA by extracting a part of the remaining\n quantity to another RMA, preview the RMA in the website. All of these\n operations can be done by clicking on the buttons in the status bar.\n\n - If you click on 'To Refund' button, a refund will be created, and\n it will be accessible via the smart button labeled Refund. The RMA\n will be set automatically to 'Refunded' state when the refund is\n validated.\n - If you click on 'Replace' or 'Return to customer' button instead,\n a popup wizard will guide you to create a Delivery order to the\n client and this order will be accessible via the smart button\n labeled Delivery. The RMA will be set automatically to 'Replaced'\n or 'Returned' state when the RMA quantity is equal or lower than\n the quantity in done delivery orders linked to it.\n\n6. You can also finish the RMA without further ado. To do so click on\n the *Finish* button. A wizard will ask you for the reason from a\n selection of preconfigured ones. Be sure to configure them in advance\n on *RMA > Configuration > Finalization Reasons*. Once the RMA is\n finished, it will be set to that state and the reason will be\n registered.\n\nAn RMA can also be created from a return of a delivery order:\n\n1. Select a delivery order and click on 'Return' button to create a\n return.\n2. Check \"Create RMAs\" checkbox in the returning wizard, select the RMA\n stock location and click on 'Return' button.\n3. An RMA will be created for each product returned in the previous\n step. Every RMA will be in confirmed state and they will be linked to\n the returning operation generated previously.\n\nThere are Optional RMA Teams that can be used for:\n\n - Organize RMAs in sections.\n - Subscribe users to notifications.\n - Create RMAs from incoming mail to special aliases (See\n configuration section).\n\nTo create an RMA Team (RMA Responsible user level required):\n\n 1. Go to *RMA > Configuration > RMA Teams*\n 2. Create a new team and assign a name, a responsible and members.\n 3. Subscribe users to notifications, that can be of these subtypes:\n\n - RMA draft. When a new RMA is created.\n - Notes, Debates, Activities. As in standard Odoo.\n\n 4. In the list view, use the cross handle to sort RMA Teams. The top\n team will be the default one if no team is set.\n\nKnown issues / Roadmap\n======================\n\n- As soon as the picking is selected, the user should select the move,\n but perhaps stock.move \\_rec_name could be improved to better show\n what the product of that move is.\n- Add RMA reception and/or RMA delivery on several steps - 2 or 3 -\n like normal receptions/deliveries. It should be a separate option\n inside the warehouse definition.\n\nBug Tracker\n===========\n\nBugs are tracked on `GitHub Issues <https://github.com/OCA/rma/issues>`_.\nIn case of trouble, please check there if your issue has already been reported.\nIf you spotted it first, help us to smash it by providing a detailed and welcomed\n`feedback <https://github.com/OCA/rma/issues/new?body=module:%20rma%0Aversion:%2017.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.\n\nDo not contact contributors directly about support or help with technical issues.\n\nCredits\n=======\n\nAuthors\n-------\n\n* Tecnativa\n\nContributors\n------------\n\n- `Tecnativa <https://www.tecnativa.com>`__:\n\n - Ernesto Tejeda\n - Pedro M. Baeza\n - David Vidal\n - V\u00edctor Mart\u00ednez\n\n- Chafique Delli <chafique.delli@akretion.com>\n- Giovanni Serra - Ooops <giovanni@ooops404.com>\n- `APSL-Nagarro <https://www.apsl.tech>`__:\n\n - Antoni Marroig <amarroig@apsl.net>\n\n- Michael Tietz (MT Software) mtietz@mt-software.de\n\nMaintainers\n-----------\n\nThis module is maintained by the OCA.\n\n.. image:: https://odoo-community.org/logo.png\n :alt: Odoo Community Association\n :target: https://odoo-community.org\n\nOCA, or the Odoo Community Association, is a nonprofit organization whose\nmission is to support the collaborative development of Odoo features and\npromote its widespread use.\n\n.. |maintainer-pedrobaeza| image:: https://github.com/pedrobaeza.png?size=40px\n :target: https://github.com/pedrobaeza\n :alt: pedrobaeza\n.. |maintainer-chienandalu| image:: https://github.com/chienandalu.png?size=40px\n :target: https://github.com/chienandalu\n :alt: chienandalu\n\nCurrent `maintainers <https://odoo-community.org/page/maintainer-role>`__:\n\n|maintainer-pedrobaeza| |maintainer-chienandalu| \n\nThis module is part of the `OCA/rma <https://github.com/OCA/rma/tree/17.0/rma>`_ project on GitHub.\n\nYou are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.\n",
"bugtrack_url": null,
"license": "AGPL-3",
"summary": "Return Merchandise Authorization (RMA)",
"version": "17.0.2.0.0.5",
"project_urls": {
"Homepage": "https://github.com/OCA/rma"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "800cd04d33af4be13f068300b1e34f4ff223b69f3bd9ef448815c4fc227a10a7",
"md5": "8d9fc31a248c6a47ac27b4e5483d1458",
"sha256": "a785b28d33f7c720b56f4a46292b88c3bfde372539aed5dbb37764ed7bcc75b6"
},
"downloads": -1,
"filename": "odoo_addon_rma-17.0.2.0.0.5-py3-none-any.whl",
"has_sig": false,
"md5_digest": "8d9fc31a248c6a47ac27b4e5483d1458",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 206874,
"upload_time": "2024-08-21T04:13:01",
"upload_time_iso_8601": "2024-08-21T04:13:01.996945Z",
"url": "https://files.pythonhosted.org/packages/80/0c/d04d33af4be13f068300b1e34f4ff223b69f3bd9ef448815c4fc227a10a7/odoo_addon_rma-17.0.2.0.0.5-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-08-21 04:13:01",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "OCA",
"github_project": "rma",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "odoo-addon-rma"
}
JSON
