Logistics Intelligence Series | Module 6 of 6

Order-volume forecasting:
What your customers will order next month

A multi-target LSTM learns from 43 customer time series simultaneously - and forecasts order volume 4 weeks ahead. The result: proactive capacity planning instead of reactive dispatch.

01 The problem - reactive dispatch erodes margin

Why "something will turn up" is not capacity planning

A mid-sized logistics company typically plans day by day: orders arrive, trucks are dispatched. Shortfalls are covered from the spot market (expensive). Surplus capacity sits idle in the yard (deadweight cost). Both hurt.

The paradox: the data needed to forecast already exists. Every customer has an ordering pattern - seasonal swings, weekday effects, monthly rhythms. Customer A orders three full truckloads every Tuesday. Customer B doubles volume in Q4. Your ERP knows this. Your dispatch team does not.

78% of volume is forecastable

The remaining 22% are genuine spot orders. But forecasting the 78% alone reduces your reliance on subcontractors by 35%.

Order history
Decomposition
LSTM-Forecast
Capacity plan
Dispo-Alert

02 Data foundation - 24 months of order history

43 customers, 52,000 orders, each with volume, timestamp and lane

▸ Output
Aufträge: 52.340
Kunden: 43
Zeitraum: 2023-01-02 bis 2024-12-29
Ø Aufträge/Woche: 503
52.340
Orders (2 years)
503
Avg orders / week
43
Regular customers
±22%
Weekly volatility

03 Decomposition - the hidden rhythms

Seasonality, trend and weekday patterns examined separately

Total fleet order volume - 104 weeks + trend
↳ The Q4 peak

Total volume rises 38% in Q4 versus Q2. But not all customers follow this pattern. K-007 (Building materials) peaks in Q2 (construction season); K-031 (E-commerce) surges in November/December. A single fleet model is insufficient - individual forecasts per customer are required.

Order distribution by weekday (all customers)
Seasonality by industry sector - quarterly comparison

04 LSTM forecast - individual prediction per customer

A recurrent network that learns 43 time series simultaneously

We train a multi-target LSTM: a single model that processes the order history of all 43 customers as parallel time series. The advantage over 43 separate models: it learns cross-industry patterns (e.g. "when Automotive declines, Chemicals rises with a 2-week lag").

▸ Output - Modell-Architektur
Modell-Parameter: 148,452
Input:  12 Wochen × 51 Features (43 Kunden + 8 Kontext)
Output: 4 Wochen × 43 Kunden-Prognosen
8.2%
MAPE (4-week)
0.891
R² score
12.4%
MAPE (week 4)
5.1%
MAPE (week 1)
↳ Accuracy by horizon

The next-week forecast achieves ±5.1% - more accurate than any dispatcher. Even the 4-week forecast (±8.2%) is more than sufficient for capacity planning. For reference: the typical "gut-feel error" in the industry runs at 25–35%.

Forecast vs. actual - total volume (last 16 weeks, test set)
MAPE by customer - where the model hits and misses

The most difficult customers for the model are small e-commerce accounts with high volatility. The best forecasts are achieved for Automotive and Pharma - industries with stable supply chains and predictable rhythms.

05 Customer forecasts - the 4-week outlook

What the weekly capacity report for dispatch would look like

K-031 · E-Commerce · avg. 38 orders/week
↗ Seasonal peak expected
+42% in 4 weeks
Forecast w45–48: 48 → 52 → 54 → 54 orders
Driver: Black Friday run-up + Christmas season. Identical pattern to prior year (±3 orders).
Capacity requirement: +6 truck-days/week additional from w46.
K-007 · Building materials · avg. 28 orders/week
↘ Seasonal decline
–31% in 4 weeks
Forecast w45–48: 24 → 22 → 19 → 19 orders
Driver: End of construction season, falling temperatures. Use freed capacity for e-commerce.
Capacity requirement: –4 truck-days/week from w46. Reallocation to K-031 possible.
K-015 · Pharma · avg. 22 orders/week
→ Stable
±3% in 4 weeks
Forecast w45–48: 22 → 21 → 23 → 22 orders
Driver: Contract-bound volume, low seasonality.
Capacity requirement: No change required. Most reliable planning basis in the fleet.
K-022 · Automotive · avg. 35 orders/week
↗ Trend increase
+18% in 4 weeks
Forecast w45–48: 38 → 40 → 41 → 42 orders
Driver: New model launch at OEM. Not seasonal – permanent increase for 8 weeks.
Capacity requirement: +3 truck-days/week permanently. Review subcontractor contract.
↳ The dispatch effect

The forecast cards reveal the decisive advantage: K-007 releases capacity that K-031 needs - in exactly the same weeks. Without a forecast, the dispatcher would book subcontractors for K-031 (€180/run more expensive) while K-007's trucks sit idle. With the forecast: internal reallocation, zero additional cost.

06 Business impact - from forecast to margin

Fewer subcontractors, less idle capacity, stronger negotiating position

Savings potential by category
€283.100
Total savings / year
35%
Reduction in subcontractor usage
CategoryAmount/yearMechanismConfidence
Subcontractor reduction€214.2002,520 fewer routes to sub (18%→12%)High
Idle reduction€22.9003.3 pp less idle (50% achievable)Medium
Negotiation effect€28.000Better margins through proactive commitmentsMedium
Staff planning€18.000Overtime reduction through advance planningHigh

07 The full picture - all 6 modules combined

What the Logistics Intelligence Series means for your fleet

Each module solves a concrete problem. Together they form an operating system for data-driven logistics - built on data you already possess.

Modul 1
€184.300
Dwell Time
Modul 2
€118.770
Tyres
Modul 3
€254.600
Drivers
Modul 4
€220.700
Empty runs
Modul 5
€96.260
Diesel
Modul 6
€283.100
Forecasting
Total potential: €1,157,730 / year

Conservatively calculated. For a 150-truck fleet. Based on data you already have. Not a single additional customer required.

Savings potential by module - full overview
↳ The message

Over €1.1 million is locked in data already sitting in your systems - untapped. No new ERP, no new hardware, no additional sensors. Just the right questions asked of the numbers you already have. That is what we do.

08 What happens next?

From proof of concept to live system - the roadmap

You have seen what is possible. The next step is a pilot project with your real data. No months-long concept papers - we deliver results step by step.

① Data workshop (1 day)

We review your telematics, ERP and HR exports together. Which modules are ready to deploy immediately? Where is the highest leverage?

② Pilot

2 modules run on your real data. Deliverable: concrete euro value, validated dashboard, implementation plan.

③ Rollout

Integration into your existing systems. Automated reports, alerts, dashboards. Training for dispatch and fleet management.