Price Realization

A manufacturer lists an item for $100, quotes $95, gives a $5 rebate and grants $2 in later credits, so its realised price under that chosen basis is $88, which differs from the invoice's initial $95 and must be tied to the same unit and transaction. Choose the comparison price, because a public list price may be irrelevant if every contract has a negotiated rate, and some teams compare actual net price with a signed contract price instead.

Define the realised amount to include agreed discounts, retrospective rebates, promotional credits and returns under a stated rule, and separate freight and tax when they are pass-through items rather than part of product price. McKinsey describes transaction pricing as tracing the list price through discounts, allowances and other deductions to the amount retained, and its pocket-price waterfall is a way to make that path visible.

Collect transaction-level data, since aggregate monthly sales can hide a few deeply discounted deals, and link order, invoice, credit note and rebate to the same customer and product when feasible. Check timing too, because a rebate earned at year-end may not appear on the initial invoice, and a current-month report could overstate realised price until the obligation is accrued or settled.

An illustrative realization percentage is realised net unit price divided by the chosen reference unit price times 100, so a realised price of $88 against a list price of $100 is 88% realization, which does not equal gross margin. Make the unit consistent, since a pallet, case and individual item need conversion before price comparison, and currency rates and taxes can also distort a trend if they shift between periods.

Segment by product, customer and channel, because a low rate may be justified for a volume agreement or a competitive launch while the same concession on a small order may be unplanned, and the number identifies where to ask why. McKinsey's pricing-infrastructure guidance discusses the systems and rules needed to make transaction prices visible and governed, and a strong process does not automatically mean prices should rise; it supports informed decisions.

Separate authorised concessions from leakage, since a contractually promised rebate reduces the price but is not a billing mistake, whereas an unauthorised discount or expired promotion may need investigation. Watch customer outcomes as well, because retracting a valid discount to improve the metric would breach trust and potentially terms, so any pricing change requires commercial, contractual and customer review.

Link price realization with margin, but do not merge them, because a product can have high realization and poor margin when input costs rise, while a low realization rate can coexist with a healthy margin on a low-cost item. Review sales incentives, since a commission plan based only on gross bookings can encourage concessions that emerge later in credits, so align measures so teams see net economics while preserving fair customer terms.

Validate data too, because duplicated credits, unlinked rebate programmes and missing returns can make the calculation unreliable, so reconcile the net amount to finance totals for the same scope and period. Use trend analysis carefully, since a shift toward lower-priced customer segments can reduce the average without any individual discount change, so compare like products and buyers where possible.

Investigate causes before changing policy, as a high level of credits may signal delivery failures rather than sales behaviour, and fixing the service problem may improve realised price more sustainably than tightening approval alone. For an owner, price realization shows the path from intended price to actual net proceeds, and it should explain concessions, not automatically portray every gap as lost money.