Territory · Substrate signal

03India outbound. One plant, one lane, ninety days.

270-280 pin codes. Multi-channel orders (PDF, email, phone, system entry). The optimization is in load building + 3D stacking + dynamic routing under 40-50 simultaneous constraints — exactly the operations-research surface our planning algorithms were built for.

Where Caddie sits

In the flow you already run.

Daily order book · multi-channel intake → planning queue

↓

CADDIE · planning algorithm · 40-50 simultaneous constraints · 3D load builder

↓

Carrier-mix transport · share-of-business constraints

Truck-type dimensions · 32ft / 24ft variants

Pin-code clusters · 270-280 destinations

Customer SLAs · per-destination delivery windows

Daily-level dispatch · constraint-aware load building + dynamic routing + 3D stacking. Each plant gets its own constraint set; the engine is shared.

What we read

The substrate.

Your conversation

"We also do retail deliveries, correct? We also send it to our retailers and distributors, which has around 270-280 pin codes across India. So even packaging to a particular retailer is again an optimization solution."

Srini Sarangapani · Director Supply Chain (India + ASEAN)

What our engine does

Our optimization engine handles 40-50 simultaneous constraints — vs. the 3-5 most spreadsheet-driven planners can model. The constraint count is the differentiator. Operations-research-deep, computing-power-heavy.

Latest-generation OR engine · core algorithm

Where we've shipped this shape

Maruti Suzuki: entire inbound + outbound operations + planning + visibility on Enmovil. De facto the auto-TMS in India. Mahindra: automatic load planning (ALP) live for FG outbound. Nestle: distribution dispatch planning + visibility in production.

Maruti · Mahindra · Nestle · TVS · Bajaj · Ashok Leyland · all in production

What Enmovil delivers here

Three surfaces · here.

Dispatch planning

Daily order book → optimized truck-and-route plan respecting carrier mix + share-of-business + SLAs + truck-type availability + cost. Outputs a one-tap dispatch sheet.

3D load building

Each truck type has its own dimensions. Caddie stacks the load three-dimensionally to maximize fill rate while respecting product-handling rules (fragile, stackable, single-axis).

Smart warehousing

Same algorithm, applied to your DC floor. Where to place SKUs to minimize pick-path distance. Optimizes the inbound put-away to support the outbound velocity.

Proof anchor

Where we have shipped this shape.

3-5%

Cost reduction on FG outbound · Mahindra deployment

40-50

Simultaneous constraints handled by the planning engine

Production

Mahindra ALP, Maruti TMS, Nestle dispatch · all live

For the conversation

Questions, fence, timeline.

Of your Indian plants, which one's outbound dispatch carries the highest empty-mile rate today — where load-building has the most slack to recover?
For multi-channel order intake (PDF, email, phone), where does the highest order-entry latency land — and what's the downstream planning miss?
Where would a 90-day proof land — one plant's outbound dispatch + load-building, or the multi-channel order normalization?

We would touch

Daily-level dispatch planning + load building
3D stacking + truck-type optimization
Multi-channel order intake normalization
DC put-away + smart-warehousing recommendations

We would not

Run physical truck loading or dock operations
Replace your existing carrier contracts
Touch the SAP order-management module
Run the global advanced-planning system

8-12 weeks · one plant outbound

First plant: one Indian plant's daily outbound dispatch instrumented for constraint-aware load planning + 3D stacking + dynamic routing · 90-day cost-baseline + post-deployment delta.