The assembly line shutdown schedule for the next quarter is already posted on your Tier-1 customer's supplier portal. Your demand plan does not use it. It continues to project next month's parts requirement from the last 12 months of shipments, then adds a safety margin. The line will stop for Golden Week, but your reorder point does not know that.
This is not an unusual planning failure. I have seen the same gap repeatedly while managing supplier operations for high-mix automotive parts programs. The MRP logic is often working as configured. The problem is that the configuration is answering a narrower question than the operations team needs answered.
It calculates what was ordered, what was shipped, and when replenishment should be triggered. It does not necessarily account for what the assembly plant will pull next week, which model is changing over, or when a customer plant will be closed. Those inputs sit in different systems, portals, spreadsheets, and email notices. The demand plan often sees none of them.
The shipment history is useful, but incomplete
Historical shipment data has a legitimate role in demand planning. It shows recurring order patterns, baseline volume, customer behavior, and the effects of normal variability. For a stable part with a consistent program and no major schedule changes, shipment history can provide a reasonable starting point.
The issue is what shipment history cannot capture. A shipment is the end of a sequence. It reflects what a supplier delivered after orders were released, adjusted, delayed, expedited, or held. It does not always represent the plant's actual consumption requirement at the time the part was needed.
A shipment record also tends to flatten important operational differences. A monthly total can look normal even when the daily pull pattern has changed. A part may have shipped the same quantity as last year, but in a different sequence because of a model changeover. Another part may show a recent spike because a supplier built ahead of a shutdown. Treating both patterns as ordinary demand can distort the next reorder decision.
Safety stock helps absorb uncertainty, but it does not identify the source of that uncertainty. If the problem is a known line stop, more stock is not a better forecast. If the problem is a scheduled model change, a generic buffer does not tell the planner when the old part number should fall and the new one should rise.
Four inputs that are often outside the plan
1. The assembly plant pull schedule
The pull schedule is closer to the actual production requirement than a shipment total. It shows the sequence and timing that will drive kanban cards, releases, and consumption at the line. Yet the schedule may remain inside the assembly plant's ERP while a Tier-2 supplier plans from a customer order file.
That separation matters. A supplier can see a firm order horizon and still miss a change in the pull pattern beyond it. The result is a plan that looks stable until the next schedule revision arrives. By then, material may already be in transit, capacity may already be committed, or a premium freight decision may be unavoidable.
2. Model changeover dates
A model changeover is not simply a small adjustment to average demand. It can change the mix of parts, the timing of releases, and the usable life of material already in stock. A forecast built from prior shipments may continue the old pattern because that is the pattern with the most history behind it.
For a supplier carrying several variants, the effect can be easy to miss. One part number declines gradually while another rises. The total program volume may appear unchanged, but the supplier is exposed to the wrong inventory. The parts master list and the scheduled change date need to be read alongside the historical order pattern.
3. Planned shutdowns and holidays
Golden Week, summer shutdowns, year-end closures, and customer-specific line stops are known events. They should alter the timing of replenishment and production, even when the annual demand total does not change.
Without those dates in the planning inputs, a supplier may build toward a normal week that will not occur. Or it may interpret a post-shutdown surge as unexpected demand when the plant is simply catching up. A safety stock rule can soften the result, but it cannot distinguish a planned closure from an actual increase in consumption.
4. Standing order deviations
Many supplier relationships have a familiar order rhythm. A part is usually called off at a similar interval and quantity, so the planner learns to expect the next release. That pattern is useful until the latest pull schedule departs from it.
The important question is not only whether the order arrived. It is whether the order deviated from the standing pattern and whether the deviation is likely to persist. An exception process should flag that change for review instead of allowing it to disappear into a revised weekly total.
What the gap looks like in practice
Consider a Kanagawa-area supplier producing several high-mix stamped and molded parts for an assembly program. Its demand plan uses 12 months of shipment history, current open orders, lead times, and a fixed safety stock rule. The supplier also receives advance schedule notices from its customer, so the team is not planning blindly.
In April, the customer posts a Golden Week line stop and a revised pull sequence for the week after the shutdown. The notice is reviewed by the account team, but the dates are not entered into the demand planning file. The MRP run continues to treat the first week of May as a normal production period.
The supplier produces against the usual reorder point. Finished goods accumulate before the closure, while a different part with a longer lead time is not advanced because its order history has not yet changed. After the line restarts, the pull schedule increases for the second part and falls for the first. The supplier now has stock in the wrong place, a compressed production window, and a new reason to question the safety stock settings.
Nothing in this example requires a bad forecast formula. The issue is that the plan did not include the event that determined the shape of demand. The shutdown schedule and pull sequence existed. They were simply not connected to the planning logic.
Some suppliers already have part of the answer
It is important to acknowledge what suppliers are already doing right. Many receive advance schedule notices, customer forecasts, kanban signals, or weekly call-offs. Experienced planners compare those notices with open orders and use judgment to adjust production. Some teams maintain separate calendars for shutdowns and model changes.
That work reduces risk. It also reveals the remaining gap. When the inputs are handled manually, they may not reach every part number, every tier, or every weekly planning run. One person may know that a model change is coming while the reorder point continues to use the old pattern. A schedule notice may be visible to a Tier-1 supplier but not passed clearly to a Tier-2 supplier that needs to reserve material and capacity.
Manual review is also difficult when a supplier manages many variants. The question is not only whether a notice exists. It is which SKUs it affects, when the effect begins, how long it lasts, and whether the observed order change is different enough from the standing pattern to require action.
That is where a connected input set is more useful than another blanket buffer. The planning process can retain shipment history while adding the signals that explain future movement.
A more complete weekly planning input
At Lean Path, we read the assembly plant daily pull schedule from ERP together with the parts master list, lead times, 24 or more months of historical order patterns, scheduled plant shutdowns, and model change dates. The purpose is not to discard the supplier's existing MRP process. It is to give the forecast the operational context that shipment history alone cannot provide.
Lean Path generates tier-specific demand forecasts weekly and flags deviations from standing order patterns as exceptions. That gives an operations team a way to review the parts where the current pattern is changing, rather than treating every SKU as equally uncertain.
For design-partner suppliers, the engagement can track up to 15 SKUs over 8 weeks. That scope is useful for testing whether the relevant inputs are available, whether the exception signals match planner judgment, and whether the forecast is addressing a real gap in the current process. It is not a replacement for understanding the plant schedule or the supplier's own constraints.
The practical test is straightforward. Take a part with a known shutdown, a model change, or a recent pull deviation. Compare the plan built from shipments and safety stock with a plan that also includes the daily pull schedule, lead time, calendar events, and changeover date. Then ask which plan gives the production team a clearer reason for the next action.
Adding these inputs changes the planning conversation from "How much did we ship last year?" to "What is scheduled to be pulled, what is changing, and which part numbers need attention this week?" Historical shipments still establish the baseline. The added schedule and calendar signals show where that baseline no longer describes the operation.
If your team wants to examine this on a limited set of parts, contact us at [email protected] or +81 3 6435 2170. We can start with the schedules, part data, and known dates already used by your operations team.