Amazon's inbound freight scheduling was managed through disconnected spreadsheets shared across 100+ fulfillment centers. Each FC independently tracked vendor appointments, standing appointment allocations, and capacity metrics — making it impossible for regional managers to identify scheduling conflicts, over-commitments, or capacity gaps until they manifested as operational disruptions on the dock floor.

FreightLens consolidated all FC scheduling data into a single rolling 21-day matrix view. The system surfaces over-scheduled dates (where committed volume exceeds planned capacity) in real time, provides standing appointment breakdowns by vendor type, and exposes per-FC operational metrics — enabling proactive load balancing and capacity planning across the network.

FreightLens ingests daily scheduling data from FC-level systems through an EventBridge-orchestrated pipeline. Each FC publishes its appointment and capacity data to S3, which triggers a Lambda consolidation function that normalizes, validates, and writes to DynamoDB.

The React frontend queries a REST API (API Gateway + Lambda) to retrieve the rolling 21-day matrix, standing appointment breakdowns, and FC metrics. The Admin Portal writes updates back through the same API layer, with optimistic locking on DynamoDB items to prevent conflicting edits.

CloudWatch dashboards monitor data freshness (each FC must report within its SLA window), Lambda error rates, and API latency. Alarms trigger SNS notifications to the on-call team when an FC misses its reporting window.