AWS reference architectureShipment tracking and ETAs
A AWS reference architecture for shipment tracking and etas in Logistics. Triggered by shipment milestone or exception event, Padiso orchestrates 3 specialist agents on Amazon Bedrock AgentCore, reaching transportation management system (tms) and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
AWSRuntime: Amazon Bedrock AgentCoreTrigger
Shipment milestone or exception event
Logistics
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Amazon Bedrock AgentCore
Tracking agent
agent
Exception agent
agent
Comms agent
agent
Integrations · MCP
MCP gateway
Your systems
Transportation Management System (TMS)
Carrier / EDI feeds
Order management
How the data flows
Trigger: Shipment milestone or exception event
- 1
Tracking agent ingests carrier events and detects delays or shortages
- 2
It correlates against the order and SLA
- 3
Exception agent proposes a reroute or recovery action
- 4
High-impact changes escalate to the ops desk
Agent team
- Tracking agent
- Exception agent
- Comms agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Amazon Bedrock AgentCore
Transportation Management System (TMS)
Carrier / EDI feeds
Order management
Security & operational considerations
- Idempotent event handling at scale
- Approvals on cost-incurring reroutes
- Audit trail per shipment
AWS deployment
Deployed in your AWS account on Bedrock AgentCore, with IAM scoping, PrivateLink to your VPC, and CloudTrail/CloudWatch for audit and observability.
Run this blueprint anywhere
More Logistics blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.