Territory · Substrate signal

01The 3PL planning black box.

Your words: "the planning is slightly black box… we outsource a lot." The 3PL plans, dispatches, settles. You see the bill, not the decisions behind it. Caddie reads the 3PL's plan, surfaces it back with what-if + override, writes the audit trail. Local solution. Doesn't touch global ABP.

Where Caddie sits

In the flow you already run.

3PL · plans + dispatches + settles your outbound + inbound flows

↓

CADDIE · read 3PL plan · what-if · override · audit trail

↓

Your visibility surface (planner / supply chain ops)

SAP backbone (source of truth, untouched)

Existing advanced-planner (untouched)

3PL's own TMS / WMS (read-only)

Local-touch overlay on top of the outsourced planning layer. Rip-and-replace nothing. Surface what is decided + let your team override + log it.

What we read

The substrate.

Your conversation

"The logistics piece because that is something which a lot of people don't focus in like for even for us like we outsource a lot. So the planning is slightly black box."

Srini Sarangapani · Director Supply Chain (India + ASEAN)

Where we've shipped this shape

Mahindra spare-parts distribution: Mahindra Logistics is the 3PL, but Mahindra wanted the planning surface in their own hands. Caddie sits above the 3PL's execution and gives Mahindra what-if + override.

Mahindra · spare-parts distribution · in production

What stays untouched

You don't replace your 3PL. You don't replace SAP. You don't touch your global advanced-planning system. Caddie's read-layer + override-layer is local — installable in one regional instance, audit-trail to the global view if you choose.

Local-touch deployment pattern

What Enmovil delivers here

Three surfaces · here.

3PL plan ingest

Read the 3PL's plan in real time across multi-mode shipments · normalize across formats (XML, EDI, email PDF, portal scrape) · surface the decisions back as a queryable view.

What-if + override

Your planner can ask: "what if we held this dispatch by 4 hours?" Caddie computes the cost / SLA delta, drafts the override message back to the 3PL, your planner one-taps to approve.

Audit trail

Every plan, every override, every cost variance logged with timestamps + decision-maker + reason code. The 3PL relationship goes from black-box-trust to read-and-verify.

Proof anchor

Where we have shipped this shape.

3-5%

Cost reduction on FG outbound network optimization · tier-1 automotive deployment

Zero

Rip-and-replace · sits as overlay above existing 3PL + SAP

6-8 weeks

First lane · one outbound corridor · 90-day historical backtest

For the conversation

Questions, fence, timeline.

Which outbound or inbound lane today is most painful to audit when something goes wrong — where you're reconstructing what the 3PL decided after the fact?
Of the 3PLs you work with in India + ASEAN, which one's planning surface would surface the highest variance against your own constraints?
Where would a first-lane pilot land — one outbound corridor from one Indian plant, or one inbound milk-run?

We would touch

Read-layer above the 3PL's planning surface
What-if + override workflow for your planner
Plan-vs-actual variance + audit trail
Drafted reroute / expedite messaging back to the 3PL

We would not

Replace your 3PL or your contracts with them
Replace your existing TMS / WMS / SAP
Touch your global advanced-planning system
Run physical dispatch operations

6-8 weeks · one outbound lane

First lane: one outbound corridor from one Indian plant instrumented for 3PL plan ingest + what-if + override + audit trail · 90-day historical backtest against your existing 3PL settlement.