# The Price You Promised Is Not Always the Price They Get

> A B2B price is built in layers by different teams: list, contract, project discount, rebate, freight and payment terms. Each layer can be approved by the right person and the stack can still land below target. One illustrative example, why the gap stays hidden, and what a single view of price requires.

Source: https://revomo.ai/blog/the-price-you-promised-is-not-always-the-price-they-get/

---

[← All articles](https://revomo.ai/blog/) Focus
Price Realization

## The Price You Promised Is Not Always the Price They Get

Alex Hoff

Chief Customer Officer · Nov 10, 2026 · 5 min read

Narrated by an AI voice 1×

The Price You Promised Is Not Always the Price They Get 5:43 Follow the reading 1×

On this page
- A price is built in layers, by different teams
- How a well-managed price ends up below target
- Why the gap stays hidden
- What a single view of price requires
- Where Revomo fits
Focus mode

Ask a sales leader what a key customer pays for a core product and you’ll usually get a confident answer. It’s typically the contract price, or the price on the last quote. Ask finance what the company actually kept on that same product after rebates, freight, and payment terms, and the number is often lower, sometimes by more than anyone in the room expected. Both answers are accurate. They describe different layers of the same price.

Last week we looked at [turning a dashboard finding into a decision](https://revomo.ai/blog/a-dashboard-tells-you-what-happened-a-decision-tells-you-what-to-do/) someone can act on, and we closed by suggesting a check 90 days later on whether invoiced prices actually moved. This piece is about why the honest answer is so often “partly,” and why the cause is usually structural rather than a mistake.

### A price is built in layers, by different teams

A B2B price is rarely one number that one person sets. It’s a stack. The pricing team sets list prices. Sales and contracts negotiate the customer agreement, usually a discount or multiplier off list. A deal desk approves project and competitive discounts on individual quotes. A channel or finance team runs rebate and growth programs that pay out quarterly or at year-end. Logistics decides when freight gets absorbed, and finance sets payment terms and early-pay discounts.

Each of those levers has an owner, an approval limit, and usually its own system. Contract prices sit in the ERP, quotes live in a CPQ tool or a spreadsheet, and rebate programs run in a rebate tool or yet another spreadsheet. Each owner checks their piece against their own rules, and in fairness, most of them manage their piece well.

What almost nobody has is a view of the whole stack for a given customer and product, at the moment someone is about to add another layer to it.

### How a well-managed price ends up below target

Here’s an illustrative example. Say the last pricing review set a target pocket price of $80 a unit for one product family sold to a tier of distributors. List price is $100.

The distributor’s contract gives 12% off list, so $88. To win a large project, the deal desk approves an extra 6%, which is well inside its authority, and the invoice comes out at $82.72. The deal desk could see the contract price when it approved the discount. It couldn’t see that the same customer was enrolled in a 4% growth rebate, which the program team had set up against projected volume without knowing project discounts were being granted on that same volume. That rebate is worth $3.31 a unit. Logistics absorbs about $2.00 a unit of freight under the customer’s standard terms, and the customer takes the 2% early-pay discount, another $1.65.

The pocket price comes to $75.76, which is $4.24 below the target the pricing review agreed. On about $6M a year of project business, that’s roughly $310K a year. Every step was approved by the right person, inside their own limits, and nobody made an error. The shortfall comes entirely from how the layers combine.

Every layer was approved, and the pocket price still landed $4.24 below target

List price (Pricing team): $100.00. Contract discount, 12% off list (Sales and contracts): $12.00. Project discount, 6% (Deal desk): $5.28. Invoice price: $82.72. Growth rebate, 4% (Program team): $3.31. Freight absorbed (Logistics): $2.00. Early-pay discount, 2% (Finance): $1.65. Pocket price: $75.76. The pocket price is $4.24 below the $80 target.

On about $6M a year of project business, $4.24 a unit is roughly $310K a year. Illustrative: one product family sold to one tier of distributors, as in the post. Hover or focus a row for the amount and who set it.

### Why the gap stays hidden

Most reporting looks at one layer at a time. Sales reports discount compliance against the deal desk matrix. Finance reports rebate accruals as a total liability. Pricing tracks realization at invoice price. Each report is correct, and none of them shows that the same customer is collecting three separate concessions on the same product.

When the overlap does surface, it’s usually late. It shows up at year-end rebate settlement, or when an account’s margin comes in below plan and an analyst rebuilds the [price waterfall](https://revomo.ai/blog/the-price-waterfall-a-simple-primer-and-why-it-matters-so-much/) by hand from four exports. By then the concessions are a year old and some are written into contracts.

Clerical errors happen too. A price increase gets loaded into the ERP two months late, or a rebate accrues on the wrong basis. Those matter, but they’re the easier problem, because there’s a correct number to check against. The harder problem is that every layer can be right on its own terms and still add up to a price nobody would have approved as a whole.

### What a single view of price requires

Closing the gap doesn’t mean taking authority away from the teams who own each lever. It means giving them the same picture. In practice that takes a few things:

- Every layer of price recorded against the same customer, product, and transaction, including off-invoice items like rebates and absorbed freight that settle months after the sale. Those get estimated at the time of sale and trued up later.
- Visibility at the point of approval. Whoever approves a new discount, rebate, or freight exception should see what the customer already receives in the other layers before saying yes.
- A regular comparison of the price you intended against the price you collected, by account, with each gap traced to the layer and the owner that caused it.

None of this requires a reorganization. It does require the layers to live on the same record, which is the point we made earlier in the series about [one record, not five systems](https://revomo.ai/blog/one-record-not-five-systems/).

### Where Revomo fits

Revomo brings list prices, contract terms, quote discounts, and rebate programs together on the same customer and product record, so pocket price is visible across those layers and the teams who own each one are looking at the same number. That’s the work behind [Price Management](https://revomo.ai/product/price-management/), [Contract Pricing & Renewals](https://revomo.ai/product/contract-management/), and [Rebates & Incentives](https://revomo.ai/product/incentives-management/). The same record feeds a pocket price waterfall, which you can build in [Analytics & Insights](https://revomo.ai/product/analytics-insights/) starting from a Revomo Library template. If you’d like to see how your own layers add up, our [margin assessment](https://revomo.ai/margin-assessment/) is a free first look.

*Next in the series: every number has to trace back to something.*

### Read next

[Next in the series

#### Every Number Has to Trace Back to Something
5 min read · Nov 19, 2026](https://revomo.ai/blog/every-number-has-to-trace-back-to-something/)[More on Price Realization

#### Seeing (and Acting on) the Cost Shock Before It Hits Your Margin
6 min read · Oct 27, 2026](https://revomo.ai/blog/seeing-the-cost-shock-before-it-hits-your-margin/)[More on Price Realization

#### Finding the Leak Before Quarter-End Finds It for You
7 min read · Oct 21, 2026](https://revomo.ai/blog/finding-the-leak-before-quarter-end-finds-it-for-you/)

****

The Price You Promised Is Not Always the Price They Get Exit focus Esc
