Net revenue management: from list price to what you keep

Gross sales are units times list price. Net revenue is what remains after the deductions. The gap between them is the gross-to-net (GTN) gap, and a waterfall lists it one deduction at a time.

Trade spend is the part of these deductions that pays the retailer for promotion, placement or performance. Where exactly trade spend ends and an ordinary discount begins is a company decision, so state yours.

Under US GAAP, payments to a customer generally reduce the transaction price, and so revenue. The exception is a payment for a distinct good or service the customer provides at fair value (ASC 606-10-32-25 and 32-26; see Deloitte’s Roadmap). Deloitte notes that payments for shelf changes are not for a distinct service. Your controller decides how each program is classified, but the working rule for NRM is that trade spend is a deduction from revenue, not a marketing cost beneath it.

Worked example: one case from list to net

One case holds 12 units and lists at $24.00, or $2.00 a unit. The terms are invented.

Two details decide whether a model matches the ledger. The first is the base each term names. The early-pay discount is 2% of the invoice price ($22.80), which is $0.46. Applied to list it would be $0.48. A model that applies every percentage to list overstates the deductions. The second is which deductions are per case, per unit sold or a lump sum. A placement fee spread per case does not move when list does.

Five levers set net revenue per unit. They act on different parts of the waterfall and usually belong to different teams, which is why net price drifts even when everyone does their job. A deduction cuts margin dollar for dollar because unit cost does not change. A mix shift or a volume gain at a lower net price can raise revenue while profit falls.

List price

List price sets the top of the waterfall. A price increase pays when the volume it costs is smaller than the break-even loss. Use net margin per unit, which is net price less variable cost, not list.

The formula works on net price. A list increase that does not reach net, as in the next section, does not buy the volume cushion it appears to.

Pack price architecture

Pack price architecture (PPA) is the set of sizes and formats you sell and the price steps between them. It changes the price per unit shoppers see at each size and which size they buy, so it moves both price and mix. The method for reading it is in the price pack architecture guide, and the arithmetic for comparing sizes is in price per unit analysis.

Promotion

A promotion should be judged against a baseline: the volume that would have sold anyway. Everything sold at the deal price that would have sold at the regular price is margin given away. Lift alone hides that.

That result is before the three things that make real events worse and that this example leaves out: the dip after the event as shoppers use up what they stocked, the purchases pulled forward from the weeks around it, and sales taken from your other packs. Measure all three before you call an event a success.

Trade terms

Trade terms are the standing rules in the customer agreement: off-invoice rates, scan funding, fees, payment terms. They change slowly and are negotiated customer by customer, so the total drifts without anyone deciding it should. Simon-Kucher’s 2025 outlook for CPG describes companies tightening proliferated trade spend, asking retailers for counter-performance, and using gross-to-net as a way to raise net price. The practical form of counter-performance is a term that pays only when the retailer delivers the display, the feature or the price the money was for.

Mix

Mix is the share of volume sold in each pack, brand, channel and customer. When shoppers move from a high-priced item to a low-priced one, the average net price per unit falls with no price change anywhere. Mix is also a lever: a ladder that makes the profitable size the sensible choice raises average net price without a list increase. The bridge below separates mix from price.

Take the case from the waterfall and raise list by 3%. Suppose the retailer pushes back and the manufacturer gives some of it back by deepening the scan-back from 6% to 9% of list. Every other term stays as it was.

Increase realization compresses this into one ratio: the percentage change in net price divided by the percentage change in list. Here it is −18%. A value of 100% means the whole increase reached net, and below zero means net moved the other way. A finance report that reads “price +3%” is reading list. It is correct and it is not the answer.

Three mechanisms produce this pattern, and a waterfall shows each one.

• The retailer takes it back through terms. The increase is accepted in return for more promotion funding or a better allowance. The deduction lines grow while list looks healthy.
• Percentage terms scale with the base. The off-invoice rate stays at 5%, but it is now $1.236 instead of $1.200. The same deal costs more dollars after a list increase.
• Volume protection is paid for in promotion. Deeper or more frequent events defend share after a price rise. Whether they bought volume is a promotion question, and the promotion example above shows how easily they do not.

The shopper may or may not see any of this. Whether a list increase reaches the shelf depends on the retailer. Track net price per unit by customer and item next to list price, and review it before every list change, not after.

A price-volume-mix (PVM) bridge splits the change in net revenue between two periods into three parts. Volume is the change in total units, valued at last period’s average price. Mix is the effect of the units moving between items, packs or customers. Price is the change in each item’s own price. The three parts add up to the total change exactly.

Worked example: a brand with two packs

Volume is in thousands of ounces and price is net dollars per ounce. The small pack’s net price rises from $0.20 to $0.21, a 5% increase. The large pack’s price is unchanged. Volume grows, and shoppers lean toward the large pack.

The bridge answers a question a price table cannot: how much of the increase stuck. The small pack’s price rose 5%, but the average net price per ounce rose only 1.1% because 13 points of volume moved to the cheaper large pack. Read alone, the price effect says the increase worked. Read with the mix effect, 54% of it was given back through the ladder.

Conventions differ. Some bridges value the price effect at period 1 volume and add an interaction line, others compute mix at the customer or brand level instead of the pack. The splits differ between conventions and the total never does. Pick one convention, write it down and use it every period. Pick one volume unit as well: mix measured in packs and mix measured in ounces tell different stories when pack sizes differ.

A short set, each with one definition, covers most of what a commercial team needs from the waterfall.

Published trade-rate ranges exist, but they come from consultancy articles that give no method or sample. Deloitte, for one, says trade spending often makes up 20 to 30 percent of gross sales. Treat a figure like that as a sense of scale. Your own rate by customer and category, tracked over time, is the benchmark that matters.

1. Reading a shelf price move as a net revenue move. The shelf price is the retailer’s, and your revenue starts at the invoice.
2. Judging a promotion by lift. The event above lifted volume 140% and lost $120.
3. Ignoring the dip and the cannibalization. A baseline-adjusted result that skips both still flatters the event.
4. Treating trade spend as marketing. Booked as a cost below revenue, it overstates net revenue and hides the trade rate from the pricing team.
5. Calling a mix shift a price change, or the reverse. Average net price per unit across mixed packs moves with mix. Use the bridge, or compare at the item.
6. Mixing gross and net prices in one elasticity estimate. Shoppers respond to the shelf price. Your margin depends on the net price. Estimate the first on shelf data and run the second through the waterfall, and do not blend them in one regression.
7. Optimizing list price while terms drift. A list increase is reviewed in a meeting. A change in the trade rate is a sum of small decisions nobody reviews.
8. Assuming pass-through. Funding that does not reach the shelf did not move shoppers. Check the shelf price during the event.
9. Importing a benchmark. A trade rate from another category, channel or period is context. It is not a target.

Price pack architecture is one lever inside NRM, and it is the one where outside data helps most. It decides which sizes carry which list price, which fixes the price per unit at each step and shapes mix. The shelf is where you see how that structure looks to a shopper next to competitors and store brands. See pack price ladders for the structure and private label benchmarking for the price gap to the store brand, the competitive reference for the ladder.

Shelf-price data has clear limits, and they decide how to use it.

The consumer-facing side is the half of the gross-to-net chain that a manufacturer cannot see from its own invoices. The invoices, the deduction ledger and the shipment data are the other half, and only you have them.

A spreadsheet is enough for the first pass. Software for trade promotion and RGM earns its cost at scale, with many customers, forecasting and managed baselines. The first version only needs three data pulls.

1. Pick one customer and the ten items that make most of its gross sales.
2. Pull the invoice lines for a quarter: units, list price and the allowances taken on the invoice.
3. Pull the deduction ledger for the same quarter, by type. Map each deduction to a waterfall line. A deduction you cannot map gets its own line, not a place in another one.
4. Build the waterfall per item. Write down how customer-level fees are allocated to items.
5. Reconcile. Net revenue from your waterfall should match net sales booked for that customer within rounding. A gap is a finding: something in the terms or the ledger is not in the model.
6. Compute the six measures by item and month, then build the first bridge at item level.
7. Before each list change or event, forecast net price under your actual terms, not list alone.

Where Shelfprice fits: for the categories it covers, it does the shelf-side work described above: price per unit by pack, ladder checks, promotion frequency and depth at the shelf, and the gap to the store brand (see price pack architecture analysis). It does not see trade spend, invoices, volume or net revenue. One retailer today: Kroger, Ralphs, King Soopers and QFC stores in 5 metros.

• Allocation changes the answer by item. Many deductions, fees especially, belong to a customer, not an item. Item-level net price rests on an allocation rule, and a different rule moves net by item while leaving the customer total alone.
• Timing. Deductions are accrued when the sale is booked and settled weeks later. A bridge built on settled deductions lags the shelf, and one built on accruals is only as good as the accrual rates.
• Baselines are estimates. No one observes the volume that would have sold without the event. It is modeled, and the model changes the verdict.
• PVM is a convention. The effects add up, but the split depends on the order of the steps and the grain of the mix. Compare bridges only when they use the same convention.
• Definitions differ. Two companies, or two divisions, can define gross, net and trade spend differently. A ratio is comparable only inside one definition.
• Pass-through is unobserved. The invoice side shows what you funded. Only shelf or scan data shows what shoppers paid.