Pricing as a process, not an event

The price list was built for a calmer world

The annual price list is an artifact of an assumption: that costs drift a few percent a year, so pricing once a year, with a cushion, is close enough. That assumption is gone. Tariffs get announced, paused, revised, and doubled inside a single quarter. Oil moves and takes resin, packaging, and every freight lane with it. Metal surcharges appear on supplier invoices mid-contract. A manufacturer's input costs now reprice monthly whether the manufacturer does or not — and holding a price list steady for a year just means financing the difference out of margin until the next printing.

The instinctive response is a bigger annual increase with a bigger cushion. That fails in both directions: the cushion is margin you handed away on day one if costs stay flat, and it's exhausted by month five if they don't.

A price list is a photograph of your costs on the day you printed it.

Where it actually leaks

Not on the big contracts. Those have owners, renewal dates, and someone watching. The leak is the long tail: thousands of items, times customer-specific prices negotiated years ago, times discount structures layered on top. Any single stale price is too small to notice. In aggregate they are a permanent tax on gross margin — and no one's job is to find them, because finding them by hand means comparing every price to a cost that moved again last week.

So the real design problem isn't “what should prices be.” It's building a loop that notices, queues, fixes, and remembers — continuously, at long-tail scale.

The loop has four parts

1. A sensor at the moment of commitment

Every sales order line — and every quote line, because a quote is a price promise — gets checked against a margin floor over a live cost basis at the moment it's entered. Falling below the floor doesn't block the order; it records a violation and tells the person entering it, right on the record.

The cost basis deserves more thought than it usually gets. Average cost is the natural choice, but it lags on the way up — it still contains the cheaper units you bought before the tariff landed. When costs are climbing, the most honest number you have is what you paid last, so the sensor falls back to last purchase cost where average cost is missing or stale. In a rising-cost world, yesterday's invoice is a better prophet than last year's average.

2. A queue, not an inbox

Alerts that arrive as email get archived; the leak continues. Each violation is written as a record — item, customer, order, entered rate, the cost at that moment, the floor it missed — so the open set is a workable queue with a count that goes down, not a mailbox that fills.

3. An actuator with authority

Someone in sales management works the queue in a console that shows, for each customer and item, how that pair prices — a negotiated contract price, a discount structure, or list — and fixes the price where it actually lives. That distinction matters: raise a discounted customer's target without grossing it up through their discount and you've fixed nothing; raise a list price and you've moved every customer on that item, which is often correct and should always be deliberate. The console's job is to make the mechanics — the gross-up math, the blast radius — visible at the moment of decision, so a sales manager can safely make ten pricing calls in the time a spreadsheet exercise used to take for one.

4. A memory

Every change keeps what the price was before, what it became, who approved it, and when. Partly for the customer conversation — the first question about any increase is “what was it before and when did it change” — and partly because a pricing process you can't audit will quietly stop being trusted, then stop being used.

Small and often beats big and annual

A perpetual loop changes the shape of increases, not just the timing. A series of small adjustments tied to visible cost drivers — a tariff line, a resin index, a freight surcharge — reads as bookkeeping. One 12% shock reads as an opening bid, and gets negotiated as one. Customers who would fight the annual letter accept the 3% moves, because each one arrives with its reason attached.

It also works in reverse, which is where the credibility comes from. When a tariff is lifted or a surcharge rolls off, the same loop that raised the price can walk it back — and a supplier who visibly retreats when costs fall is a supplier whose increases get believed.

The guardrails

A loop with authority to change prices needs restraints as much as it needs power. One odd order is not a trend — a rep who typed over the rate as a one-time favor created an exception to talk about, not a pricing problem to fix, and the system has to tell those apart or it will raise prices on every customer to correct for one. Cost spikes deserve a beat of skepticism before they cascade — a fat-fingered receipt looks exactly like a tariff until someone checks. And every automated suggestion stays a suggestion: a human with pricing authority approves each change, at console speed instead of spreadsheet speed.

The honest summary

Most companies already own the sensor — some report, somewhere, that says which orders shipped thin. What they're missing is everything after it: the queue that persists, the console that acts, the memory that defends the change. A report tells you you're underwater. The loop is what gets you out — and in a world where Washington or the oil market can reprice your inputs between board meetings, out is not a place you arrive at once. It's a place you have to keep steering back to, continuously, with machinery built for exactly that.

Related: four traps in building the repricing console itself, and the freight you quoted versus the freight you paid.