| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 160 |
| Technical Name |
eg_po_dynamic_approve |
| License | OPL-1 |
| Website | https://www.inkerp.com/ |
| Versions | 16.0 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 | 160 |
| Technical Name |
eg_po_dynamic_approve |
| License | OPL-1 |
| Website | https://www.inkerp.com/ |
| Versions | 16.0 17.0 18.0 19.0 |
Our Most Suggested Products
Dynamic Approve for PO
The Dynamic Purchase Order Approval module enhances procurement control by enabling flexible and structured approval workflows within Odoo. It allows organizations to define purchase order approval teams and assign approval responsibilities dynamically based on predefined rules or business needs.
Features
Screenshots
Support
Service
Features
Dynamic Purchase Order Approval Teams
This feature allows organizations to create dedicated Purchase Order approval teams with specific users assigned as members. Each team is responsible for reviewing and approving purchase orders, ensuring that approvals are handled by the right personnel.
Access Restriction & Validation Mechanism
The module enforces strict access control by restricting non-team members from approving or confirming purchase orders. If an unauthorized user attempts to perform these actions, the system immediately generates an error notification.
Screenshot
1.) Purchase Team Configuration
A dedicated menu allows purchase managers to create and manage Purchase Order approval teams. From here, users can define team structures and assign members responsible for handling approvals, ensuring a well-organized approval framework.
2.) RFQ Team Selection
While creating or reviewing a Request for Quotation, managers can assign the appropriate approval team. This ensures the RFQ is routed through the correct approval path, aligning with internal procurement policies.
3.) Unauthorized Action Warning
Attempting to confirm or approve a purchase order without being part of the assigned team triggers a clear error notification. This helps prevent unauthorized actions and reinforces role-based access control.
4.) Approval Restriction Notification
When a user without proper permissions tries to approve an order, the system blocks the action and provides immediate feedback.
5.) Team-Based Approval Action
Authorized team members gain access to an approval route where they can review and approve RFQs. This provides a streamlined interface for decision-makers to efficiently process purchase requests.
6.) Purchase Order Confirmation
Once the approval process is completed by the designated team, authorized users can proceed with confirming the purchase order.
User Guide
Teams
team@inkerp.com
Suggested Products
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