Logistics and Supply Chain on AWS (2026): Visibility, Fleet Tracking, and Planning Tiers

AWS Supply Chain added N-Tier Visibility — trading-partner onboarding, shared purchase orders, and in-app collaboration — extending upstream beyond your four walls. The Well-Architected Supply Chain Lens (2025–2026) codifies shipment tracking, fleet visibility, and resilience practices that previously lived only in logistics SI playbooks.

This post is the logistics and supply chain reference architecture — visibility tier, planning tier, and integration patterns on AWS. It is not manufacturing OT/IT, not retail peak traffic, not media OTT delivery, and not generic event throughput (though high-volume scan events may need that guide).

Artifacts: architecture decision matrix, KPI baseline worksheet CSV.

Benchmark pattern (not a cited client) — Mid-market 3PL, ~2.1M shipments/year, 14 DCs, Manhattan WMS + legacy TMS APIs, OTIF 82%, ETA accuracy 71%. Phase 1: nightly ERP/WMS → S3 → AWS Supply Chain ingest (visibility latency 180 min → 22 min). Phase 2: Amazon Location + driver mobile on 500 owned routes (ETA accuracy 71% → 87% in 90 days). WMS unchanged.

Three tiers — pick one primary pain

Opinionated take: Buy visibility before building a data lake. Teams that start with Kafka + Flink for logistics usually have not fixed OTIF baselines — see the KPI worksheet.

Reference architecture

ERP (SAP/Oracle) ──┐
WMS (Manhattan)  ──┼──► Connectors / S3 landing ──► AWS Supply Chain (SCDL)
TMS APIs         ──┘         │                           │
                             │                           ├── Risk map / insights
Telematics/ELD ──► IoT Core ─┼──► Timestream / Kinesis   ├── N-Tier partner chat
Mobile driver app ─► Location Services                   └── Export to S3 → ERP
                             │
                             └──► EventBridge ──► Lambda (exception workflows)
                                       │
                                       └──► QuickSight (OTIF, fill rate, ETA)

AWS Supply Chain layer

AWS Supply Chain sits above operational systems — it does not replace WMS picking logic. Ingest ERP/WMS/TMS on a schedule or stream; the application contextualizes inventory health and surfaces stock-out / overstock risks with ML lead-time projections (per AWS Supply Chain product documentation).

Use when:

• Multiple DCs and suppliers create conflicting inventory snapshots
• Planners spend days merging spreadsheets before S&OP meetings
• You need partner-facing PO status without building a portal from scratch

Fleet and last-mile layer

For owned fleet or contracted carriers with mobile apps:

• Amazon Location Service — maps, geofences, route segments
• AWS IoT Core — MQTT from telematics or phone location streams
• API Gateway + Lambda — appointment scheduling, exception webhooks
• EventBridge — fan-out to customer notification SNS/email

Well-Architected Supply Chain Lens SCREL02-BP01 recommends IoT + logistics API integration for end-to-end shipment visibility — align geofence entry/exit to automated workflows (delay notifications, dock reassignment).

What broke — Week 5 of a TMS API polling pipeline. Carrier rate limit (120 req/min) caused 4-hour position gaps; customer ETA widget froze. Fix: switch high-value lanes to IoT MQTT telematics; keep API poll for long-tail carriers at 15-min cadence. ETA accuracy recovered 61% → 84% on instrumented lanes only.

Integration patterns — latency vs complexity

For event volume above ~8k TPS on scan streams, read high-throughput tier selection before FIFO or shard mis-sizing.

KPIs — measure before tooling

Model targets in the KPI worksheet before RFPing AWS Supply Chain or IoT vendors.

When NOT to escalate architecture

What to do this week

1. Export 90-day OTIF, fill rate, ETA accuracy — worksheet CSV.
2. Inventory ERP/WMS/TMS extract paths; alarm on stale snapshot > 2 hours.
3. Run decision matrix for visibility vs fleet vs planning.
4. Pilot one DC + one carrier lane on Location + IoT before enterprise mobile rollout.
5. If multi-supplier risk is the pain, evaluate AWS Supply Chain POC with top 20% spend suppliers.

Reproduce this — Download kpi-baseline-worksheet.csv. Fill baseline_before from your TMS/WMS exports. Set month_3_target at +5–8 pts OTIF only if visibility latency is under 30 minutes — otherwise fix pipeline first.

What this post doesn’t cover

• Warehouse robotics / AMR — WMS vendor domain.
• Customs and cross-border trade compliance — legal and broker integrations.
• Manufacturing plant OEE — manufacturing industry hub.
• Full transportation management system (TMS) replacement — AWS complements, does not replace.

Related: Data analytics on AWS · Managed services · Event-driven messaging