Pass cost increases on to price on time: stop margin erosion in high inflation
Margin erosion in an inflationary market rarely comes from one bad pricing decision. It comes from delay: the supplier raises the price on the 1st, the new invoice lands on the 5th, and your selling price changes on the 20th, if someone notices at all. In between, you sell goods at a price set for the old cost, and each sale funds less of the next purchase.
The leak is hard to see because the margin report looks fine. Most ERP margin reports use book cost, an average of what you paid for the stock on hand. While old, cheaper stock is still being sold, the reported margin stays healthy. By the time the average catches up, the old stock is gone, and you have sold it at a price that does not pay for its replacement.
Where the margin leaks when costs rise faster than prices
In retail, wholesale and manufacturing, the mechanics are similar. The cost signal arrives in one place, and the price decision is made somewhere else, later:
- Price update lag: cost increases arrive through invoices, supplier price lists or e-mails, while selling prices are reviewed monthly or when a category manager has time.
- Averaged cost hides replacement cost: weighted average cost blends cheap old stock with expensive new stock, so the price looks sufficient when it is not.
- Fixed commitments: dealer price lists, customer contracts and campaign prices set weeks in advance keep old prices alive after costs move.
- Indirect costs left out: freight, energy, packaging and currency-linked costs rise but never reach the product cost used for pricing.
- Quotes on old costs: in manufacturing and project sales, offers are prepared with last month's material costs and accepted after costs have risen.
- Uneven updates: the thousands of SKUs nobody reviews individually, the long tail, keep old prices the longest.
How to measure margin erosion from late price updates
The basic formula: margin lost to lag = cost increase per unit × units sold between the cost increase and the price update. Run it per SKU or product line for each cost change in the last six months, and you have both the size of the leak and your real price update lag in days.
Illustrative example (hypothetical, round numbers): a distributor sells 10,000 units a month of a product line with a unit cost of 100 TL. The supplier raises the cost by 8% on the 1st, to 108 TL. The new selling price goes live on the 21st, 20 days later. Roughly 6,700 units are sold in that window, so 6,700 × 8 TL = 53,600 TL of margin is given away on one line in one cycle. If the same pattern repeats six times a year across 20 lines of similar size, the total reaches about 6.4 million TL. The exact figure matters less than the lag, which is the number you can manage.
Why margin reports and ERP miss cost-increase leakage
- They report book cost, not replacement cost: the margin looks right on paper until the old stock runs out.
- Aggregates hide the tail: category margin can look stable while hundreds of SKUs sell below target.
- Purchasing and pricing are separate: the buyer sees the new cost, the pricing team sees the old margin, and no system connects the two on the same day.
- Cost information is unstructured: supplier price lists arrive as PDFs and e-mails, so they reach the ERP only when the invoice is booked.
- Manual repricing does not scale: updating prices for thousands of SKUs in spreadsheets happens in batches, never continuously.
How an AI-agent approach keeps prices in line with costs
An AI agent watches the cost side every day. It detects: it compares each new purchase cost or supplier price list with current selling prices and flags every SKU whose margin on replacement cost has fallen below its category floor. It diagnoses: which supplier or cost component drove the change, how much stock at the old cost is left and for how many days it covers sales, and how the item's sales responded to earlier price changes. It assigns: it prepares a proposed new price, rounded to your price points and checked against channel rules, and sends it to the category or pricing manager for approval. Only approved prices go to the ERP, and label-change tasks go to the stores. It measures: realized margin on replacement cost and volume after the change, so the next proposal is better calibrated.
Data needed: purchase invoices and orders, supplier price lists, sales and stock by SKU, current prices by channel, target margins, and exchange rates where costs are currency-linked. With Zzeti, supplier price lists can be read as collections, so a new PDF list is compared with current prices before the first invoice arrives. The agents run on your own infrastructure, so cost and margin data, among the most sensitive in any company, stay inside it. Price proposals wait in the Actions Inbox; the agent never changes a price without human approval.
A 4-week pilot plan for inflation-proof pricing
- Week 1: choose two or three categories or suppliers with frequent cost changes. Agree on target margins per category, calculated on replacement cost.
- Week 2: measure the baseline: price update lag for every cost change in the last six months, and margin lost with the formula above.
- Week 3: switch on daily price proposals for the pilot scope. Pricing managers approve, adjust or reject each one, with a reason.
- Week 4: compare lag, realised margin and volume against the baseline, review rejected proposals, and decide on the next categories.
Pricing and margin KPIs to track in high inflation
- Price update lag: days from cost change to live selling price.
- Share of sales below target margin on replacement cost.
- Gross margin on replacement cost versus book cost.
- Estimated margin leakage in TL per month.
- Volume change after price updates, by category.
- Approval turnaround time for price proposals.
In inflation, the price update lag is the margin leak. Measure it in days, price on replacement cost, and make every cost increase trigger a pricing decision someone approves.
Frequently asked questions
How do I pass cost increases on to customers without losing them?
Move quickly on items where customers are less price-sensitive and hold prices on the few key items they compare. Stagger increases rather than making one large jump. For business customers, clear notice periods in contracts help.
Should I price on replacement cost or purchase cost during inflation?
For pricing decisions, replacement cost: what it will cost you to buy the item again. Accounting keeps its own cost method; the point is not to let averaged book cost set your selling price.
How often should prices be updated in high inflation?
Let cost changes trigger reviews rather than a fixed calendar. A monthly review cycle means up to a month of lag on every increase. Items with frequent cost changes need daily monitoring, even if prices change less often.
Is cost-plus pricing enough in an inflationary market?
Cost-plus is a useful floor, but only if the cost is current. Combine a margin floor on replacement cost with market and demand signals, so you neither lag costs nor overshoot what customers will pay.
Pass cost increases on to price — on time
Zzeti tracks cost, demand and price together, lists the products whose margin is eroding and those with room to price, and proposes prices together with the reasoning and the query behind them.