Kaizen 230 - Smart Discount-Based Quote Approvals Using CRM Functions and Approval Process

Kaizen 230 - Smart Discount-Based Quote Approvals Using CRM Functions and Approval Process


Hello everyone!
Welcome back to the Kaizen series!
Discount approvals are a standard part of sales governance.
Most organizations need something like this:

Discount %
Required Action
< 10%
Auto-approve
10–19.99%
Sales Manager approval
≥ 20%
VP Sales approval

Zoho CRM already includes a powerful Approval Process feature capable of routing records, locking them, notifying approvers, and maintaining audit history.
So the natural question is "Isn’t the native Approval Process enough?". Often, yes. But when the discount logic depends on accurate percentage calculation across line items and header adjustments, we need a small architectural enhancement.

This Kaizen combines Functions(for decisions), Workflow Rules(for triggers), Approval Process(for governance), and Reporting Hierarchy(for routing) into a clean, scalable solution.

Understanding the native Approval Process

Before adding anything custom, it’s important to recognize what the Approval Process already does extremely well.
  1. Evaluates criteria based on field values
  2. Automatically submits records
  3. Locks records during review
  4. Routes to users, roles, or hierarchy levels
  5. Maintains approval history
  6. Sends notifications
It is a powerful governance engine.
However, it evaluates existing values and does not calculate new ones. That distinction matters in discount scenarios.

The missing piece: Reliable discount percentage

In Quotes:
  1. Discounts may be applied at line-item level
  2. Discounts may be applied at header level
  3. Grand Total reflects cumulative adjustments

There is no guaranteed native field that consistently represents
True Discount % = (Sub_Total - Grand_Total) / Sub_Total * 100

If approval rules rely directly on partial fields(like “Discount”), they may misrepresent the effective discount.

To ensure accuracy, we introduce a Function to calculate and store a reliable Discount Percentage.
We are not replacing the Approval Process, but preparing accurate data for it.

Here is the architectural flow with each component having a distinct responsibility. This makes the system sustainable.
Quote Saved --> Workflow triggers Function --> Function calculates Discount % --> Function sets Approval_Status --> Approval Process evaluates status --> Record submitted and locked

Let's go over this one step at a time.

Step 1: Create Custom Fields(Quotes Module)

Field
Type
Purpose
Discount_Percentage
Percent
Stores calculated discount
Approval_Status
Picklist
Controls approval trigger. Values:
  1. Auto Approved
  2. Pending Manager Approval
  3. Pending VP Approval
  4. Approved
  5. Rejected
Approval_LevelSingle LineDisplays routing level

Step 2: Write the CRM Function(Decision Layer)

This function calculates the effective discount and determines the approval level. This function becomes the decision engine.
void automation.Set_Quote_Approval_Level(String id)
{
quoteId = id.toLong();
quoteDetails = zoho.crm.getRecordById("Quotes",quoteId);
if(quoteDetails != null)
{
subTotal = ifnull(quoteDetails.get("Sub_Total"),0).toDecimal();
grandTotal = ifnull(quoteDetails.get("Grand_Total"),0).toDecimal();
discount = subTotal - grandTotal;
discountPercentage = 0.0;
if(subTotal > 0)
{
discountPercentage = discount / subTotal * 100;
}
approvalStatus = "";
approvalLevel = "";
if(discountPercentage < 10)
{
approvalStatus = "Auto Approved";
approvalLevel = "None - Auto Approved";
}
else if(discountPercentage < 20)
{
approvalStatus = "Pending Manager Approval";
approvalLevel = "Sales Manager";
}
else
{
approvalStatus = "Pending VP Approval";
approvalLevel = "VP Sales";
}
updateMap = Map();
updateMap.put("Discount_Percentage",discountPercentage.round(2));
updateMap.put("Approval_Status",approvalStatus);
updateMap.put("Approval_Level",approvalLevel);
updateResponse = zoho.crm.updateRecord("Quotes",quoteId,updateMap);
}
}

Step 3: Workflow(Trigger Layer)

Every time a quote is saved, we want the discount to be evaluated automatically.
Create the following Workflow Rule:
Module: Quotes
Trigger: On Create or Edit
Action: Execute Function
Map the Quote ID with the "id" argument in the function.


Step 4: Approval Process(Governance Layer)

Rule 1 - Manager Approval when Discount% is 10 to 19.99
Approval_Status = "Pending Manager Approval" --> Route to Sales Manager(via hierarchy)

Rule 2 - VP Sales Approval when Discount% >= 20
Approval_Status = "Pending VP Approval" --> Route to VP Sales(via hierarchy)
When this process is triggered, CRM:
  1. Submits the record for approval
  2. Locks it
  3. Sends notification
  4. Tracks approval history

The outcome


Why is this layered approach strong?

This design works well because each component in the system has a clearly defined responsibility. The CRM Function acts as the decision layer. It performs the discount calculation, determines the appropriate approval level, and updates the control fields. This ensures that the logic behind the approval requirement is accurate and intentional.

The workflow serves as the trigger layer. Its only job is to execute the function whenever a quote is created or edited. It does not contain business logic; it simply initiates the evaluation process at the right time.

The approval process becomes the governance layer. Once the function sets the appropriate status, the approval engine evaluates the criteria, submits the record, locks it, routes it to the correct approver, and maintains the approval history. This is where enforcement happens.

Finally, the reporting hierarchy determines who the approver is. Instead of hard-coding specific users, the system dynamically identifies the appropriate manager or second-level supervisor based on the role structure. This keeps the design scalable and adaptable to organizational changes.

By separating calculation, triggering, enforcement, and routing into distinct layers, the solution remains clean, maintainable, and easy to extend. The Approval Process continues to do what it does best—govern and enforce—while the Function ensures that the decision it evaluates is accurate and business-driven.

Summary

Zoho CRM’s native Approval Process is powerful and reliable.
When business logic depends on calculated values, like true discount percentage, introducing a function strengthens the design by ensuring accurate, consistent decision-making.
Used together, Functions and Approval Process create:
  1. Intelligent routing
  2. Accurate governance
  3. Clean audit trails
  4. Scalable architecture
That combination is what makes this solution robust.

We hope you liked this post. We'll see you next week with another interesting one!
Write to us at support@zohocrm.com or let us know your feedback in the comments section of this post.

Cheers!



==========================================================================




    • Sticky Posts

    • Kaizen #198: Using Client Script for Custom Validation in Blueprint

      Nearing 200th Kaizen Post – 1 More to the Big Two-Oh-Oh! Do you have any questions, suggestions, or topics you would like us to cover in future posts? Your insights and suggestions help us shape future content and make this series better for everyone.

    • Kaizen #226: Using ZRC in Client Script

      Hello everyone! Welcome to another week of Kaizen. In today's post, lets see what is ZRC (Zoho Request Client) and how we can use ZRC methods in Client Script to get inputs from a Salesperson and update the Lead status with a single button click. In this

    • Kaizen #222 - Client Script Support for Notes Related List

      Hello everyone! Welcome to another week of Kaizen. The final Kaizen post of the year 2025 is here! With the new Client Script support for the Notes Related List, you can validate, enrich, and manage notes across modules. In this post, we’ll explore how

    • Kaizen #217 - Actions APIs : Tasks

      Welcome to another week of Kaizen! In last week's post we discussed Email Notifications APIs which act as the link between your Workflow automations and you. We have discussed how Zylker Cloud Services uses Email Notifications API in their custom dashboard.

    • Kaizen #216 - Actions APIs : Email Notifications

      Welcome to another week of Kaizen! For the last three weeks, we have been discussing Zylker's workflows. We successfully updated a dormant workflow, built a new one from the ground up and more. But our work is not finished—these automated processes are