When a supplier's input costs rise, you hear about it fast. A letter arrives, usually within the quarter: formal in register, apologetic in tone, firm in content. It names an index, cites a percentage, sets an effective date. When the same input costs fall, nothing arrives. No letter, no revised rate card, no effective date. The price you accepted at the top of the cycle quietly becomes the new floor.

This is the least discussed asymmetry in supplier pricing, and across a full cost cycle it moves more money than most negotiation programs recover. It is not the product of dishonest suppliers. It is the product of one side having a process and the other side having an assumption.

One direction has a machine behind it

The price increase is an institutional product. Most mid-size and large suppliers run a margin-recovery motion with real infrastructure behind it: a pricing team that tracks the input indices, letter templates reviewed by legal, a playbook for sequencing which accounts get the letter first, and a recovery-rate metric that someone's bonus depends on. We wrote before about the price-increase letter as a negotiation event. The point here is what surrounds it: a repeatable process, staffed and measured, that fires whenever costs move in one direction.

Now look for the equivalent machine pointing the other way. There is no decrease team. There is no template titled "notice of price reduction following favorable input movement." There is no metric anywhere in a supplier's organization that counts how much margin was voluntarily handed back. The motion does not exist, because no rational business builds infrastructure to shrink its own revenue. A price decrease happens under exactly one condition: a customer asks for it, with an argument attached.

So the two directions of the same market movement get two different mechanisms. Cost up: supplier-initiated, professionally executed, near-universal. Cost down: buyer-initiated, rarely executed, entirely dependent on whether anyone on your side noticed.

Why the silence is structural

Three structural facts keep the decrease conversation from happening, and none of them is fixed by trying harder.

First, the information sits on the wrong side of the table. The supplier knows their cost stack in detail; you see a price. When resin or ocean freight or wage indices move, the supplier's pricing team knows the margin impact that week. Your category manager, covering 200 suppliers across a dozen input markets, finds out when a benchmark lands or a competitor mentions it in passing. The side with the information has no incentive to volunteer it, and the side with the incentive doesn't have the information.

Second, the calendar has no trigger. Increase letters arrive on the supplier's schedule, which tracks the index. Your negotiation calendar tracks contract dates: renewals, rate-card cycles, MSA reviews. An input market that peaks and reverts in the middle of a three-year term hits no tripwire on your side at all. By the time the renewal opens, the elevated price has 18 months of tenure and looks like the baseline.

Third, the ask is socially harder than the refusal. A category manager opening a mid-term decrease conversation is initiating conflict without a contractual hook, on spend that is performing fine, with a supplier who will smile and offer to "hold your next increase" instead. That counteroffer trades a real reduction today for a promise about a letter they control the timing of. Most teams take the trade, because the alternative is a fight nobody scheduled.

A price increase is a negotiation your supplier starts. A price decrease is a negotiation nobody starts. That is the entire mechanism, and it ratchets your cost base upward one cycle at a time.

What the ratchet costs over a cycle

Run the arithmetic on one category. Say $5M of annual spend where 30% of the supplier's cost stack is a volatile input: resin, steel, ocean freight, contract labor. The input spikes and the supplier passes through a 12% increase, citing the index by name. That letter was mostly justified at the moment it was sent; call it $600K of new annual cost. Two years later the index has given back most of the move. If nobody reopens the price, the recovered portion stays in the supplier's margin: several hundred thousand dollars a year, on one category, continuing indefinitely. The exact figure depends on the pass-through math, but the direction never varies, and it repeats every cycle in every category with a volatile input underneath it.

The ratchet also compounds with the mechanisms we've written about before. The escalator clause applies next year's percentage to this year's elevated base, so an increase that was never given back doesn't just persist. It grows. Stack three cost cycles on a decade-long supplier relationship and the gap between the price you pay and the price a cost-informed negotiator would pay stops being a rounding error and starts being the margin difference between you and the competitor whose team asks.

The letter you filed is the case you need

Here is the useful irony: the strongest evidence for a decrease request is the supplier's own increase letter. That letter named an index, quantified an exposure, and asserted a pass-through logic. It is a signed confession of the cost model. When the index reverts, the argument writes itself: same index, same arithmetic, opposite direction. A supplier can argue with your consultant's benchmark. Arguing with their own letter means disowning the logic they used to raise you.

That suggests a short list of practical moves. Keep every increase letter in one place, tagged by the index it cites; the file is a map of exactly where your pricing is exposed to markets that move both ways. Put the index, not the contract date, on the calendar: a quarterly review of the three or four indices your accepted letters have named costs an hour and creates the trigger that doesn't exist today. And when the moment comes, send the mirror image of what they sent you: one page, their index, their percentage logic, a proposed effective date. The teams that do this report a version of the same pattern: the first conversation is awkward, the second one is expected, and by the third the supplier starts pre-empting with smaller increases, because they know this account checks.

Where the contract is still open, fix the asymmetry at the source. If a supplier wants indexation upward, the same clause can move downward; a symmetric collar is a reasonable ask precisely because it uses the supplier's own logic. Refusing symmetry is a supplier admitting the index was a ratchet, not a pass-through, and that admission is worth having in the room even if you lose the clause.

What this means for how we build

The decrease conversation fails today because it depends on memory and attention that no procurement team can staff: who accepted which letter, citing which index, with what arithmetic, and where that index is now. This is exactly the shape of problem Whispor Assist's counterparty memory is built for. Every increase letter becomes part of the supplier's record; when the cited index reverts, Whispor Assist surfaces the decrease case with the supplier's own pass-through logic already loaded, and the category manager walks into the conversation carrying the file instead of reconstructing it.

Whispor Auto runs the same motion where no human was ever going to ask: across the tail, where thousands of prices sit on top of the same handful of input markets and nobody has ever opened a decrease conversation in the history of the account. The supplier side has run a one-way pricing machine for decades because the buyer side never had one pointing back. Building the return direction is not a feature. It is the point.

The Whispor team

Related: The price-increase letter is a negotiation · The escalator clause negotiates every year · Contract renewals: stop value leaking at auto-renewal