Skip to Content
Role-Based Multi-Level Purchase Order Approval

Role-Based Multi-Level Purchase Order Approval

34.56   34.56
v 19.0 36
Required Apps hr
purchase
Technical Name purchase_approval_kanak
License OPL-1
Also available in version v 12.0 v 13.0 v 14.0 v 15.0 v 16.0 v 17.0 v 18.0
You bought this module and need support? Click here!
Technical Name purchase_approval_kanak
License OPL-1
Also available in version v 12.0 v 13.0 v 14.0 v 15.0 v 16.0 v 17.0 v 18.0 v 19.0
Kanak Infosystems LLP.
Community
Enterprise
Odoo.sh

Purchase Approval Rules

The Purchase Approval Rules module enables structured approval of purchase orders through a predefined workflow involving multiple stakeholders. Approvals are managed based on user roles, ensuring that each purchase request is reviewed by the appropriate personnel. This module simplifies the purchasing process, improves accountability, and helps organizations control and manage approvals.

Purchase Approval Rules

The first step in setting up purchase approval in Odoo is to create Approval Roles. Navigate to Purchase > Configuration > Approval Roles and define the roles according to your organization's hierarchy. Each role represents a level of responsibility for approving purchase orders. For example, you can create roles such as Manager, Department Head, or Finance Officer. Assigning these roles ensures that each employee involved in the purchase process has clearly defined authority levels.

Approval Roles

Once roles are created, the next step is to define Approval Categories. Navigate to Purchase > Configuration > Approval Categories and create categories to classify purchase orders. Each category can represent different types of purchases, such as office supplies, capital expenditures, or high-value items. Linking categories to roles and approval rules ensures that the approval process is tailored according to the type and value of the purchase, providing better control and organization.

Approval Categories

After creating roles and categories, you need to configure Approval Rules to define the workflow logic. Navigate to Purchase > Configuration > Approval Rules and create new rules for different purchase scenarios. Set Price Lower and Upper Limits to specify which role can approve purchases within certain value ranges. Use -1 as the upper limit to indicate unlimited approval authority. Each rule should be linked to an appropriate Approval Category, ensuring that the workflow automatically follows the correct sequence based on the product type and amount.

Approval Rules

To activate the approval workflow, navigate to Purchase > Configuration > Settings. Enable the Purchase Order Approval option and select the applicable approval rule to be applied system-wide. Saving these settings ensures that all future purchase orders follow the defined approval hierarchy, enforcing compliance and accountability throughout the procurement process.

Purchase Settings

After setting up roles and rules, assign approval responsibilities to employees. Navigate to Employees > Employees, select the employee whose approval role you want to define, and open their detailed profile. In the employee's settings page, locate the Approval Role field and select the appropriate role. Save the changes to ensure the employee is included in the purchase order approval workflow according to their assigned responsibilities.

Assign Approval Role to Employee
Assign Approval Role to Employee - Screenshot 2
Assign Approval Role to Employee - Screenshot 3

After creating approval categories, assign them to products to control which approval workflow applies. Navigate to Inventory > Products > Products, select the desired product, and in the General Information tab, choose the relevant Approval Category. This ensures that each product triggers the correct approval rules when a purchase request is created, maintaining consistency and proper oversight.

Assign Approval Category to Product

With approval categories assigned, you can create a purchase request for the product. Navigate to Purchase > Purchase and click Create to open a new request for quotation (RFQ). Select the product with the assigned approval category, fill in supplier and quantity details, and save the request. The purchase request will now follow the defined approval workflow, ensuring that each approver in the sequence is notified and can take action according to their role.

Create Purchase Order for Product

Before sending the purchase request for approval, review the Approval Hierarchy to ensure the correct sequence of approvers is maintained. Navigate to the Approval Hierarchy page in the created RFQ, verify the approvers and their sequence, and click Send for Approval to start the approval workflow. This step ensures that the purchase request will be routed correctly, following the defined rules and categories, and helps maintain accountability at each stage.

Review Approval Hierarchy and Send for Approval

Once the purchase request is sent for approval, the first sequence approver in the hierarchy can review the request. Navigate to Purchase > Requests for Quotation from the employee dashboard. The approver will see the Approve PO and Reject PO buttons, allowing them to take action on the purchase request according to their assigned role and sequence.

Approve PO by First Sequence Employee

After the first sequence approver has acted, the next sequence employee receives the approval buttons if applicable. This screenshot demonstrates a rejection scenario for the second sequence approver. The workflow ensures that each approver can approve or reject the request based on their sequence, maintaining strict adherence to the approval hierarchy and proper organizational control.

Reject PO by Second Sequence Employee

When an approver chooses to reject a purchase order, a popup appears requesting the reason for rejection. This step is essential to provide transparency and accountability. The rejection reason is recorded in the system and visible in the approval history, ensuring that all stakeholders understand why the request was rejected.

Reject Reason Popup

Employees who are not assigned to the approval category of a product will not see the Approve PO or Reject PO or Send For Approval buttons. This ensures that only authorized personnel can take approval actions, preventing unauthorized approvals and maintaining strict adherence to the organization's approval policies.

Employee Without Approval Rights

From the admin perspective, it is crucial to track the approval progress of purchase requests. Navigate to the request for quotation (RFQ) and open the Approval Hierarchy page. Here, admins can view which users have approved or rejected each request, including the sequence order. This provides transparency and helps monitor workflow compliance.

Approval Hierarchy Status for Admin

The Approval History section provides a detailed record of each purchase request, including the dates and times when approvals or rejections were made. It also displays any rejection reasons provided by approvers. This allows admins to audit the workflow, ensure accountability, and review compliance at any stage of the purchase process.

Approval History with Dates and Reasons

Key Features

Enables structured approval workflow for purchase orders based on employee roles.
Allows creation of multiple approval categories and rules to match organizational hierarchy.
Purchase order approvals follow a sequential hierarchy, ensuring compliance and accountability.
Admins can track approval history with dates, users, and rejection reasons for full transparency.
Only employees in the relevant approval category can approve or reject purchase orders, ensuring role-based access.

Free 3 Months Support

Need help or any technical support ?

Kanak Infosystems LLP. will provide free 3 months support for bug fixes, any doubts or queries, installation, configuration support or any types of issues related to this module.

At our company, we take pride in providing exceptional help and technical support to our valued customers.

Our team of dedicated experts is well-versed in the intricacies of the Odoo platform.

Purchase Approval Rules
Version 19.0.1.0 (17th September 2025)
  • Initial Release for the 19.0

Suggested Apps

Our Services

Hire Odoo Developer

Odoo Customization

Odoo Development

Odoo Installation

Odoo Integration

Odoo Resource

Odoo Themes

Odoo Training

Important Notice

All applications are developed within the default, up-to-date Odoo environment, and as such, we cannot guarantee flawless compatibility with third-party apps. While we strive to ensure smooth integration, any conflicts or issues that arise due to third-party applications will require additional support services, which can be provided at an extra cost. Kindly contact our support team for more information or to arrange paid support.

Kanak Infosystems LLP.

Reach out to us at our offices for any inquiries or collaboration.

Delhi Office

Unit no. 1017 & 1026, 11th Floor, Westend Mall,

Janak Puri, New Delhi,

Delhi, India - 110058

Gujarat Office

Unit no. 307, The Landmark, Urjanagar 1, Kudasan,

Gandhinagar, Gujarat, India - 382421

Kanak Infosystems LLP. 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 Kanak Infosystems LLP. 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.

Comment on this module. Please Login