Territory · Substrate signal

06Network sequencing across 45 DCs.

One European yard (Tessenderlo, Belgium, 65,000 m², 180 trucks/day) on Peripass — deliberately standalone, no TMS / WMS / ERP integration. The orchestration layer above the rest of the 45-DC network is wide-open white space.

Where Caddie sits

Network-level sequencing above local yard.

Customers · retailer scorecards · dealer dispatch

↓

CADDIE · network sequencing · capacity rebalancing · audit trail

↓

DC ops (45 sites)

Peripass · Tessenderlo

Manhattan / BY WMS

Local yard / dock systems

Yard tools solve the gate locally. Caddie ties yard + dock + dispatch + capacity together with full upstream and downstream context.

What we read

The Tessenderlo precedent · the unfilled rest.

Tessenderlo · standalone

Peripass live since June 2022 — 65,000 m², 180 trucks/day. "No integration to TMS, WMS, or ERP." Solves the local yard surface; doesn't reach upstream / downstream.

Peripass · SBD case

Network footprint

~120 factories worldwide + 45 DCs delivering ~85,000 SKUs across Tools + Outdoor + Industrial. Cross-network orchestration surface is unowned at the platform layer.

Industry coverage / SBD operations

Manufactory 4.0 · plant-side

Hartford, Connecticut center shipping connected-factory + flexible-automation + advanced-analytics to plants. Plant-side investment named; cross-network DC + yard orchestration is not.

New Equipment Digest

What Enmovil delivers here

Three surfaces · one network.

Yard + DC sequencing

Trailer-arrival + dock-allocation + outbound dispatch · drafted with inbound delivery estimate + customer scorecard + capacity in one decision.

Multimodal vanning + 3D load building

Outbound load mix optimized against bulky-SKU constraints, retailer dock-windows, dealer-allocation fairness rules.

Cross-DC capacity rebalancing

When one DC throttles (labor, dock, weather) and another has slack, Caddie drafts the rebalancing action across affected purchase orders with audit trail.

Proof anchor

Where we've shipped this shape.

Multi-DC

Fleet + yard + dispatch sequencing in production · a tier-1 industrial-equipment manufacturer

Road + rail

Multimodal dispatch on finished-vehicle outbound · a tier-1 commercial vehicle manufacturer

~100K trucks/day

Under orchestration across the deployment base

For the conversation

Questions, fence, timeline.

Tessenderlo Peripass was deliberately standalone — does that logic still hold across the rest of the 45-DC network?
When a DC throttles unexpectedly, how is cross-DC capacity rebalancing decided today — planner level, BU level, or after-the-fact in chargebacks?
Is there a network-level dispatch-sequencing layer above individual DC operations, or does each DC sequence locally?

We'd touch

Yard + DC sequencing with full upstream/downstream context
Outbound load mix for bulky SKUs against constraints
Cross-DC capacity rebalancing on throttle inputs
Network-level dispatch orchestration above individual DCs

We wouldn't

Local yard / gate management at Peripass sites
WMS replacement at any DC
Dock-door physical operations
Plant-side Manufactory 4.0

10-12 weeks · one Outdoor + one Tools DC pair

First lane: one Outdoor DC + one Tools DC instrumented for cross-network sequencing, with 90 days of historical operations data for the throttle / rebalance pattern.

Who's building this

Enmovil · the technology thought partner for autonomous supply chains.

One AI-native platform. Demand sensing, inventory, dispatch, execution, freight settlement, sustainability reporting. All on one intelligence layer that sits above the systems you already own.

Under orchestration

~100K

Trucks per day across the deployment base

Daily delivery accuracy

99%

Road, rail, ocean, air

Forecast accuracy

97%

Demand sensing across deployments

Logistics cost savings

8 to 15%

Measured across deployments