$ 51.86
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Approvals (approvals)
• CRM (crm) • Contacts (contacts) • Documents (documents) • Employees (hr) • Purchase (purchase) • Discuss (mail) • Calendar (calendar) • Invoicing (account) • Studio (web_studio) |
| Lines of code | 1017 |
| Technical Name |
st_customer_vendor_approval |
| Website | https://www.surekhatech.com |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Approvals (approvals)
• CRM (crm) • Contacts (contacts) • Documents (documents) • Employees (hr) • Purchase (purchase) • Discuss (mail) • Calendar (calendar) • Invoicing (account) • Studio (web_studio) |
| Lines of code | 1017 |
| Technical Name |
st_customer_vendor_approval |
| Website | https://www.surekhatech.com |
| Versions | 18.0 19.0 |
Customer & Vendor Approval
Prevent uncontrolled creation of customers and vendors in Odoo. The Customer & Vendor Approval app introduces a structured approval workflow that ensures every new partner goes through a defined review process before being added to the system.
Compatible with Odoo 18 & 19 Enterprise. Direct partner creation from Contacts, Sales Orders, Purchase Orders, CRM and Invoices is restricted : all new registrations must go through an approval request.
Key Features of Customer & Vendor Approval
1
2
3
4
5
6
7
8
Customer & Vendor Approval
The Customer & Vendor Approval app ensures that all new business partners entering your Odoo system go through a controlled review process. Instead of allowing anyone to directly create a customer or vendor, every registration is submitted as an approval request : complete with contact details, supporting documents, and a verification checklist.
Once submitted, the request flows through your configured approval chain. On final approval, the contact is automatically created in the system with all provided details, and the requester is notified instantly. This ensures data quality, compliance, and a clear audit trail for every new partner added.
Approval Workflow
Step 1 : Create New Approval Types for Customer or Vendor(Admin)
Before any request can be submitted, the Admin must set up the approval types. Go to Approvals -> Configuration -> Approval Types and create a new approval type:
- Set Name : e.g. "Customer Approval" or "Vendor Approval"
- Select Approval Type : Customer Registration or Vendor Registration
- Choose Approval Routing : Employee's Manager or Specific Approvers
- Assign Approvers : one or multiple users in sequence
- Optionally assign a Contact Checklist template for this approval type
- Set Overdue Reminder Days : auto-notify pending approvers after N days
For Requester To Create New Approval Request
Once the approval type is configured, any user can submit a registration request. Navigate to Dashboard -> Customer/Vendor Registration Form -> New Request to open the request form.
Step 2 : Submit a Customer or Vendor Registration Request
Instead of creating a contact directly, the user fills in a Registration Request form with all required partner details:
- Name, Address, Email, Phone, Website
- Is Company : individual or company type
- Child contacts : invoice address, delivery address, contact persons
- Contact Checklist : verification worksheet must be completed before submission
- Supporting attachments : documents uploaded to the request
Step 3 : Approval Chain
Once submitted, the request flows through the configured approval chain:
- An activity is automatically created for the first pending approver
- Approvers can view the full request but cannot edit partner details
- Each approver Approves or Refuses with a mandatory reason on refusal
- On approval, the next approver in sequence is notified automatically
- Refusal reason is logged in the chatter for full audit trail
Step 4 : Contact Created on Approval
When the final approver approves the request:
- The partner record is automatically created with all provided details
- Customer rank or Supplier rank is set based on the request type
- Child contacts (invoice, delivery, contact persons) are created under the parent
- A Contact smart button appears on the request to open the created partner
- The requester is notified by email that the contact has been created
- Attachments are moved to the configured document workspace automatically
Partner Creation Restriction
Direct contact creation is blocked : approvals only
Once the module is installed, users cannot directly create a Customer or Vendor from the Contacts module, Sales Orders, Purchase Orders, CRM or Invoices. All partner registrations must go through the approval workflow. Other modules such as HR and internal system operations are unaffected and continue to work normally.
Contact Checklist
Worksheet Checklist Integration
Ensure data completeness before every submission with a configurable checklist:
- Admin creates separate checklist templates for Customer and Vendor registrations
- Each approval category can have its own specific checklist assigned
- Checklist includes verification points such as Valid Tax ID, Email Confirmed, Website Verified
- The requester must fill the checklist before submitting : empty checklists are blocked
- Approvers can view the checklist but cannot edit it after submission
Screenshots
Approval Request Form : Partner Details Tab
Approval Category Configuration
Checklist Template Configuration
Refusal Reason Wizard
Document Workspace : Customer & Vendor Folders
Approved Mail Sent to Requester
Configuration
1. Approval Type Setup (Admin)
Go to Approvals -> Configuration -> Approval Types and create separate approval types for Customer Registration and Vendor Registration. For each type you can:
- Set approval routing : Employee's Manager or Specific Approvers
- Assign a Contact Checklist template specific to that approval type
- Configure Overdue Reminder days to auto-notify pending approvers
2. Contact Creation Rights for Approvers
When an approval request is approved, the system automatically creates the contact. The approver user must have write access to Contacts (res.partner) for this to succeed. Ensure approvers are assigned at minimum the Contact / Read & Write access right under Settings -> Users -> Access Rights. Without this, the contact creation step will raise an access error.
3. Document Workspace (Optional)
To store approval request attachments in a centralised document folder, go to Settings -> Documents and:
- Enable the Contact Documents toggle
- Set the Customer Document Workspace folder
- Set the Vendor Document Workspace folder
After approval, all attachments are automatically moved into a per-contact subfolder (named after the created contact) inside the respective Customer or Vendor workspace.
4. Checklist Template Setup (Admin)
Go to Approvals -> Configuration -> Checklist Configuration and create worksheet templates for Customer and/or Vendor registration:
- Set Contact Tag to Customer Checklist or Vendor Checklist
- Mark one template as Default per type, or assign it directly to an approval type
- Add verification fields such as checkboxes for Valid Tax ID, Email Verified, Website Confirmed
Access Rights & Roles
The module follows the standard Odoo Approvals group hierarchy. The table below summarises what each role can do in Odoo 18 and 19 Enterprise.
| Capability | Normal User | Officer | Admin |
|---|---|---|---|
| Configuration Menu | No | No | Yes |
| View All Requests | Own only | Everyone's | Everyone's |
| Submit New Request | Yes | Yes | Yes |
| Approve / Refuse | If assigned | If assigned | If assigned (v18) |
| Approve own request | Yes | Yes | Yes |
| Force Approval | Blocked | Blocked | Blocked |
| Manage Checklist Templates | No | No | Yes |
| Normal user as self-approver | Blocked (v19) | Yes | Yes |
Can Approve Only if the user is explicitly assigned as an approver in the approval chain.
Our Odoo Services
Odoo Implementation
Odoo Support & Maintenance
Odoo Customization
Odoo Migration
Help & Support
Get Immediate support for any of your query.
You will get 90 days free support for any doubt, queries, and bug fixing (not including data recovery).
Please log in to comment on this module