Weekly Demand Forecast & Replenishment Workflow

Purpose

This workflow helps kitchen, purchasing and operations teams match stock and prep to anticipated demand each week. Use it to reduce stockouts on busy service periods and excess spoilage on slow periods by combining short-term signals (POS, reservations, weather), known events, and simple reorder rules into clear decisions and communications.

Who should run it

• Owner / Manager: final approvals, exceptions
• Shift Lead / Kitchen Manager: prepares forecast inputs, sets prep volumes
• Purchasing / Buyer: converts recommendations to POs and confirms deliveries
• Front-of-house lead: shares reservations, private events, expected covers

Inputs (what you need before the weekly meeting)

• POS sales history by item and time-of-day for the past 4–8 weeks (daily granularity)
• Open reservations / private events calendar for the coming week
• Local events (sports, festivals, holidays) and expected attendance
• Short-term weather forecast (high/low and precipitation)
• Current on-hand inventory and outstanding purchase orders
• Supplier lead times, minimum order quantities, and delivery days
• Planned promotions, menu changes, or catering orders

Recommended forecast horizons

• Operational / Prep horizon (0–2 days): used to set daily prep quantities and mise-en-place.
• Near-term horizon (3–7 days): used to place short lead supplier orders and finalize staffing & prep plans.
• Procurement horizon (8–28+ days): used for suppliers with longer lead times, bulk buys, and seasonal planning.
• Tailor horizons by SKU perishability. Perishables (produce, fresh proteins) rely more on 0–7 day signals; dry goods and packaging can be planned on longer horizons.

Weekly workflow — step by step

1. Prepare (no later than 48 hours before meeting)
   • Export last 4 weeks of POS by item and service period.
   • Pull inventory snapshot and list of outstanding POs.
   • Collect reservations and events for the coming week.
   • Note any planned menu changes, specials, or promotions.
2. Forecast meeting (30–60 minutes)
   • Review headline signals: bookings, events, supplier issues, weather.
   • For each high-impact SKU or menu category, propose a baseline forecast using recent POS (e.g., average of same weekday over last 4 weeks adjusted for trend).
   • Apply adjustments (see simple rules below) for events, weather, or promotions.
   • Agree on prep volumes (days 0–2) and reorder quantities (3–28 days) by SKU class: perishables vs staples.
3. Set reorder recommendations and orders
   • Convert agreed reorder suggestions into clear action: PO quantities, order by date, alternate suppliers if needed.
   • Include delivery date windows and who will receive/check deliveries.
   • Purchasing confirms when orders are placed and expected arrival.
4. Communicate to teams
   • Publish daily prep sheets for cooks (quantities per service, any special handling).
   • Notify front-of-house of menu availability or limited items.
   • Flag high-risk items (short lead, high spoilage) for daily review.
5. Execute and monitor
   • During the week, track real-time sales vs forecast for key items and flag >20% deviations.
   • If an unexpected spike occurs, use contingency rules (emergency order, cross-utilize ingredients, temporary menu adjustment).
6. Reconcile (after week ends)
   • Compare forecast vs actual sales and compute simple accuracy metrics (see KPIs).
   • Record spoilage and stockouts by SKU and reason.
   • Capture lessons and adjustment factors to feed the next week’s forecast.

Simple demand-adjustment rules (practical heuristics)

• Event uplift: small internal event = +10–25% to expected covers for affected shift; large public event = +50–200% depending on expected draw. Use conservative numbers until you calibrate.
• Reservation override: if confirmed reservations exceed normal covers by X, increase prep for high-turn items by the ratio of confirmed covers to expected covers.
• Weather: hot & sunny → increase cold beverages, salads, ice cream; cold & rainy → increase soups, hot drinks. Test multipliers locally (e.g., +15–30%).
• Promotion effect: planned promotion historically increases item sales by Y%; if unknown, start with +20–30% and adjust after reconciliation.

Example reorder-rule (par method)

ReorderQty = max(0, ParLevel - OnHand - OnOrder + ExpectedSalesDuringLeadTime)

Set ParLevel = expected sales during lead time + safety stock (e.g., 1–2 days equivalent for perishables).

Communication checklist for purchasing

• Confirm SKU code, supplier, unit of measure, and pack size.
• Confirm requested delivery date and acceptable delivery window.
• Note any substitutions permitted and approval process.
• Record PO number and expected invoice amounts for cost tracking.
• Notify receiving staff of any special handling (temperature, staging).

Reconciliation steps and short analysis

• Track forecast error per SKU: use MAPE (mean absolute percentage error) or simple percentage error for the week.
• Identify bias (consistent over- or under-forecast) and adjust baseline method or uplift rules.
• Log all exceptions (supplier delay, no-shows, special events) so you can classify causes of variance.
• Update ParLevels and safety stock for items with repeated stockouts or spoilage.

Key performance indicators to track

• Forecast accuracy (MAPE) by SKU or category
• Number of stockouts per week
• Spoilage rate (value or % of received)
• Fill rate from preferred supplier
• Days of inventory for key SKUs

Tailoring tips

• Independent restaurants: keep the weekly meeting tight (15–30 min). Focus on 10–20 SKUs that drive most variance.
• Multi-location groups: centralize forecast rules and share event calendars, but allow site-level prep adjustments for local patterns.
• High-variability menus: move to smaller batch prep and more frequent replenishment where practical.

Common pitfalls to avoid

• Relying solely on last-week sales without accounting for events or weather.
• Over-ordering to avoid stockouts without tracking spoilage costs.
• Poor communication between FOH and purchasing about events or menu changes.

Quick meeting agenda (15–30 min)

1. Review headline signals (reservations, events, weather) — 5 min
2. Agree baseline sales for key SKUs/categories — 5–10 min
3. Apply adjustments & set prep / reorder recommendations — 5–10 min
4. Assign purchasing actions and confirm delivery windows — 5 min

Use this workflow every week and record the inputs and outcomes. Small, consistent improvements in forecasting lead quickly to fewer stockouts, lower spoilage, and better margins.