In short
- Schedules carry a firm horizon you build to and a forecast horizon you plan material against; treating them the same causes either shortages or excess.
- Revision handling is the real test. A plan that must be retyped on every revision will drift out of date within weeks.
- ASN accuracy matters as much as delivery timing, because a mismatched notice creates receiving problems at the customer plant.
- Delivery rating should be visible continuously, not discovered at month end when it can no longer be recovered.
Firm, forecast and why the distinction matters
An OEM delivery schedule typically contains two zones. A firm horizon covering the near term, which is a committed call-off, and a forecast horizon beyond it, which is planning information subject to change.
Suppliers get into trouble by collapsing the two. Build everything in the forecast horizon and you accumulate finished stock for quantities that later reduce. Treat the firm horizon as provisional and you miss committed deliveries. The correct behaviour is to build to firm and buy material against forecast, accepting that material commitment carries more risk than production commitment.
Our production planning page covers how this splits into a build plan and an MRP horizon.
Handling revision without chaos
Schedules revise. Quantities move, dates shift, and occasionally a part is pulled entirely. The practical question is what happens in your plant when a revision arrives.
In a spreadsheet-driven operation someone compares the new schedule to the old one manually, updates a plan, and hopes nothing was missed. That works until volume or part count grows, then it silently stops working.
What good looks like: the revision is loaded, the system highlights what actually changed, new shortages are flagged, affected work orders are identified, and commitments that are now at risk surface immediately. The planner spends their time deciding what to do rather than working out what changed.
See how this runs on your own part numbers, schedule to dispatch.
ASN and labelling accuracy
An advance shipping notice tells the customer what is arriving, in what quantity and packing configuration, before it physically arrives. Their receiving process depends on it matching reality.
Common ASN failures and their consequences:
| Failure | Consequence at customer |
|---|---|
| Quantity mismatch | Receiving discrepancy, investigation, possible rating hit |
| Wrong packing configuration | Manual re-count and handling |
| Label format not to spec | Scan failure at goods-in |
| ASN sent after arrival | Defeats the purpose entirely |
| Wrong part revision | Potential quality escape |
Raising the ASN from actual dispatch data rather than from an intended dispatch removes most of these, because what is notified is what was packed.
Protecting the delivery rating
Delivery rating is usually calculated over a rolling period, which means a bad week has a long tail. That has a practical implication: recovery is far cheaper than repair. A shortfall spotted three days before the due date can often be recovered with overtime or a partial early shipment. The same shortfall discovered on the due date usually cannot.
This is why continuous visibility matters more than accurate month-end reporting. Practical measures:
- Promised versus projected, updated as production progresses.
- Alerts when projected output for a committed date falls behind.
- Material shortage flags tied to specific committed deliveries.
- Rating exposure by customer, visible before the period closes.
Our OEM supplier page covers how this is normally surfaced.
Want a fixed-scope ERP plan for your Hosur plant?
Passing the signal upstream
Most Hosur suppliers are themselves customers of smaller Tier-2 vendors and job workers. The same discipline applies upstream: issuing a schedule to a vendor rather than placing ad hoc orders lets them plan, which improves your inbound reliability more than pressure does.
Sharing a rolling horizon with key vendors is usually the single highest-return supply chain change available, and it costs nothing but the willingness to share planning information. See vendor management.
Key Takeaways
- Build to the firm horizon and buy material against forecast; collapsing the two causes either shortage or excess.
- Revision handling is the real test of a system; manual comparison stops working as volume grows.
- Raise the ASN from actual dispatch data so what is notified matches what was packed.
- Delivery rating recovery is far cheaper than repair, which makes continuous visibility more valuable than accurate month-end reporting.
- Issue schedules to your own Tier-2 vendors so they plan rather than react.
Frequently Asked Questions
The firm horizon is a committed call-off you build to. The forecast horizon is planning information subject to change, which you buy material against while accepting more risk.
The system should load the revision, highlight what actually changed, flag new shortages and identify affected commitments, so the planner decides what to do rather than working out what changed.
An advance shipping notice tells the customer what is arriving before it does. Their receiving process depends on it matching reality, so quantity or configuration mismatches create discrepancies and rating exposure.
Typically over a rolling period, which means a bad week has a long tail. Confirm the specific method with each customer, since definitions vary.
Because a shortfall spotted days before the due date can often be recovered, while the same shortfall discovered on the due date usually cannot.
Yes. Each customer format is mapped once and converted into the same internal build plan and material demand, so planners work with one consistent view.
Generally yes for key vendors. A vendor who can see your horizon plans instead of reacting, which improves inbound reliability more than expediting pressure does.
Material availability far more often than production capacity, which is why inbound reliability and MRP accuracy deserve more attention than shop-floor speed.
Yes. Customer-specific label layouts and ASN structures should be configured once and applied automatically, since scan failures at goods-in create the same problems as a late delivery.
Material availability and revision response typically improve within one or two planning cycles once schedules drive the plan directly rather than being retyped.
Conclusion
Handling OEM delivery schedules well is one of the highest-leverage capabilities an auto-component supplier can build, because it touches delivery rating, inventory and cash simultaneously. Split firm from forecast and treat them differently. Make schedule revision an event the system absorbs rather than one a planner reconstructs. Raise ASN from actual dispatch so notification matches reality. Watch rating exposure continuously so shortfalls are recovered rather than reported. And pass the same discipline upstream to your own vendors, because inbound reliability is where most delivery problems actually originate.
Want schedule revisions absorbed instead of retyped?
Talk to our Hosur team, or book a free demo and see it on your own part BOM.