Why is passing on cost price increases so difficult?
The answer you hear in the boardroom is: "the customer will not accept it." But when you look one level deeper, the real picture is different. At the moment of quoting, the salesperson does not know the current purchase price of a raw material. The calculation in the ERP is based on a price from three months ago. The associated labour costs are estimated using a standard derived from a different production configuration. By the time the cost price change has been worked through internally, the quote has already been sent or the order is already in production. That is not a commercial problem. It is an information problem.
What pattern keeps recurring in manufacturing companies?
In many manufacturing companies, purchasing data, production planning and commercial calculations live in three separate systems that rarely update each other in real time. Purchasing works in a procurement module or even a spreadsheet. Production works with work orders in a MES or a customised ERP screen. Sales works with a quoting tool connected to a product catalogue that is updated periodically, sometimes manually. That triangle means the actual cost price is only truly known after the project or production run is complete. And by then, it is too late to pass it on.
What sets companies that do manage it apart?
Companies that consistently pass on cost price increases all have one thing in common: their calculation draws live on the current purchase price, not on a fixed standard. That sounds simple, but it requires purchasing, production and sales to work from the same data source. As soon as a supplier provides a new price, the system applies it directly to the cost price build-up of all active quotes and orders. The salesperson sees the revised margin before confirming a price, not after. That gives them the opportunity to have the conversation with the customer at the right moment, with the right substantiation.
When is a new system the answer, and when is it not?
Not every company needs to replace its core system to solve this. If the ERP structure is sound but the connection between purchasing and calculation is missing, an AI Worker that processes purchase invoices and supplier messages and writes directly back to the cost price record is already a significant step forward. But if the calculation logic is spread across dozens of spreadsheets running alongside the ERP, building a standalone integration is essentially treating the symptom rather than the cause. In that case, it is better to rebuild the calculation core from scratch, AI-native, so that the connection between purchase price, actual consumption and commercial price is built in from the start. The choice depends on where the noise originates: in the data flow or in the system logic itself.
What does it actually deliver when you have this properly in place?
You do not need to make a major leap to feel the impact. Simply eliminating the delay between a purchase price change and its processing in quotes produces immediate, visible margin gains. Salespeople no longer have to guess at the cost price; they can quote with confidence. And in customer conversations about price adjustments, you have a concrete basis rather than a vague reference to market conditions. That makes passing on cost price increases far less a matter of internal politics, and far more a straightforward business reality.