| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 741 |
| Technical Name |
wc_purchase_approval |
| License | OPL-1 |
| Website | https://www.wicoders.com |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 741 |
| Technical Name |
wc_purchase_approval |
| License | OPL-1 |
| Website | https://www.wicoders.com |
| Versions | 17.0 18.0 19.0 |
Community
Enterprise
Multi Approval Purchase Order
Explore this module
Overview
A Multi-Approval Purchase Order is a process where a purchase order requires approval from multiple stakeholders before being finalized.
Features
Multiple Approval Levels:
Notifies approvers about pending tasks, ensuring timely approvals and avoiding delays in the procurement process.
Real-Time Notifications:
Automatically syncs product and customer data between the POS and backend systems. Any updates to product details or customer information are instantly reflected across all platforms, ensuring consistency and real-time updates.
Threshold-based Approvals:
Allows different approval levels based on the purchase amount or other criteria, ensuring proper scrutiny for high-value purchases.
Screenshots
01
Install module/application.
02
Go To Purchase Configuration And Enable Minimum approval amount based on the ratio of untaxed to total amount .
03
Go to Approval Setting Menu.
04
you can set the minimum quantity or set criteria for the selected vendor and There are two types of approval processes: User-based and Group-based. Select the 'User' approval process and define the individual responsible for approving the purchase.
05
The user can click the CONFIRM ORDER button in the RFQ for the If the approval is based on 'Total', the approval will be triggered by the total amount; if based on 'Untaxed Amount', the approval will be determined by that value instead. and sending mail to configure second approver.
06
The next approval level will be automatically set under the 'Approval Info' tab.
07
The second approver can click on the 'Approve' button to confirm the RFQ approval.
08
After the RFQ is approved by the second approver, the confirmed purchase order can be viewed, along with the approvers' details in the 'Approval Info' tab and Notification for Approved Purchase Order Confirmation.
10
The approver has the option to click the 'Reject' button to decline the RFQ.
11
After clicking the 'Reject' button, the approver is required to provide a reason for rejection in the wizard.
12
After the RFQ is rejected by the approver, it enters the 'Reject' stage, and additional approvals are no longer needed. Rejection details can be viewed under the 'Approval Info' tab.
Get Help From Me!
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module