Territory · Substrate signal

01The orchestration seam.

Afresh decides fresh. Gateway decides promo. Blue Yonder decides everything else. Symbotic waves the dock. Descartes runs in-transit. Nothing arbitrates when they disagree. Today, that arbitration is a category director on a Teams call.

Where Caddie sits

One layer above the five point systems.

Customers · banners · stores · vendors

↓

CADDIE · agentic execution · read · draft · execute · audit

↓

Blue Yonder Enterprise Supply Planning

Afresh (fresh)

Gateway (promo)

Symbotic (DC automation)

Descartes MacroPoint (visibility)

Caddie reads across the five surfaces, surfaces conflicts, drafts the decision, and writes back on dispatcher approval with audit trail.

What we read

Five point systems · no orchestrator named.

4 Big Bets · Q4 2025

Susan Morris: "Gateway, a proprietary AI-powered tool that boosts inventory efficiency and replenishment for promotional center-store SKUs." Distinct from Afresh (which owns fresh).

Albertsons newsroom

Afresh chainwide · Oct 2025

Chainwide rollout completed across produce, meat / seafood, deli, bakery; Distribution Center Forecast also deployed across all fresh distribution centers.

Afresh PR

Inbound visibility

Descartes MacroPoint runs across private fleet + 200+ contracted carriers · 175K+ inbound loads / yr · mandatory carrier scorecards.

Descartes case

What Enmovil delivers here

Three moves · one orchestration layer.

Cross-system read

Reads across Blue Yonder + Afresh + Gateway + Symbotic + MacroPoint into one banner-aware operational picture.

Conflict drafting

When Gateway pushes a promo lift and Afresh is already cutting fresh adjacency, Caddie surfaces the conflict and drafts the resolution.

Writeback + audit trail

Dispatcher one-taps; Caddie writes back across the systems of record with a full audit trail behind every action.

Proof anchor

Where we have shipped this shape.

5 systems

Read across in one query · same pattern shipped at a Fortune 500 manufacturer

90 min

Conversational query → SAP writeback end-to-end · same deployment

40% / 30%

Fewer client inquiries · faster exception resolution · global lead-logistics provider operating across 50+ countries

For the conversation

Questions, fence, timeline.

Where does the handoff between Blue Yonder, Afresh, Gateway, and the new warehouse system live today? Is there a single planning calendar across them?
When Gateway and Afresh recommend conflicting actions on the same product-store-week, who arbitrates today — and who logs the override?
Where would a 90-day Caddie pilot land first — one distribution center, one banner, one category, or one cross-system flow?

We would touch

Cross-system reconciliation across Blue Yonder + Afresh + Gateway + Symbotic + Descartes.
Drafted conflict resolution + dispatcher one-tap + audit trail.
Banner-aware exception surfacing.
Self-contained shadow-mode logging vs incumbent decisions.

We would not

Replacing Afresh on fresh.
Replacing Gateway on center-store promo.
Replacing Blue Yonder on master planning.
Symbotic warehouse automation territory.

90-day proof · one distribution center · one dry category

Cloud-native stack + zero US grocery precedent → 3-4 month proof, not weeks. Shadow-mode Caddie logging conflicts retroactively against what category managers actually caught.