Predictive Logistics Developer
When to Use
- Build demand forecasts at SKU, location, lane, or network-node granularity with logistics-aware features
- Design inventory positioning and safety stock model interfaces that feed planning and execution systems
- Predict ETA, lead time, and transit time distributions from operational and external signals
- Forecast capacity, congestion, and throughput for nodes, lanes, and facilities at integration level
- Integrate route and network flow predictions with TMS/WMS/OMS—not full VRP solver implementation
- Model cold chain, perishables, and shelf-life constraints in forecast and positioning logic
- Encode promotions, seasonality, and calendar effects for logistics demand and capacity
- Run backtests, monitor drift, and score models against fill rate, OTIF, WMAPE/MAPE, and service KPIs
- Define feature stores, inference contracts, and batch/real-time scoring pipelines for logistics ML
When NOT to Use
- Pure OR/MIP formulation and solver implementation without logistics prediction scope →
operations-research-algorithm-developer
- Supply chain strategy, RFQ, supplier scorecards, or inventory policy governance without ML build →
supply-chain-manager
- WMS workflows—waves, pick paths, RF scanning, slotting application logic →
wms-developer
- Fleet telematics ingestion, map matching, or geospatial pipeline engineering →
geospatial-telematics-developer
- Generic ML experimentation, causal inference, or MLOps without logistics domain framing →
data-scientist
- EDI/X12 mapping, AS2, or partner document translation →
edi-engineer
- Warehouse dimensional modeling or dbt mart design without prediction modeling →
analytics-data-engineer
Related skills
| Need |
Skill |
| LP/MIP, VRP, scheduling optimization |
operations-research-algorithm-developer |
| SCM strategy, forecast process, supplier QBRs |
supply-chain-manager |
| WMS application and ERP/WMS integration |
wms-developer |
| GPS/telematics streams and spatial ETL |
geospatial-telematics-developer |
| Partner EDI and order/shipment documents |
edi-engineer |
| General ML, A/B tests, MLOps patterns |
data-scientist |
| BI dashboards and KPI storytelling |
bi-analyst |
| Feature pipelines and warehouse modeling |
analytics-data-engineer |
Core Workflows
1. Scope and problem framing
Clarify horizon, granularity, decision consumer, and operational KPI contract.
See references/predictive_logistics_scope.md.
2. Demand forecasting and features
Build SKU/location/lane demand models with logistics calendars, promotions, and hierarchy reconciliation.
See references/demand_forecasting_and_features.md.
3. Inventory and network positioning
Connect forecasts to positioning, safety stock interfaces, and multi-echelon handoffs.
See references/inventory_and_network_positioning.md.
4. ETA, lead time, and capacity
Model transit times, node congestion, and capacity signals for planning and execution.
See references/eta_leadtime_and_capacity.md.
5. Evaluation and monitoring
Backtest against operational KPIs; track drift, bias, and forecast value.
See references/model_evaluation_and_monitoring.md.
6. Operations integration
Wire scores to OMS/TMS/WMS, planning cycles, and human-in-the-loop overrides.
See references/integration_with_operations.md.
Outputs
- Problem brief — granularity, horizon, consumers, KPI targets, and non-goals
- Feature catalog — definitions, freshness SLAs, leakage checks, and hierarchy keys
- Model card — training window, metrics (WMAPE/MAPE, bias), segments, and known failure modes
- Backtest report — rolling-origin results tied to fill rate, OTIF, or inventory service proxies
- Inference contract — schema, latency, batch cadence, fallback rules, and version pins
- Monitoring runbook — drift thresholds, retrain triggers, and escalation to planning ops
Principles
- Optimize for operational KPIs, not only statistical accuracy — tie WMAPE to service and inventory outcomes
- Respect logistics calendars — lead times, cutoffs, carrier schedules, and promotion lift are first-class features
- Prevent leakage — exclude post-decision signals; align train labels to information available at forecast origin
- Reconcile hierarchies — bottom-up vs top-down consistency for SKU × location × lane stacks
- Separate prediction from optimization — deliver distributions and interfaces; route MIP/VRP to OR peers
- Monitor in production — drift, bias by lane/node, and forecast value beat one-time offline accuracy
- Document override paths — planners and TMS rules may supersede scores; model serving must degrade safely
When to load references
| Topic |
Reference |
| Role scope, boundaries, RACI |
references/predictive_logistics_scope.md |
| Demand features, seasonality, promotions |
references/demand_forecasting_and_features.md |
| Safety stock, positioning, multi-echelon |
references/inventory_and_network_positioning.md |
| ETA, lead time, capacity signals |
references/eta_leadtime_and_capacity.md |
| Backtesting, WMAPE, drift, KPIs |
references/model_evaluation_and_monitoring.md |
| OMS/TMS/WMS integration, cadence |
references/integration_with_operations.md |
1---2name: predictive-logistics-developer3description: Build and operate predictive models for logistics networks—demand forecasting at SKU/location/lane granularity; inventory positioning and safety stock optimization interfaces; ETA and lead-time prediction; capacity and congestion signals; route and network flow forecasting at model-integration level; cold chain and perishables; promotion and seasonality; model monitoring, drift, and backtesting against operational KPIs (fill rate, OTIF, WMAPE/MAPE). Use for predictive logistics, demand forecasting logistics, ETA prediction, inventory positioning, safety stock optimization, OTIF forecast, lane demand, WMAPE, logistics ML, capacity forecasting logistics, or cold chain forecast—not pure OR/MIP without logistics domain (operations-research-algorithm-developer), supply chain strategy only (supply-chain-manager), WMS feature dev (wms-developer), fleet telematics ingestion (geospatial-telematics-developer), generic ML without logistics (data-scientist), or EDI document mapping (edi-engineer).4---56# Predictive Logistics Developer78## When to Use910- Build **demand forecasts** at SKU, location, lane, or network-node granularity with logistics-aware features11- Design **inventory positioning** and **safety stock** model interfaces that feed planning and execution systems12- Predict **ETA**, **lead time**, and **transit time** distributions from operational and external signals13- Forecast **capacity**, **congestion**, and **throughput** for nodes, lanes, and facilities at integration level14- Integrate **route and network flow** predictions with TMS/WMS/OMS—not full VRP solver implementation15- Model **cold chain**, **perishables**, and **shelf-life** constraints in forecast and positioning logic16- Encode **promotions**, **seasonality**, and **calendar effects** for logistics demand and capacity17- Run **backtests**, **monitor drift**, and score models against **fill rate**, **OTIF**, **WMAPE/MAPE**, and service KPIs18- Define **feature stores**, **inference contracts**, and **batch/real-time** scoring pipelines for logistics ML1920## When NOT to Use2122- **Pure OR/MIP** formulation and solver implementation without logistics prediction scope → `operations-research-algorithm-developer`23- **Supply chain strategy**, RFQ, supplier scorecards, or inventory policy governance without ML build → `supply-chain-manager`24- **WMS workflows**—waves, pick paths, RF scanning, slotting application logic → `wms-developer`25- **Fleet telematics ingestion**, map matching, or geospatial pipeline engineering → `geospatial-telematics-developer`26- **Generic ML** experimentation, causal inference, or MLOps without logistics domain framing → `data-scientist`27- **EDI/X12** mapping, AS2, or partner document translation → `edi-engineer`28- **Warehouse dimensional modeling** or dbt mart design without prediction modeling → `analytics-data-engineer`2930## Related skills3132| Need | Skill |33|---|---|34| LP/MIP, VRP, scheduling optimization | `operations-research-algorithm-developer` |35| SCM strategy, forecast process, supplier QBRs | `supply-chain-manager` |36| WMS application and ERP/WMS integration | `wms-developer` |37| GPS/telematics streams and spatial ETL | `geospatial-telematics-developer` |38| Partner EDI and order/shipment documents | `edi-engineer` |39| General ML, A/B tests, MLOps patterns | `data-scientist` |40| BI dashboards and KPI storytelling | `bi-analyst` |41| Feature pipelines and warehouse modeling | `analytics-data-engineer` |4243## Core Workflows4445### 1. Scope and problem framing4647Clarify horizon, granularity, decision consumer, and operational KPI contract.4849**See `references/predictive_logistics_scope.md`.**5051### 2. Demand forecasting and features5253Build SKU/location/lane demand models with logistics calendars, promotions, and hierarchy reconciliation.5455**See `references/demand_forecasting_and_features.md`.**5657### 3. Inventory and network positioning5859Connect forecasts to positioning, safety stock interfaces, and multi-echelon handoffs.6061**See `references/inventory_and_network_positioning.md`.**6263### 4. ETA, lead time, and capacity6465Model transit times, node congestion, and capacity signals for planning and execution.6667**See `references/eta_leadtime_and_capacity.md`.**6869### 5. Evaluation and monitoring7071Backtest against operational KPIs; track drift, bias, and forecast value.7273**See `references/model_evaluation_and_monitoring.md`.**7475### 6. Operations integration7677Wire scores to OMS/TMS/WMS, planning cycles, and human-in-the-loop overrides.7879**See `references/integration_with_operations.md`.**8081## Outputs8283- **Problem brief** — granularity, horizon, consumers, KPI targets, and non-goals84- **Feature catalog** — definitions, freshness SLAs, leakage checks, and hierarchy keys85- **Model card** — training window, metrics (WMAPE/MAPE, bias), segments, and known failure modes86- **Backtest report** — rolling-origin results tied to fill rate, OTIF, or inventory service proxies87- **Inference contract** — schema, latency, batch cadence, fallback rules, and version pins88- **Monitoring runbook** — drift thresholds, retrain triggers, and escalation to planning ops8990## Principles9192- **Optimize for operational KPIs**, not only statistical accuracy — tie WMAPE to service and inventory outcomes93- **Respect logistics calendars** — lead times, cutoffs, carrier schedules, and promotion lift are first-class features94- **Prevent leakage** — exclude post-decision signals; align train labels to information available at forecast origin95- **Reconcile hierarchies** — bottom-up vs top-down consistency for SKU × location × lane stacks96- **Separate prediction from optimization** — deliver distributions and interfaces; route MIP/VRP to OR peers97- **Monitor in production** — drift, bias by lane/node, and forecast value beat one-time offline accuracy98- **Document override paths** — planners and TMS rules may supersede scores; model serving must degrade safely99100## When to load references101102| Topic | Reference |103|---|---|104| Role scope, boundaries, RACI | `references/predictive_logistics_scope.md` |105| Demand features, seasonality, promotions | `references/demand_forecasting_and_features.md` |106| Safety stock, positioning, multi-echelon | `references/inventory_and_network_positioning.md` |107| ETA, lead time, capacity signals | `references/eta_leadtime_and_capacity.md` |108| Backtesting, WMAPE, drift, KPIs | `references/model_evaluation_and_monitoring.md` |109| OMS/TMS/WMS integration, cadence | `references/integration_with_operations.md` |