Why the link between production planning and procurement so often breaks down
Most ERP systems offer a connection between production planning and procurement. Yet in practice, that connection rarely works as smoothly as the demo promises. The reason is almost always the same: the link is technically present, but the data behind it is not current enough, not complete enough, or is bypassed by people because the system responds too slowly to changes. As a result, the planner starts working manually, the buyer relies on their own overviews, and a silent gap opens up between what is planned and what has actually been ordered.
Break 1: a planning change does not reach the purchase order
The first pattern appears when a customer order shifts or a production order is postponed. The planner adjusts the schedule. But the purchase order already placed remains unchanged. The system has not automatically propagated the change, or the buyer missed the notification in an overcrowded task list. The result: material arrives on the original date while production is scheduled three weeks later. Storage fills up, or the material quietly disappears into another order. This is not purely a system issue; it is also a question of agreed workflow. Which system governs the planning? Who initiates the change in the purchase order? Until that is clear, no automatic link will help. What you can automate is an alert that actively notifies the buyer whenever a planned date shifts by more than a defined number of days, so a decision can be made. Not automatically adjusting the purchase order, because the context is too complex for that. But providing the signal that action is needed.
Break 2: lead times in the ERP are not current enough
The second break lies in lead times. In most systems we encounter, lead times are static fields: entered when a supplier or item was created, and not systematically maintained since. The planner calculates with four weeks for a particular material, while the supplier has been running at six weeks for months. That two-week difference only surfaces when the production date approaches and the material is not there. Retrieving real-time lead times from a supplier portal or via EDI is technically possible, but requires an investment in integration and also demands that suppliers have their side of the connection in order. That is far from always the case, particularly with smaller subcontractors. A more realistic first step: systematically tracking lead times per item based on historical receipt data already in the system. If you have three years of purchase orders and goods receipts, you can calculate a reliable average lead time per item and update it periodically. It is not real-time, but it is better than a static figure from 2021.
Break 3: a material shortage only becomes visible when switching is no longer an option
The third break is the most painful. The production order is scheduled for next week. On Monday it turns out that a critical component is out of stock and can no longer be delivered in time. The production line stops, or work switches to a different order that requires other materials in turn, shifting the problem rather than solving it. This problem arises because shortages only become visible at the point of issue, not at the point of planning. A working link between production planning and procurement starts with a net requirements calculation that takes place early enough: not once the order has already started, but at the moment it is scheduled. That sounds obvious. In systems where planning and inventory information live in different modules or even different systems, it is not. We regularly see planners working in a planning module that does not communicate live with the inventory data in the ERP. The planner sees an availability percentage that is only updated overnight. By the time a shortage becomes visible, all suppliers are already at maximum capacity.
What a better link between production planning and procurement realistically delivers
Anyone expecting a better system integration to resolve all three breaks at once will be disappointed. The technical link is relatively quick to build: an alert for planning changes, a calculation of current lead times based on historical data, a net requirements check that runs at the point of scheduling. What takes more time is the organisational side: clearly agreeing on who acts after a notification, which system is authoritative, and how exceptions are handled. With the manufacturing companies we work with, we always start by asking where the pain is greatest. Sometimes it is the silent planning change the buyer misses. Sometimes it is the overly optimistic lead time. Sometimes it is the late visibility of shortages. The order matters. You will not solve the shortage problem by improving lead times first if the planning change is not being communicated in the first place. Build the link step by step, start with the break causing the most disruption, and ensure that people make decisions based on a clear signal rather than having the system automatically adjust purchase orders without context.