Feature Availability
Vtiger Editions: One Pilot | One Growth | One Professional | One Enterprise | One AI
Introduction
Approvals for Inventory ensure that transactions involving products, pricing, and financial commitments are reviewed and authorized before being finalized. This helps your business maintain pricing control, prevent revenue leakage, and enforce compliance with internal policies.
You can configure approvals for key Inventory modules, including Quotes, Sales Orders, Purchase Orders, and Invoices. When a predefined condition is met (for example, a discount exceeds a threshold), the system automatically sends a record to the designated approver for approval.
Approval Process for Inventory
The following are the steps involved in approving Inventory records:
- An approval rule is configured in the required Inventory module.
- Conditions are defined (for example, discount > 10% and total value > $50,000).
- An approver (a manager or a role-based user) is assigned.
- When the condition is met, the record is sent for approval.
- The approver can approve or reject the record. the record.
- Once approved, the record proceeds to the next stage of the sales or procurement cycle.
Key Features
The key features of Approvals for Inventory are:
- Condition-based approval rules
- Role-based or user-based approver assignment
- Automatic record locking during approval
- Approval history tracking for audit purposes
- Multi-level approval configuration (if required)
Benefits
The benefits of using approvals in the inventory process are:
- Enforcing discount and pricing policies
- Preventing unauthorized changes to financial documents
- Maintaining audit trails for compliance
- Reducing financial risks
- Improving accountability across sales and procurement teams
In this article, you will learn about:
- Approving inventory records
- Approval examples for different Inventory modules
Key Terminology
| Key Term | Definition |
| Approval Rule | A predefined condition that determines when an Inventory record (Quote, Sales Order, Purchase Order, Invoice) must be reviewed before proceeding. |
| Approval Process | The workflow is triggered when an approval rule condition is met, and the record is sent to a designated approver. |
| Approver | The user (or role-based user) is authorized to review and approve or reject the record. |
| Approval Status | The current state of the record in the approval cycle (for example, Pending, Approved, Rejected). |
| Condition Criteria | Logical rules that are defined in the approval configuration (for example, Discount > 10%, Total > ₹5,00,000). |
| Record Locking | Automatic restriction that prevents editing or further processing of a record while it is pending approval. |
| Role-based Approval | Approval is assigned to a CRM role (for example, Sales Manager) rather than a specific user. |
| Rejection Workflow | The process followed when a record is rejected, allowing edits and resubmission if required. |
Approvals for the Inventory Modules
Quotes Approvals
The following table lists the Quotes module fields that may require Approval:
| Field | Why Approval May Be Required | Example Scenario |
| Discount (%) | High discounts can impact profit margins. | A sales rep applies a 20% discount, even though company policy allows only a 10% discount. |
| Discount Amount | Prevents unauthorized price reductions. | Discount amount exceeds ₹50,000. |
| Manual Price Override (List Price change) | Ensures product pricing consistency. | Sales rep changes product price below standard rate. |
| Grand Total | Large quote values require managerial visibility. | Quote value exceeds ₹10,00,000. |
| Payment Terms | Prevents risky payment agreements. | You offer 120-day payment terms to a customer. |
| Special Pricing Notes / Terms | Ensures special commitments are approved. | Custom pricing agreement for a strategic customer. |
Example Scenario: As a sales representative, you create a Quote with a 15% discount for a customer. The company policy allows only up to 10% without manager approval.
Approval Flow:
- Condition: Discount > 10%
- Approver: Sales Manager
- Action: Quote is locked until approved
- Outcome: Once approved, the Quote can be shared with the customer
This ensures pricing discipline and margin protection.
Sales Orders Approval
The following table lists the Sales Order module fields that may require Approval:
| Field | Why Approval May Be Required | Example Scenario |
| Discount (%) | Protects margins after quote conversion. | Sales rep increases discount during order finalization. |
| Grand Total | Large orders may require management approval. | Order value exceeds ₹20,00,000. |
| Delivery Date | Prevents unrealistic delivery commitments. | Sales rep promises delivery earlier than production capacity allows. |
| Payment Terms | Ensures finance approval for extended credit. | Customer requests a 90-day payment cycle. |
| Product Quantity | Prevents committing stock beyond availability. | You place an order for 5,000 units when inventory is limited. |
Example Scenario: A Sales Order exceeds ₹10,00,000 in total value.
Approval Flow:
- Condition: Grand Total > ₹10,00,000
- Approver: Regional Sales Head
- Action: Order cannot proceed to fulfillment until approved
- Outcome: Approved order moves to the delivery/fulfillment stage
This prevents large financial commitments without visibility into management.
Purchase Orders Approval
The following table lists the Purchase Order module fields that may require Approval:
| Field | Why Approval May Be Required | Example Scenario |
| Purchase Amount / Grand Total | Controls procurement spending. | PO value exceeds ₹5,00,000. |
| Vendor Selection | Ensures procurement from approved vendors. | Purchase from a new or unverified vendor. |
| Product Price | Prevents overpaying vendors. | The vendor charges a price higher than the agreed-upon contract price. |
| Quantity Ordered | Ensures purchase aligns with demand forecasts. | Procurement team orders excess stock. |
| Delivery Schedule | Prevents unrealistic vendor commitments. | Early delivery is requested and may incur an extra cost. |
Example Scenario: A Purchase Order is created for a new vendor or exceeds the approved procurement budget.
Approval Flow:
- Condition: PO Amount > ₹5,00,000
- Approver: Procurement Manager or Finance Head
- Action: PO remains pending until approved
- Outcome: Approved PO is sent to the vendor
This controls procurement spending and avoids unauthorized purchases.
Invoices Approval
The following table lists the Invoices module fields that may require Approval:
| Field | Why Approval May Be Required | Example Scenario |
| Manual Price Adjustments | Prevents unauthorized billing changes. | The invoice price differs from the sales order price. |
| Discount (%) | Ensures discounts are approved before billing. | Invoice discount added after order confirmation. |
| Tax Adjustments | Prevents incorrect tax application. | GST rate modified manually. |
| Grand Total | Ensures high-value invoices are verified. | Invoice value exceeds ₹15,00,000. |
| Write-offs / Adjustments | Protects revenue recognition. | Partial amount written off before payment. |
Example Scenario: An Invoice is generated with special pricing adjustments or tax modifications.
Approval Flow:
- Condition: Manual price override applied
- Approver: Finance Manager
- Action: Invoice cannot be finalized or sent to the customer
- Outcome: After approval, the invoice is officially issued
This ensures financial accuracy and tax compliance.
References