Margin intelligence

Price on the number you actually keep

Optimisation in a channel business is less about elasticity modelling and more about consistency: most of the price spread between similar customers is unexplained rather than strategic.

Book a demo See the whole platform

From list price to what you actually keep

An illustrative mid-market distribution waterfall. The shape matters more than the numbers — most businesses can name the first two steps and not the last three.

List price

Where the negotiation starts

100.0%

Contract discount

On invoice — visible

−12.0%

Volume break

On invoice — visible

−4.5%

Ship-and-debit / bill-back

Off invoice — settles later

−6.2%

Year-end rebate

Off invoice — settles later

−3.8%

Promotional allowance

Off invoice — settles later

−2.1%

Settlement terms & freight

Off invoice — often absorbed

−2.4%

Pocket price

What you actually keep

69.0%

Invoice-to-pocket gap −31.0% of list, most of it invisible at the point of sale

Illustrative. Build yours from one month of sold lines — the exercise takes a day.

The same problem, stated twice

Once for the person who owns the P&L, once for the person who owns the systems. Neither column is a summary of the other.

The financial problem

The same product goes out at dozens of prices and the spread is not deliberate.

Margin floors enforced on invoice margin are routinely satisfied by deals that settle below cost once incentives land.
Discount latitude is granted per customer when it should be per product, because rebate-adjusted cost is not visible at the line.
The bottom decile of realised price is where the damage concentrates, and it is invisible in an average.
Erosion accumulates through small defensible moves that reset the market’s expectation.

The technical problem

The number pricing needs does not exist at the line.

Rebate-adjusted net cost is not carried on the item, so it cannot flow into pricing, quoting or margin reporting.
Off-invoice reductions settle in a different system in a different period, so realised price is a reconstruction.
Price approval happens at order entry, before the concessions that will follow are known.
Segment-level price distributions require a query nobody can run interactively.

What RevUpra does

Inside price optimisation

Pocket-price bands

Realised price distribution by segment, product and deal shape — outliers name themselves.

Rebate-adjusted net cost

Computed per item from live agreement rules and published back to pricing and quoting.

Margin floors that hold

Floors expressed against pocket price, including the incentives that settle later.

Stack visibility at approval

The combined effective rate of every concession, shown before the last approval.

Scenario comparison

Weigh structures side by side against your own historical volume before committing.

Erosion monitoring

Multi-period realised-price trend per segment, so slow drift becomes visible.

Benchmarks

What good looks like

Use this as a self-assessment. If you cannot produce one of these numbers for your own programme, that is itself the finding.

Price optimisation benchmarks
Metric	Typical today	Target
Lines priced on rebate-adjusted cost	<25%	>90%
Pocket-price variance per segment	±5 – 9%	within ±3%
Deals with a modelled net contribution pre-approval	30 – 55%	>95%
Margin floors applied to pocket, not invoice	Rare	Standard

Ranges are indicative benchmarks drawn from published channel-incentive and pricing research together with our own implementation experience. They vary widely by programme complexity, channel depth and data quality — treat them as the opening question in a diagnostic, not a guarantee.

None of this requires new pricing discipline from your commercial team. It requires the pocket number to exist at the line, which changes what they win.

Leak points

What this closes

The leak points from our taxonomy that this module addresses directly.

Price erosion & discount stacking

“Every discount was defensible. The stack was not.”

Financially

List price, then a contract discount, then a volume break, then a ship-and-debit, then a year-end rebate. Each concession was approved on its own merits; nobody ever saw the pocket price at the bottom of the stack, which on some lines is below cost.

Technically

Discounts are applied in different systems at different times — order entry, billing, and post-transaction settlement — so no single record holds the fully-loaded net price. Reconstructing it means joining three systems after the fact.

Typical cost: 1.5% – 4.0% of net revenue
Benchmark: Disciplined programmes keep pocket-price variance within a ±3% band per customer segment.

How it closes: Price triangulation resolves invoice price, net-net pocket price and contract price into one number per transaction — visible before the deal is signed.

See the module →

Unclaimed entitlement

“The threshold was crossed. Nobody raised the claim.”

Financially

Volume crossed a tier, a growth kicker or a lump-sum threshold and nobody raised the claim before the agreement window closed. It runs in both directions. Buy-side it is pure margin — earned from a supplier, never invoiced, quietly written off at year end. Sell-side it is the mirror image: an entitlement a customer earned that was never accrued, which returns months later as a retrospective claim settled in full because nobody can still prove what was actually due.

Technically

The agreement terms live in a PDF in a shared drive, not in a system that can evaluate them against the transactions that earn them — purchases on the buy side, sell-through on the sell side. There is no engine watching the threshold, so no event fires when it is crossed. Discovery depends on a person remembering.

Typical cost: 0.3% – 1.1% of purchase spend
Benchmark: Best-in-class recover >98% of earned entitlement within one claim cycle.

How it closes: Agreement terms become executable rules on both sides of the trade. The accrual engine evaluates them nightly against real transactions and raises the claim — or the liability — itself.

See the module →

Reporting latency

“By the time you saw the number, the quarter was over.”

Financially

Channel performance is visible six to eight weeks after the fact, once POS files have been consolidated. Programmes that are not working keep running for another quarter, and the corrective decision arrives after the money is spent.

Technically

Reporting aggregates live over transaction tables, so any useful cut takes minutes to hours and is scheduled rather than interactive. Nobody explores; everybody waits for the monthly pack.

Typical cost: 1 – 2 quarters of decision lag
Benchmark: Leading programmes see channel sell-through within 5 business days of period end.

How it closes: Materialised snapshots make financial reads instant, so channel performance is a screen you open — not a pack you wait for.

See the module →

Terminology

Terms on this page, defined

Plain-language definitions with the reason each one tends to leak.

Pocket price ↗: What you actually keep from a transaction after every on-invoice and off-invoice reduction.
Net-net price / cost ↗: Price or cost after all rebates and allowances — on the sell side, what you keep; on the buy side, what you truly paid.
Price waterfall ↗: The step-by-step decomposition from list price down to pocket price, naming every reduction along the way.
Discount stacking ↗: The accumulation of multiple independently-approved concessions on the same transaction, producing a combined reduction nobody authorised.
Margin floor ↗: The minimum acceptable margin for a transaction, below which approval must escalate.
Price optimisation ↗: Setting price by segment, product and deal characteristics using evidence about what the market actually pays, rather than by cost-plus or by precedent.

Open the full terminology library →

See what RevUpra can recover for you.

Thirty minutes, tailored to your programmes. We walk an agreement through modelling, contracting, accrual, claim and settlement using examples close to your own — and model an indicative ROI against your volumes.

Book a demo Read the leak map