Updated: October 7, 2026
Originally posted: March 20, 2023
List price is visible. Pocket price is what you keep. Learn how to measure each off-invoice layer, set pocket price floors, and assign an owner to every deduction, so Heads of Pricing and CFOs can find where margin leaks and fix it.
A 1% price improvement lifts operating profit by 8.7% on average, assuming no loss of volume, according to McKinsey. In distribution, their analysis of 140 public companies puts the same 1% at more than a 22% boost in EBITDA margin. Most Heads of Pricing and CFOs in manufacturing and distribution accept that math. Fewer can say which layer of their price waterfall is giving it away.
That is the real gap. List price is visible. Invoice price is tracked. Everything between invoice and pocket is spread across functions that each see only their own piece: rebates accruing at quarter-end, freight absorbed by logistics, payment terms extended by exception. The leakage is not a surprise to anyone. It is simply no one’s number.
This guide began as a definition of the price waterfall. It is now a diagnostic. Below: how to measure each off-invoice layer, the data you need, how to set pocket price floors, and who should own each layer. By the end, you can run the waterfall on your own transactions and know what to do with the result.
If you lead Pricing, this gives you a measured pocket price, floors you can enforce, and a monthly review where every layer owner shows up. That is the basis for authority over the total, not only over list price. If you run Finance, it gives you what you need to defend the number: every layer reconciled to the ledger, every exception traceable, and a named owner for each deduction.
What is a price waterfall?
A price waterfall (also called a pocket price waterfall) traces every deduction between the list price and the pocket price: the net amount you actually keep on a transaction. The name comes from the way price steps down through layers of discounts, rebates, allowances and concessions before it reaches the bottom line.
Each layer usually has a reasonable justification and a different owner. That is the problem. Sales approves the discount, finance books the rebate, logistics absorbs the freight, and no one function sees the cumulative cost. The waterfall puts them on one page.
It answers three questions that invoice-level reporting cannot:
- Where does the margin go? Which layers take the most between list and pocket.
- Who put it there? Which function, program or approval path created each deduction.
- Is it consistent? Whether two customers with similar volumes end up at the same pocket price, or nowhere near it.
You can recover margin without raising list prices. You need to know which layer to enforce, and who is accountable for it.
Five layers between list price and pocket price
The waterfall runs in a fixed order, and each layer hides a different kind of leakage.
- List price. The published price in your catalog or price book. Every other layer is measured against it.
- On-invoice discounts. Volume tiers, distributor and channel discounts, promotional pricing. They print on the invoice, so this is the layer most teams already track.
- Off-invoice rebates and incentives. Growth and volume rebates, market development funds, co-op advertising, off-invoice promotions. They settle after the sale, often quarterly or annually.
- Terms, freight and allowances. Cash discounts for prompt payment, the carrying cost of receivables, freight absorbed by the seller, return allowances, performance penalties.
- Pocket price. What remains. If your products are customized or your cost to serve varies by account, go one step further to pocket margin: pocket price minus direct product cost and the cost of serving that account.
Layers 3 and 4 are where the money goes unseen. They are not on the invoice, they settle at different times, and they sit in different systems. The measurement section below takes them one at a time.
Example: From a $1,000 list price to a $787 pocket price
Take an industrial equipment manufacturer that sets a list price of $1,000 per unit. A customer commits to 500 units a year and earns a 10% volume discount. The customer pays within 15 days, which earns a 2% early-payment discount, and exceeds last year’s purchases, which earns a 5% growth rebate. The manufacturer also absorbs freight instead of billing it.
Each deduction looked reasonable when it was approved. Together they take 21.3% of list price, and only the volume discount is printed on the invoice. Notice the bases, too. The early-payment discount applies to the invoice price. The growth rebate is calculated on list-price spend. Neither is wrong, but if Sales and Finance do not know which base each program uses, no one can reconcile them.
Sales owns the discount, Finance owns the rebate and the terms, Logistics owns the freight. None of them sees the total. When B2B companies build their first waterfall, this is usually what they find.
How to measure each off-invoice layer
Measure every layer on what was actually taken or paid, expressed as a percentage of list price on each transaction line. Three rules keep the numbers comparable:
- Measure what happened, not what the contract allows. Discounts taken, rebates paid, days to pay.
- Use one base. A percentage of list price on the transaction line lets you add the layers and rank them.
- Tie it out. The sum of the layers should reconcile to revenue deductions in the general ledger. If it does not, the gap is itself a finding.
| Layer | Measure (per transaction line) | Data needed | Watch for |
| Cash discounts | Discount actually taken ÷ list value; take rate; days paid vs. discount window | Cash application and payment dates, terms master, invoice lines | Customers who take the discount but pay after the window closes |
| Payment terms | Carrying cost of receivables, from actual days to pay (formula below) | Payment history, treasury’s cost-of-capital rate | Using contractual terms instead of actual days to pay |
| Volume and growth rebates | Accrued rebate allocated to each qualifying line, reconciled to rebate paid and to the contract calculation | Rebate agreements (tiers, thresholds, retroactive or incremental, eligible products), sales history, accrual ledger, settlements | Flat-rate accruals when tiers reset retroactively; one program calculated on list spend and another on net spend |
| Promotions, MDF and co-op | Program spend ÷ the sales it targeted, allocated to those customers and SKUs | Program approvals, claims, proof of performance, marketing ledger | Spend booked as marketing expense, so it never reaches the waterfall |
| Freight and delivery | Freight paid − freight billed, allocated by weight, volume or distance | Carrier invoices or transportation system data, order shipping terms, line weights | Company-wide freight cost spread by revenue, which hides small, heavy orders |
| Returns, credits and penalties | Credits issued ÷ gross sales, by customer and reason code | Credit memos, returns records, service-level results against contract penalties | Credit memos not linked back to the original invoice line |
The carrying cost of receivables, per transaction line:
Carrying cost = Invoice value × Cost of capital × (Actual days to pay ÷ 365)
Rebates deserve the most scrutiny. They are large, they settle late, and the calculation base often differs from program to program. McKinsey’s July 2026 work on distributors points to contract terms as a source of leakage that is often invisible until it is reconciled to transactions: one industrial provider that analyzed more than 500 contracts found roughly 5% margin uplift available through term optimization.
Set pocket price floors, not invoice floors
A floor set on invoice price lets the off-invoice layers push the real price below your minimum without anyone approving it. Set the floor on pocket price, or on pocket margin if your cost to serve varies by account, and set it by segment rather than company-wide.
Start with the cost of the transaction: direct product cost plus the cost of serving that account (freight, handling, technical support). Then choose the minimum pocket margin for each segment.
Pocket price floor = (Direct product cost + Cost to serve) ÷ (1 − Minimum pocket margin)
The floor is only useful at quote time if reps can see what it means for the invoice. Convert it using the customer’s expected off-invoice deductions, as a share of invoice price:
Minimum invoice price = Pocket price floor ÷ (1 − Expected off-invoice rate)
In the worked example above, this customer’s off-invoice layers (early-payment discount, growth rebate and freight) total $113 on a $900 invoice, or 12.6%. If the pocket floor for this segment is $760, the lowest invoice price a rep can quote without approval is about $869, roughly 13% off list. The same rep looking only at invoice margin would never see the difference.
Because the floor is a trigger for a decision, build the approval path around it:
| Pocket price vs. floor | Zone | Who decides |
| At or above target | Target | Sales rep |
| Between floor and target | Negotiating range | Sales manager |
| Below floor | Exception | Pricing, with Finance for large or repeated exceptions |
Two data points show why the basis matters. A tempered-glass manufacturer in McKinsey’s pocket margin analysis needed a pocket margin of at least 12% just to break even, and more than a quarter of its sales fell below that line. More recently, a building materials distributor whose sellers overrode system prices in more than half of transactions cut overrides by 80% and expanded margin by more than 200 basis points.
Track the share of transactions below floor and the override rate every month. Review floors when costs move, and give any strategic exception an owner and an expiry date. Done well, a floor gives Pricing a defensible reason to say yes faster, not only no.
Assign an owner to every layer
Every layer has a function that sets it, one that measures it, and one that enforces it. When those are three different people with no shared view, no one answers for the total. The table below shows a typical split for a manufacturer or distributor. Adjust it to your org chart, but fill in every cell.
| Layer | Sets the policy | Measures | Enforces |
| List price and on-invoice discounts | Pricing, with Sales leadership | Pricing | Sales leadership, through approval thresholds |
| Cash discounts and payment terms | Finance (credit and treasury), with Sales for customer-specific terms | Finance (receivables) | Finance (collections) |
| Volume and growth rebates | Sales or channel leadership; Pricing reviews program design | Finance (accruals); Pricing (program effectiveness) | Finance (claims and settlement against contract) |
| Promotions, MDF and co-op | Marketing or channel | Finance | Marketing, through proof of performance |
| Freight and delivery | Supply chain or logistics | Logistics, with Finance | Logistics; Sales approves exceptions to freight terms |
| Returns, credits and penalties | Customer service or operations | Operations and Finance | Operations (reason codes); Finance (credit approval) |
| Pocket price (the total) | Head of Pricing, accountable | Pricing, reconciled by Finance | CFO as sponsor and final arbiter |
The last row matters most. Someone has to be accountable for the number that results from all the layers, and Pricing is the natural owner when it has the authority to match. That authority should be explicit: any new rebate program, freight policy or terms change gets a waterfall impact estimate before it is approved, and the layer owner shows the effect on pocket price, not only on their own budget.
The tempered-glass manufacturer in McKinsey’s case did this in practice. It reviewed each standard waterfall element to make sure it had clear objectives, accountability and controls. McKinsey’s 2026 pricing research makes the same point at larger scale, recommending a pricing command center that coordinates pricing, IT, finance, sales and data science around shared objectives.
A monthly pocket price review, chaired by the Head of Pricing with every layer owner in the room, is enough to start. The CFO’s role is to make sure it happens and that its findings change policy.
Run the diagnostic on your own transactions
Start with one product family, prove the method, then widen it.
- Scope it. Pick one product family or customer segment and the last 12 months of invoiced transactions.
- Pull the data. At minimum: invoice lines (customer, SKU, quantity, list price, invoice price, date); cash application and payment dates; rebate agreements with accrual and settlement records; freight paid and freight billed; credit memos; standard cost and cost-to-serve drivers.
- Build the waterfall at transaction-line level. Use the measures in the table above, with every layer as a percentage of list price. Roll up by customer, product and sales rep afterward, not before.
- Reconcile to the ledger. The layers should sum to the revenue deductions Finance reports. Investigate any gap before drawing conclusions.
- Plot the pocket price band. Chart sales volume against pocket price as a percentage of list. The shape matters more than the average.
- Test against the floors. Calculate the share of revenue below the pocket price floor, by segment, and the override rate by seller.
- Assign actions. For each finding, name the layer, the owner and a target. Re-run the waterfall quarterly.
Reading the results
- A wide band is an opportunity. In McKinsey’s lighting-supplier case, some products sold at a pocket price below 30% of list while others sold at 90% or more. When the band is wide, small changes to its shape can move the average by a point or more.
- Check the pattern against size. If small customers hold lower pocket prices than large ones, discounts are following relationships rather than volume or cost to serve.
- Rank the layers. The layer that takes the most pocket price from a segment is where to start.
At that lighting company, bringing small accounts’ discounts into line and tightening discount rules raised the average pocket price by 3.6% and operating profit by 51% in the first year. The case is two decades old, but the method holds: the gain came from finding where the waterfall was uneven, not from raising list prices.
Where the AI Pricing Assistant fits
The diagnostic above is work most pricing teams do by hand, in spreadsheets, over weeks. Vendavo Analytics builds the price waterfall from ERP, CRM and billing data, with margin leakage detection and root cause analysis. The Vendavo AI Pricing Assistant lets your team ask questions of that data in plain language:
- “Show me margin leakage quarter over quarter for the last four quarters.”
- “What is the root cause of margin leakage for Customer X?”
- “Which products face excessive price variation between region X and region Y?”
- “What are the biggest opportunities to realize margin growth?”
For a CFO, the question is whether the answer can be defended. The AI Pricing Assistant runs predefined algorithms, validated by Vendavo data scientists, on your transactional data. The same question returns the same answer, and each number traces back to its inputs. It is not a generic language model guessing at your margins.
The results show up in the work. A medical device manufacturer using the AI Pricing Assistant saves about 80% of its time on pricing analysis, roughly 20 hours a week for the team. JLR uses it across 700,000 part numbers in 33 markets to find where to look first among 33 million price points. Across Vendavo Pricing, customers realize an incremental 1–3% average gross margin improvement.
The timing matters. In McKinsey’s November 2025 survey of 419 pricing executives, 65–85% of organizations expect to adopt gen AI or agentic AI in pricing within one to three years, up from 10–30% today. The same survey found a gap between impact and investment: 62% ranked discount approval and governance among the top three opportunities, while only 22% ranked it a top three investment priority. Data quality and integration complexity were the most common barriers to realizing value. The waterfall diagnostic is how you build that data foundation.
FAQs about the price waterfall
What is pocket price?
Pocket price, also called net realized price, is the amount you keep per unit after every discount, rebate, allowance, fee and cost of terms. It is always below list price. How far below depends on how many layers you run and how well you control them.
How do you calculate a price waterfall?
Start with list price. Subtract on-invoice discounts, then off-invoice rebates and incentives, then terms, freight and allowances. What remains is the pocket price. Subtract direct product cost and cost to serve to get pocket margin. Calculate each layer on the same base, a percentage of list price, so you can rank them.
What data do I need to build one?
Invoice lines with list and invoice price, cash application and payment dates, rebate agreements with accrual and settlement records, freight paid and billed, credit memos, and standard cost plus cost-to-serve drivers. The measurement table above lists the data for each layer.
How do I set a pocket price floor?
Divide the sum of direct product cost and cost to serve by one minus your minimum pocket margin, by segment. Then convert the floor to a minimum invoice price using the customer’s expected off-invoice rate, so sellers can act on it at quote time.
Who should own each layer of the waterfall?
Each layer needs a function that sets policy, one that measures and one that enforces. The Head of Pricing should be accountable for the total pocket price, with the CFO as sponsor.
What causes margin leakage?
Uncontrolled discounts, inconsistent rebate structures, complicated channel pricing and manual processes. When pricing decisions are made in separate functions without shared visibility, small concessions add up across thousands of deals. The leak becomes part of the structure instead of an exception.
Is price waterfall analysis relevant for B2B manufacturers and distributors?
Yes, and more than for most. B2B pricing carries negotiated contracts, volume tiers, channel partners and rebate programs that stack on each other. The waterfall shows what you earn from each customer, channel and product line after all of it.
Why not offer deeper discounts to win volume?
Because the volume rarely comes. In McKinsey’s analysis of typical S&P 1500 economics, volume would have to rise by 18.7% just to offset the profit impact of a 5% price cut.
How often should we run it?
Re-run the full waterfall quarterly. Track the share of transactions below floor and the override rate monthly, in the pocket price review.
Turning waterfall transparency into profit
The waterfall shows where margin goes. The diagnostic shows who put it there and what to do about it. Companies that hold their margin do not rely on one-time negotiations. They enforce discipline at every layer, with an owner for each and a floor under the total.
- Measure each off-invoice layer on what was taken or paid, as a percentage of list price per transaction line, and reconcile it to the ledger.
- Set floors on pocket price or pocket margin by segment, and convert them into minimum invoice prices that sellers can see.
- Give every layer a policy owner, a measurer and an enforcer. Make the Head of Pricing accountable for the total.
- Re-run it quarterly. The first pass finds the leaks. The second shows whether the fixes held.
Ready to see your own waterfall? Schedule a demo with a Vendavo expert today.