The Price Increase You Already Agreed To
A PDF landed on Tuesday. Subject line: 2027 Price Adjustment Notification. It is from Brenmark Tool, one of your larger vendors, and it runs two pages. Four point nine percent across three product families, effective January 1. There is a paragraph about input costs and a sentence thanking you for your partnership.
Purchasing opens it, notes the date, and drops it in the shared drive folder where these live. Somebody will update cost in the ERP closer to the effective date. That part usually happens.
Here is what does not happen. Nobody walks the letter across to the three places it actually matters, and two of those places have deadlines that expire before the increase ever takes effect.
The reflex is to say purchasing should have flagged it, which is fair, because the letter was addressed to purchasing and reads like a purchasing document. It talks about your cost. So it gets filed where cost lives. But an increase notice is a sales document in a purchasing envelope, and there is nobody at most companies whose job is to route it that way.
Why a 4.9% Letter Becomes a Margin Problem
Start with what a single point of price is worth. McKinsey's April 2026 analysis of B2B pricing puts it at the number pricing teams quote from memory: a 1 percent price increase translates into an 8.7 percent increase in operating profits, assuming no loss of volume. That multiplier is the entire argument for having a pricing function. It also runs in reverse, which is the half nobody says out loud. A point of price you absorb instead of passing through does the same 8.7 percent of damage, just to the other side of the ledger.
Now the lag. Intuilize, a pricing analytics firm that benchmarks distributors, puts the typical gap between a vendor cost increase and the matching customer-facing price update at two weeks, and pegs average margin erosion from that delayed response at 1.6 percent. Hold that against operating margins in this business, which run 3 to 4 percent. Delayed cost response alone eats something like a third of the operating margin, every year, without ever appearing as a line item. One $45 million distributor they worked with documented $250,000 in annual losses from delayed updates on 7 percent of its catalog.
And two weeks is the good case. Two weeks is the gap when somebody is actively working the file. The letter that arrives in August with a January date does not get two weeks of lag. It gets five months of being nobody's problem, then a scramble in the first week of January when the vendor invoices come in higher than the POs.
The repricing you can still fix late. The clause deadline and the honored quote you cannot. Those two expire on their own schedule, and they expire quietly.
This Week, Try This: The Letter Sweep
Different raw material this week. Not an ERP export. The letters themselves.
Pull every increase notice you have received in the last 90 days. They are sitting in a purchasing inbox, a shared drive folder, or both, in every format a vendor can produce: a PDF letter, a scan of a letter, plain text in the body of an email, a spreadsheet of affected part numbers with no explanation attached. That variety is the reason nobody has ever tabulated them by hand. It is also the reason this is a good job for a language model.
Then three things to check them against, ordered by what they are worth:
- Current sell price by SKU. One ERP export, one line per item.
- Your contract list. The clause text if you can get it, and if you cannot, at least which agreements exist and when they renew.
- Open quotes with their expiration dates.
Get the first one and you can run this today. Get all three and it names your January exposure to the dollar. Attach what you have with the prompt below.
You are analyzing supplier price increase notices for a
manufacturer or distributor. The attached files are the
increase notices received in the last 90 days, in mixed
formats: PDF letters, scans, email text, and part-number
spreadsheets. Additional files may include a sell-price
export, a contract list, and open quotes.
STEP 1 - NORMALIZE EVERY NOTICE INTO ONE TABLE:
- Vendor
- Date received, and the date on the notice if different
- Affected products at whatever level the letter states
them: SKU, part number, product family, or whole line
- Increase, as a percentage and as a dollar amount where
the letter gives one
- Effective date
- Any notification or acceptance deadline the letter
imposes on us
- Tiering, exclusions, or conditions, quoted verbatim
- Whether the increase applies to orders placed before
the effective date or only to orders placed after
STEP 2 - IF A SELL-PRICE EXPORT IS ATTACHED:
- Match affected items to current sell prices
- Show current margin and margin after the increase,
assuming sell price does not change
- Rank affected families by annual margin at risk, using
the last twelve months of volume if it is provided
- Flag every item where the new cost meets or exceeds
the current sell price
STEP 3 - IF A CONTRACT LIST IS ATTACHED:
- List contracts covering affected items
- For each, state whether a material cost pass-through
clause exists, and quote it
- Where a clause sets a notice period, count backward
from the effective date and give the date we must
notify by
- Put contracts with no pass-through clause in a separate
list. Those are absorbed increases, not negotiations.
STEP 4 - IF OPEN QUOTES ARE ATTACHED:
- Flag every quote whose validity window extends past an
effective date affecting any line on it
- Show margin at the quoted price against the post
increase cost
- List separately any quote that would be sold at or
below new cost if it were accepted
RULES:
- Quote effective dates and deadlines exactly as written.
Never round or infer a date.
- If a letter names a product family rather than SKUs,
say so and name the family. Do not guess what is in it.
- If a letter is ambiguous about scope or timing, put it
in an UNCLEAR list with the ambiguous sentence quoted.
Do not resolve the ambiguity yourself.
- Never estimate a percentage the letter does not state.
- Costs and prices come only from the attached files.
No market assumptions.
What comes back is a table nobody at your company has ever built: every announced increase, normalized, with an effective date and a dollar figure next to it. Then three action lists. Which SKUs to reprice and by when. Which contracts carry a pass-through clause, with the notification deadline counted backward from the effective date. Which open quotes should not be written past December at this year's cost.
Work the notification deadlines first. They are the only items on the list with a hard expiration, and a 60 day notice on a January 1 increase cannot be given in December.
First run takes under an hour, and for once almost none of that is waiting on an export.
An Honest Take
The price increase letter is the most under-read document in distribution. It arrives addressed to the person who pays the vendor, so it gets handled as an accounts payable event, and the only question anybody asks is whether the increase is negotiable. I think that is the least valuable question in the letter. The valuable question is which of your own commitments the letter just broke, and answering it requires reading the letter next to your contracts, which nobody does because those two documents live in different buildings.
And while we are here, quote validity windows. Most companies default to 30 or 60 days because that is what the template said in 2011. If you sell anything with volatile input costs, a quote that stays live across a known cost change is an option you handed the customer for free. If I could change one habit, I would put a cost-change clause in the standard quote template and stop thinking about it. But I would settle for a rule that no quote gets a validity window crossing January 1 unless somebody priced it at next year's cost.
The Bottom Line
The letters are arriving right now. That is the whole reason this is worth an hour in August instead of an hour in January. Every notice you have received in the last month has an effective date about five months out, a set of your own contracts and quotes it quietly conflicts with, and a notification deadline that probably falls in the fall.
Read them together and the exposure is a list you can work. Read them one at a time as they arrive, which is what happens now, and January does the reading for you.
The letter got filed because reading it was somebody's manual job.
Same failure mode as a PO sitting unread in an inbox for four hours. A document arrives as email, and it waits until a person reads it, interprets it, and gets it into your system correctly.
Y Meadows does that for order entry: inbox pickup to ERP posting, matching customers and SKUs, applying your pricing and credit rules. Want to see it run on documents like yours?