What spreadsheet forecast sharing looks like in manufacturing
Supplier forecast sharing is the regular exchange of expected purchase volumes by part and period, so suppliers can reserve capacity and raw material before firm purchase orders arrive.
Suppliers of castings, molded parts, printed circuit boards and packaging need weeks or months of notice to book capacity and buy material. Most manufacturers give that notice through a monthly spreadsheet export from MRP, sent to a supplier contact by email. When demand shifts mid-month, the file does not. Benchmark data from APQC shows why that matters: among bottom performers, inaccurate demand forecasts cause 49% of expedited orders, ahead of raw material shortages.[1]
Picture a supplier of die-cast housings. In early March the planner emails the forecast. Two weeks later a large customer order doubles April demand for one housing. The planner updates MRP and assumes the supplier will see the PO. The supplier's scheduler is still working from the March file, the tooling is booked for another customer, and the parts ship late by air freight at your cost.
Operations Director
Watches premium freight and overtime climb while the plan on paper says everything was forecast.
"We told them. Why are we flying parts in?"Supply Planner
Spends the first days of each month exporting, formatting and emailing forecasts, then chasing replies.
"Half my week is spreadsheets and follow-ups."Procurement Head
Negotiates with suppliers who say they never saw the change, with no record to prove otherwise.
"Which version did they plan against?"Supplier Account Manager
Receives files in a different format each month and has to guess which lines changed.
"Just tell me what moved."Are your suppliers planning against an old forecast?
Tick every statement that is true today. Three or more means the problem is likely costing you real money.
Six root causes behind forecasts that go stale with suppliers
The spreadsheet is the visible problem. These are the reasons it keeps failing.
The forecast is a snapshot, not a shared record
An emailed file freezes the plan on the day it is sent. Every later change needs a new file, and suppliers rarely know one exists.
No firm and flexible horizons
When suppliers cannot tell which weeks are committed and which are indicative, they either build nothing early or build the wrong thing.
No capacity confirmation loop
The forecast goes out and silence is taken as agreement. Constraints surface only when the order is already late.
Changes are not highlighted
A 40% jump on one part hides among hundreds of unchanged lines. The supplier's scheduler misses it, and so does yours.
Forecast and PO live in different places
Forecasts sit in email, orders sit in the ERP, and conversations sit in inboxes. Nobody sees the forecast, the order and the reply together.
Nobody measures forecast accuracy
Without comparing what was forecast to what was ordered, the same parts miss by the same amount every quarter.
What stale supplier forecasts cost a manufacturer
The cost shows up as expediting, but expediting is only the part you can see on a freight invoice.
APQC benchmarks show top performers spend 3% of their total logistics cost on expediting, while bottom performers spend 10%.[1] The direct costs are premium freight, supplier rush charges and overtime to recover the schedule. The indirect costs are harder to see: planner hours spent exporting and chasing files, extra safety stock held against unreliable supply, lost goodwill with suppliers who are asked to absorb every change, and customer orders that ship late.
Estimate your annual expediting cost
Enter your figures. Nothing is stored or sent anywhere.
The expert playbook: six practices for forecasts suppliers can plan against
These practices work even while you still send spreadsheets. Structure and rhythm come first, tools second.
"At SAP Labs I worked on the Ariba Network, and the lesson I kept seeing was that a document sent is not a document received. A forecast in someone's inbox is a hope. The buyer needs to know which version the supplier saw, what they said back, and what changed since."Md. Kafil, Co-founder and CEO, Zapro. Former senior product specialist on SAP Ariba Network and procurement transformation manager at KPMG.
Send one versioned forecast per supplier
Agree firm, flexible and planning zones
Ask for a capacity response every cycle
Highlight changes above a threshold
Keep forecast, orders and replies together
Measure forecast accuracy and expedite causes
"Every supplier we paid late at Voonik called to ask where their money was, because they had no other way to know. Forecasts work the same way. If suppliers cannot see the latest number without asking, they will plan on the old one, and the cost of that comes back to you as expediting."Daniel Sagayaraj, Co-founder and CTO, Zapro. Previously built and ran supplier onboarding and payments for a 15,000-supplier marketplace at Voonik.
How Zapro keeps forecasts, orders and supplier replies in one record
Zapro ties demand planning, purchasing and the supplier relationship together, so the forecast a supplier received, what they replied and the orders that followed all sit on one vendor profile instead of in email attachments.
| Root cause | Zapro capability | What changes |
|---|---|---|
| Forecast is a snapshot in email | Vendor Management: documents and conversations in one place | Each forecast version and supplier reply sits on the vendor profile, so everyone sees the same current file and its history. |
| No link between forecast and demand | Inventory Management: demand planning and low-stock alerts | Demand planning and stock levels across locations give planners an earlier signal, and alerts warn before a shortage needs expediting. |
| Forecast and PO in different places | Procurement: purchase requests, approval workflows and RFQs without email chains | Orders and quotations run through one workflow tied to the supplier, not through separate threads. |
| No record of supplier commitments | Contract Management: all contracts in one place with version tracking | Forecast horizons and flexibility bands written into agreements are stored and versioned where the team can find them. |
| No visibility of expediting spend | Spend Analytics | Spend by supplier and category surfaces where rush charges and premium freight concentrate. |
Zapro syncs vendor and master data two ways with your ERP and connects to Slack and email, so planners keep working in the tools they already use. See Zapro integrations.
A 30, 60, 90 day plan
Days 1 to 30: Baseline it
- List critical suppliers that receive forecasts
- Tag the last six months of expedites by cause
- Measure forecast accuracy on top parts
- Agree firm and flexible horizons internally
Days 31 to 60: Structure it
- Issue versioned forecasts on a fixed day
- Add a change list for large moves
- Ask critical suppliers for capacity responses
- Store forecasts and replies on supplier records
Days 61 to 90: Tighten it
- Write horizons into supply agreements
- Review accuracy and expedites monthly
- Adjust safety stock where supply is reliable
- Extend the process to the next supplier tier
KPIs to track progress
| KPI | How to calculate | Review |
|---|---|---|
| Forecast accuracy | One minus the absolute difference between forecast and actual orders divided by actual orders, by part family | Monthly |
| Expedite rate | Expedited orders divided by total supplier orders | Monthly |
| Expedite spend | Premium freight and rush charges on supplier orders | Monthly |
| Supplier response rate | Critical suppliers confirming or flagging the forecast within the agreed window | Each forecast cycle |
| Firm-zone changes | Forecast changes made inside the firm horizon | Monthly |
| Supplier on-time delivery | PO lines received by the confirmed date divided by PO lines due | Monthly, by supplier |
Go deeper with our guide to procurement strategy.
What a Zapro customer saw after moving this work into one workflow
"Zapro's strategic sourcing tools have allowed us to negotiate superior contracts and realize significant cost savings."Frank Esmeijer, Vice President Development, Bob W
Why Zapro for this challenge
Stale forecasts are a record-keeping problem that turns into a freight bill. Zapro keeps each forecast, reply and order on the supplier's record, so both sides plan against the same numbers.
The supplier record is the center
Zapro is built around the vendor relationship, so forecasts, contracts, orders and conversations sit together instead of in inboxes.
Planning and purchasing connect
Demand planning, stock levels across locations and purchase workflows share data, so a change in demand is visible where orders are raised.
Fewer email chains
RFQs, quotations and supplier conversations run inside Zapro, which cuts the manual chasing that eats planner time.
Priced for growing manufacturers
Plans start at $699 per month for up to 50 vendors with unlimited users, so planners, buyers and managers can all work in the same record.
When Zapro may not be the right fit
- You need automated forecast transmission by EDI directly into suppliers' MRP systems. Your ERP or an EDI provider is the right tool for that.
- You need full collaborative planning with statistical forecasting and supplier-side capacity modeling. A dedicated supply planning platform fits better.
- You buy from only a few suppliers on stable, long-term schedules. A fixed monthly call and a shared file may be enough.
Frequently asked questions
Why should manufacturers share forecasts with suppliers?
Suppliers need notice to reserve capacity and buy raw material. Sharing expected volumes before firm orders arrive shortens effective lead times, reduces expediting and helps suppliers plan labor and tooling.
What is a firm zone in a supplier forecast?
The firm zone is the near-term window, often the next few weeks, where quantities are committed and the buyer accepts liability if they change. Beyond it sit flexible and planning zones where quantities may move within agreed limits.
How often should forecasts be shared with suppliers?
Monthly is common, with weekly updates for fast-moving or critical parts. The rhythm matters less than consistency, a clear version on every forecast, and a quick flag whenever a large change happens between cycles.
What is wrong with sharing forecasts by spreadsheet?
Nothing, at small scale. Problems appear when files multiply: suppliers work from old versions, changes go unnoticed, replies scatter across inboxes and nobody can prove what was shared. Structure and a single record matter more than the file format.
How do we reduce expediting caused by poor forecasts?
Tag every expedite with a cause, measure forecast accuracy on the parts that expedite most, agree firm and flexible horizons, and ask suppliers to confirm capacity every cycle. Tools such as Zapro help by keeping forecasts, replies and orders on one supplier record.
About the experts behind this page
Sources
Editorial note: this page is published by Zapro, which sells procurement software. Best practices are written to work with any tool, and figures are cited to their original publishers. Last reviewed 29 September 2026; next review due March 2027. See how the Procurement Challenges Directory is researched and reviewed.