Purchase Representative
by ForgeFlow https://github.com/OCA/purchase-workflow , Odoo Community Association (OCA) https://github.com/OCA/purchase-workflow| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase Management (purchase)
• Inventory Management (stock) • Discuss (mail) |
| Lines of code | 84 |
| Technical Name |
purchase_representative |
| License | AGPL-3 |
| Website | https://github.com/OCA/purchase-workflow |
| Versions | 13.0 14.0 15.0 11.0 |
Purchase Representative
This module adds the field Purchase Representative to Purchase Orders. This field is present in Standard Odoo v12. The user specified will be the contact person for the purchase order.
Additionally, it defaults it to the user doing a procurement to overcome the known flaw of Odoo (until v13) which changes the user in the transaction when using sudo.
Table of contents
Usage
Just set the Purchase Representative in the Purchase Order header. Then when sending the RFQ/PO to the vendor the Purchase Representative will be the contact person (email from and reply to).
Known issues / Roadmap
Migration notes:
- The field user_id is out-of-the-box in v12.
- In v13 the user doing the transaction is respected. Check if emails are also sent to the correct user.
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
- ForgeFlow
Contributors
- Lois Rilo <lois.rilo@forgeflow.com>
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.
This module is part of the OCA/purchase-workflow project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Please log in to comment on this module