Demand forecasting by region
Stage 6 · Analytics, Refinement & Efficiency
P2Expansion
Four-Lane View
Software Function
- ›Consumer demand by region (the app_demand screen): where freight will originate PO-to-load pipeline: client purchase orders become forecast outbound legs Warehouse inventory positions (Stage 5) + demand = forward-placement recommendations Seasonality models per corridor (produce, retail, peak)
Service Provider / Admin
- ›Capacity planning weeks ahead: recruit drivers (Stage 1) where demand will be, not where it was
User — Driver / IOO
- ›"Where freight will come from" screen — plan next month, not just next load
Customer — Client / FF / NVOCC
- ›Forward-place inventory ahead of demand (six SKUs at stockout risk in the NE → move them now) CLIENT/FF/NVOCC — advice only a warehouse+freight owner can act on
Software Function
- ›Consumer demand by region (the app_demand screen): where freight will originate PO-to-load pipeline: client purchase orders become forecast outbound legs Warehouse inventory positions (Stage 5) + demand = forward-placement recommendations Seasonality models per corridor (produce, retail, peak)
Competitors
SONAR (macro indices), DAT iQ (rate forecasts), SAP IBP (enterprise planning, no execution). None connect forecast to trucks and pallets they control.
Differentiation
Forecasts everywhere else end as PDFs. Ours end as dispatched repositioning moves and recruiting targets — closed-loop between prediction and execution.
Make It Better
Stockout prevented because the platform moved the pallets before the client asked — the moment analytics becomes a service no one can churn from.