Suppose a supplier raises prices 7% in July. Finance applies that increase from January. Six months of extra costs have appeared without a single additional purchase order. The spreadsheet is certainly looking ahead. Perhaps a little too far.
To forecast supplier price increases in budgets, start with the rate actually payable, the month it changes, the quantity the business expects to purchase, and the date cash leaves the bank. A blanket inflation assumption is useful for a first-pass sensitivity test. It is a poor substitute for a contract schedule.
1. Separate contracted prices from exposed spending
Split the supplier base into fixed-price agreements, index-linked contracts, pending renewals, and uncontracted purchases. For each meaningful category, record the current rate, contract expiration, notice terms, minimum purchases, and who owns the supplier relationship.
The critical number is spend exposed to repricing, not total annual purchases. If 70% of a category is fixed through September, applying a January increase to all of it inflates the forecast before the supplier has the right to change the rate.
2. Put the increase in the correct month
Consider a hypothetical company with $8 million of annual supplier purchases at current prices, spread evenly throughout the year. Forty percent of that spend is subject to a 5% increase from January. The other 60% is fixed until July, when a 7% increase takes effect.
At unchanged purchase volumes, the first group adds $160,000 for the year ($8 million × 40% × 5%). The second adds $168,000 ($8 million × 60% × 7% × six months / twelve). Total incremental purchase cost: $328,000.
Applying both increases for twelve months would produce $496,000. That is the annualized increase once both new rates apply, not the cost of this budget year. The $168,000 gap is a timing error disguised as precision.
3. Forecast units and mix before calculating price
Price increases do not operate on last year’s purchasing pattern unless the business plans to buy exactly the same things in exactly the same quantities. For each significant input, calculate planned units × expected unit cost, then sum across the mix.
Operations may be reducing scrap, shifting to another material, or adding a product that consumes more expensive inputs. Those changes belong in the volume and mix assumptions. Keep them separate from supplier price movements. Otherwise a 6% spending increase can be blamed on inflation when half of it came from buying more units.
Finance already makes this distinction on the revenue side. The same discipline should apply to purchasing; the logic is familiar from separating price, volume, and mix in a revenue model.
4. Use market indexes as evidence, not purchase orders
The Bureau of Labor Statistics Producer Price Index tracks changes in selling prices received by domestic producers. That makes a relevant, narrowly selected PPI series a useful signal for some U.S. supplier categories. It does not establish what a particular customer will pay under a particular contract.
For imported goods, the BLS also publishes import price indexes. Neither series replaces a confirmed quote, agreed escalation formula, or assessment of freight and currency exposure. Match the index to the actual input where possible, document the gap, and use a range when the link is weak.
Using an economy-wide inflation rate to forecast a specialty component is convenient. So is using the weather forecast to approve a factory maintenance budget. Both skip a fairly important middle step.
5. Reconcile the full delivered cost
A quoted unit-price increase is only part of the change. Test freight, fuel or energy surcharges, duties where applicable, rebates, volume discounts, minimum-order requirements, and foreign-exchange terms. Confirm whether those charges are already included in the base forecast. Double-counting a surcharge can make a supplier appear expensive twice.
For each category, keep a simple bridge from prior expected cost to revised cost: rate change, quantity change, mix, and separately identified landed-cost items. Procurement should be able to reconcile the assumptions to actual contracts and purchase orders. FP&A should be able to explain them to the CFO without opening twelve unrelated workbooks.
6. Test margin and cash on their own timelines
An increased purchase price can affect cash when the supplier is paid, inventory value when goods are acquired, and cost of goods sold when the inventory is sold. Those dates need not coincide. A service business may have a different expense pattern. Match the forecast treatment to the transaction rather than forcing every supplier change through the same monthly expense line.
Then test pricing power. Can the business raise customer prices, change the product mix, renegotiate volume commitments, qualify another supplier, or absorb the cost? The answer depends on competitive and operational evidence. Do not assume a supplier increase can simply be passed through at the same percentage.
7. Give each forecast change an owner and a decision rule
Assign Procurement to validate contractual rates and renewal dates, Operations to own usage and substitution assumptions, and FP&A to maintain the margin-and-cash bridge. Require an explicit decision when a proposed supplier increase crosses a materiality threshold chosen for the business.
That decision might be to renegotiate, change purchase timing, update customer pricing, or accept lower margin for a defined reason. Track whether the action happened. The monthly variance review should lead to a decision, rather than another explanation of why purchasing costs were higher than forecast.
The useful output is a dated supplier-cost schedule with named owners and a margin and cash sensitivity—not an inflation assumption that somehow applies to every purchase on January 1. If that forecast needs rebuilding, The Schlott Company’s budgeting and forecasting work can help turn purchasing inputs into assumptions management can actually challenge.