App catalogue Sales and service

Quote discount approval

Routes every quote whose discount passes the band to the sales manager and then pricing, and returns the approved status and discount to the quote.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 Quotes to approvescreenS02 Quote reviewscreenS03 DecisionscreenS04 Seller viewscreenS05 Discount boardscreendh_quoteQuotationdh_customerCustomer masterdh_pricePrice conditiondh_soSales order lineSalesforceQuote · QuoteLineItemSalesforceAccountSalesforcePricebookEntry · Product2SalesforceOrder · OrderItemrows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on Salesforce. Other systems have their own page.
3 days
of configuration to a production-grade version
estimate
5
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
2
clocks with escalation
catalogue
What it does

Today, and with the app

Today a seller who needs a discount above the band emails the sales manager with a screenshot of the quote, and pricing finds out when the order arrives. The approval sits in the inbox, and the quote in the CRM still shows the old status.

The app watches quotes as they are saved and picks up any line where the discount passes the band for the customer's segment, or where the quote value passes 250,000. The seller sees the margin at the proposed discount, the last 3 orders of the customer with the discounts they carried, and the list price condition, and adds the reason. The sales manager approves within the first band, pricing approves within the second, and the sales director decides above 30 percent or 1,000,000. The decision, the approved discount and the approver's note are written to the quote, and the seller sends it from the CRM as usual.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
Sellerproposes the discount with the reason and the expected volume
Sales managerapproves up to 20 percent, or returns with a counter-proposal
Pricing deskchecks margin and the customer's price history; approves up to 30 percent
Sales directordecides above 30 percent or above 1,000,000
Screens

5 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Quotes to approvegrid of quotes waiting with customer, value, discount, margin and age; filter by region and seller; open button
S02 Quote reviewquote lines with list price, proposed price, discount and margin per line; the customer's last 3 orders and their discounts; reason field; competitor field
S03 Decisionapprove, counter-propose a discount or return; note; the margin at the approved discount
S04 Seller viewmobile screen: status of the seller's quotes, the counter-proposal, accept or revise
S05 Discount boardapprovals by seller and region; average discount by segment; quotes won at each discount band
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Quotationquote lines, value, discount and validitySalesforce · S/4HANA · Oracle Fusion · Snowflake
Customer mastersegment, sales organisation and termsSalesforce · S/4HANA · Oracle Fusion · Snowflake
Price conditionthe list price condition for each productSalesforce · S/4HANA · Oracle Fusion · Snowflake
Sales order linethe customer's recent orders and their valueSalesforce · S/4HANA · Oracle Fusion · Snowflake

Written back

ObjectWhat changes
Quotationapproval status, approved discount per line and approver note written to the quote; a returned quote goes back to draft with the note
The flow

From the trigger to the last write

THE FLOW · QUOTE DISCOUNT APPROVAL1Quote picked upquote shown on S01 for theseller's manager; margincomputed per line2Manager decisionapproved up to 20 percent;higher discounts move topricing3Pricing decisionapproved up to 30 percentwith the margin recorded;above that the salesdirector decides4Quote updatedstatus and approveddiscount written to thequote; seller notified onmobile5Outcome trackedwon or lost recorded whenthe order arrives or thequote expires
Each step and the criterion that moves it.

Start: A quote saved with a line discount above 15 percent, or a quote value above 250,000.

# start criterion, in canonical fields; each system page shows it in that system's fields
{quote.discount} > 15 or {quote.value} > 250000

StepMoves when
Quote picked upquote shown on S01 for the seller's manager; margin computed per line
Manager decisionapproved up to 20 percent; higher discounts move to pricing
Pricing decisionapproved up to 30 percent with the margin recorded; above that the sales director decides
Quote updatedstatus and approved discount written to the quote; seller notified on mobile
Outcome trackedwon or lost recorded when the order arrives or the quote expires
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
grd_lineson load → read list price and cost for each product → show margin per line, colour lines below the floor
btn_counteron click → write the counter-proposed discount to the review → notify the seller on S04, pause the clock
btn_approveon click → call the CRM quote interface with status and discount per line → store the record ID, close the review, refresh S01
tmr_expiryon quote valid-to date passed → mark the review expired → record the outcome on S05

Clocks

StepTime limit and escalation
Manager decision4 working hours, then the seller and the sales director are told
Pricing decision1 working day, then the review escalates to the head of pricing

Measures

hours from quote to decisionaverage approved discount by segmentmargin on approved quotesquotes won by discount band
A day with the app

Illustrative

Names, places and figures are illustrative; the pattern is the catalogue's.

At 14:10 on a Tuesday, Tomás, a seller in São Paulo, saved a quote for 420,000 with a 24 percent discount on 2 of its 6 lines. His manager saw the margin at 31 percent and the customer's last order at 18 percent, and countered at 21 percent within the hour; Tomás accepted from his phone at 15:40 in the customer's car park. Pricing approved at 16:05, the quote in the CRM showed the approved status and the new discount a few seconds later, and the customer signed the next morning.

illustrative scenario · Quote discount approval
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Discount bandThe range of discounts a role may approve, set per customer segment.
Margin floorThe lowest margin per line the company accepts on a quote; lines below it are shown in red.
List priceThe price condition in the ERP before any discount.
Questions

How long does it take to have this running?

About 30 minutes to a first running screen on your live rows, and 3 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.

Which system does it run on?

Any of Salesforce, SAP S/4HANA, Oracle Fusion Cloud, Snowflake, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.

Who takes part from outside the company?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.