Every ELD ping and EDI 214 updates the load state machine in real time.
The Shipment Events Agent ingests position and status events from ELDs, EDI 214 transactions, and carrier portals. It manages load state transitions, recalculates ETAs, and flags behind-schedule loads for the Service Failure Monitor.
Trigger
ELD ping, EDI 214 status update, or carrier portal event
Human approval required
No — state updates and ETA recalculation are automated
Hands off to
Service Failure Monitor (behind schedule) · POD Collection (delivered)
Every load moves through defined states
The Shipment Events Agent is the authoritative writer to the load state machine. Every transition is timestamped and immutable.
Quoted
Rate request received, pending pricing
Needs Rating
Load record created, sent to Rating agent
Pending Approval
Rate confirmation draft in dispatcher queue
Dispatched
Rate confirmation sent, carrier assigned
At Pickup
Driver checked in at origin facility
In Transit
Loaded and moving toward delivery
At Delivery
Driver checked in at destination facility
Delivered
Delivery confirmed, POD collection starts
What the Shipment Events Agent does
Processes event data from any source — ELD, EDI, or portal — and keeps load state, timestamps, and ETAs accurate without dispatcher intervention.
ELD position processing
Samsara and Motive ELD pings are ingested on the configured interval. Position is matched to the load by truck ID or carrier USDOT number. ETA is recalculated from current position using historical lane transit times.
EDI 214 status updates
Carrier-transmitted EDI 214 motor carrier shipment status messages are parsed in real time. Status reason codes (X1 — picked up, X3 — in transit, X6 — out for delivery, D1 — delivered) map directly to the load state machine.
Carrier portal event ingestion
For carriers that don't transmit EDI 214, the agent scrapes carrier visibility portals on a configurable schedule and translates portal status text into normalized load state transitions.
Load state machine management
The agent is the authoritative writer to the load state machine. Every transition — dispatched, at_pickup, in_transit, at_delivery, delivered — is recorded with the source event, the timestamp, and the triggering data.
ETA recalculation
Each position update triggers an ETA recalculation using current position, road speed data, and remaining distance. The updated ETA is written to the load record and surfaced in the shipper visibility portal.
Schedule deviation flagging
When the recalculated ETA exceeds the required delivery window by a configurable threshold, the agent flags the load as behind schedule. The Service Failure Monitor picks up the flag and begins its exception workflow.
From event stream to current load state
Any event from any connected source updates the load record within seconds. Dispatchers always see the current picture — not the one from the last manual check call.
Event arrives from any source
An ELD position ping from Samsara or Motive, an EDI 214 transaction from the carrier, or a status update from a carrier visibility portal reaches the event processor.
Event is matched to a load
The event is matched to an open load record by truck ID, carrier pro number, BOL number, or SCAC code. Unmatched events are held in a review queue for manual assignment.
State machine transitions
If the event corresponds to a state change — pickup arrival, loaded departure, delivery check-in — the load state is updated. The transition is timestamped and the previous state is preserved in history.
ETA is recalculated
For in-transit loads, the updated position triggers a new ETA calculation. The shipper-facing portal reflects the new estimate within seconds of the event.
Deviation check runs
If the new ETA indicates the load will miss the delivery window, a behind_schedule flag is set on the load record. The Service Failure Monitor begins its early-warning workflow automatically.