| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Sales (sale_management) • Invoicing (account) • Discuss (mail) |
| Lines of code | 191 |
| Technical Name |
eg_customer_supplier_approve |
| License | OPL-1 |
| Website | http://www.inkerp.com |
| Versions | 16.0 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Sales (sale_management) • Invoicing (account) • Discuss (mail) |
| Lines of code | 191 |
| Technical Name |
eg_customer_supplier_approve |
| License | OPL-1 |
| Website | http://www.inkerp.com |
| Versions | 16.0 17.0 18.0 19.0 |
Our Most Suggested Products
Customer and Vendor approval
The Customer and Vendor Approval module for Odoo streamlines the process of managing customer and vendor validation. It ensures that all customers and vendors go through a structured approval workflow, enabling only approved entities to participate in sales or purchase processes.
Features
Customer Approval Process
The module provides a clear approval flow for customer registration. When a sales manager creates a new customer, the system automatically sets the customerâs status as "New" until an authorized user approves it.
Vendor Approval Process
Similar to customer approval, vendors must also be validated before being allowed to participate in purchasing activities. The system restricts the visibility of vendors to only those who have passed the approval process, ensuring that only trusted and vetted vendors can be selected for RFQs (Requests for Quotation) and purchase orders.
State-Based Validation
Both customers and vendors progress through various stages New, To Approve, and Approved. This state-based system allows managers to easily track and manage the approval status of each entity.
Screenshot
1.) Users View
Users with the appropriate access rights can approve or reject customers and vendors by toggling the "Customer Approval" or "Vendor Approval" Boolean field.
Navigation : Settings → Users & Companies → Users
2.) Customer Form View
A new customer can be created by the sales manager, generating a unique customer ID. However, the customer remains in the "New" state until approval.
Navigation : Sales → Orders → Customers
3.) Customers View for Customer Validation
Managers can view a list of customers and their validation states. They can change the customer's status from "To Approve" to "Approved" once the customer meets the necessary criteria.
Navigation : Sales → Customer Validation → New Customers
4.) Approved Customer Form View
Once the customer is approved, the manager can confirm their approval status. Approved customers are then eligible for use in sales orders.
Navigation : Sales → Customer Validation → Approved Customers
5.) Customers Kanban View (New Customers)
In this Kanban view, only new customers awaiting approval are displayed. This helps managers focus on customers in the initial stages of the approval process.
Navigation : Sales → Customer Validation → New Customers
6.) Customers View with "Customer to Approve" Option
This view allows managers to filter and view customers who are still pending approval, ensuring only validated customers progress in sales workflows.
Navigation : Sales → Customer Validation → Customer to Approve
7.) Customers View with "Approved Customers" Option
In this filtered view, only customers who have been approved and are ready to participate in sales activities will be visible.
Navigation : Sales → Customer Validation → Approved Customers
8.) Quotations View
While creating a new quotation, only approved customers are shown in the customer list. This ensures that only validated customers are involved in sales transactions.
Navigation : Sales → Orders → Quotations → New
9.) Vendors Form View
Similar to the customer approval process, new vendors are created with an approval status of "New." They remain in this state until authorized users approve them, making them eligible for use in purchase orders.
Navigation : Purchase → Orders → Vendors → Vendor Validation
10.) Vendors View
Authorized users can approve or reject vendors from the vendor validation menu. This step ensures that only trusted vendors are allowed in the procurement process.
Navigation : Purchase → Orders → Vendors → Vendor Validation
11.) Vendors Kanban View (New Vendors)
This Kanban view displays only new vendors awaiting approval, helping users manage and approve vendor requests efficiently.
Navigation : Purchase → Orders → Vendors → Vendor Validation → New Vendors
12.) Vendors View with "Vendors to Approve" Option
This view shows only vendors who are awaiting approval, allowing the user to manage pending vendor validation.
Navigation : Purchase → Orders → Vendors → Vendor Validation → Vendors to Approve
13.) Vendors View with "Approved Vendors" Option
Only vendors who have been approved will be shown in this view, making them eligible for use in RFQs and purchase orders.
Navigation : Purchase → Orders → Vendors → Vendor Validation → Approved Vendors
14.) RFQ Form View
When creating a new RFQ, only approved vendors appear in the vendor selection list, ensuring that only validated vendors are considered for procurement activities.
Navigation : Purchase → Orders → Requests for Quotation → New
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