Outbound orders are already picked and counted to the case. The job is not to predict demand, it is to prove every trailer load is legal on all six rules (temperature zones, payload weight, stacking, delivery windows, hours-of-service, dock accessibility) before it leaves the DC.
Run a scenario to see the order book folded into verified loads.
Each trailer shows three compartment fill bars (cube %), a payload weight bar, the delivery stop list with arrival and window times, and a pass/fail chip for every rule.
Regional DC (red) to store stops. Each colored polyline is one trailer's route.
Every load carries a full six-rule enumeration with measured and limit numbers, plus a sha256 hash of the canonical load. The hash lets a reviewer confirm the certificate covers the exact load it claims.
A legacy cube-only load builder merges stops whenever the total cube fits the trailer envelope. It never checks compartments, weight, stacking, delivery windows or stop limits, so it ships loads that cannot legally run. The verified builder accepts a merge only when all six rules pass, and logs every merge it refused with the blocking rule.