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.
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.
| Lane | Does |
|---|---|
| Seller | proposes the discount with the reason and the expected volume |
| Sales manager | approves up to 20 percent, or returns with a counter-proposal |
| Pricing desk | checks margin and the customer's price history; approves up to 30 percent |
| Sales director | decides above 30 percent or above 1,000,000 |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Quotes to approve | grid of quotes waiting with customer, value, discount, margin and age; filter by region and seller; open button |
| S02 Quote review | quote 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 Decision | approve, counter-propose a discount or return; note; the margin at the approved discount |
| S04 Seller view | mobile screen: status of the seller's quotes, the counter-proposal, accept or revise |
| S05 Discount board | approvals by seller and region; average discount by segment; quotes won at each discount band |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Quotation | quote lines, value, discount and validity | Salesforce · S/4HANA · Oracle Fusion · Snowflake |
| Customer master | segment, sales organisation and terms | Salesforce · S/4HANA · Oracle Fusion · Snowflake |
| Price condition | the list price condition for each product | Salesforce · S/4HANA · Oracle Fusion · Snowflake |
| Sales order line | the customer's recent orders and their value | Salesforce · S/4HANA · Oracle Fusion · Snowflake |
| Object | What changes |
|---|---|
| Quotation | approval status, approved discount per line and approver note written to the quote; a returned quote goes back to draft with the note |
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| Step | Moves when |
|---|---|
| Quote picked up | quote shown on S01 for the seller's manager; margin computed per line |
| Manager decision | approved up to 20 percent; higher discounts move to pricing |
| Pricing decision | approved up to 30 percent with the margin recorded; above that the sales director decides |
| Quote updated | status and approved discount written to the quote; seller notified on mobile |
| Outcome tracked | won or lost recorded when the order arrives or the quote expires |
| Component | Trigger → action → outcome |
|---|---|
| grd_lines | on load → read list price and cost for each product → show margin per line, colour lines below the floor |
| btn_counter | on click → write the counter-proposed discount to the review → notify the seller on S04, pause the clock |
| btn_approve | on click → call the CRM quote interface with status and discount per line → store the record ID, close the review, refresh S01 |
| tmr_expiry | on quote valid-to date passed → mark the review expired → record the outcome on S05 |
| Step | Time limit and escalation |
|---|---|
| Manager decision | 4 working hours, then the seller and the sales director are told |
| Pricing decision | 1 working day, then the review escalates to the head of pricing |
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.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Quotation read from Quote · QuoteLineItem (or SBQQ__Quote__c with CPQ); CRM.
Open the Salesforce page →Quotation read from VBAK · VBAP (VBTYP = 'B'); also on SAP ECC.
Open the S/4HANA page →Quotation read from Oracle CPQ REST: transactions (quotes); also on Oracle E-Business Suite.
Open the Oracle Fusion page →Quotation read from CONFORMED.QUOTATION; lakehouse.
Open the Snowflake page →Other systems connect through the same handlers; see how SmartApps connect.
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.
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.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
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.