Who sends it
Sent by the carrier to the shipper or broker (and sometimes onward to the end customer). It is an outbound message from the carrier’s point of view.
When it fires
Throughout the life of a committed load, from dispatch to delivery. A partner’s routing guide usually specifies which status events it requires and by when.
What it carries
- The shipment and load reference numbers tying the status to the original 204.
- A status code and, for exceptions, a reason code.
- The date, time, and location the status applies to.
- For an appointment or ETA update, the new date and time.
- Equipment and stop references so multi-stop loads report per stop.
Common shipment status codes
A representative subset of standard ANSI X12 (AT7) status codes — the exact codes and the events a partner requires are set in its implementation guideline.
| Code | Meaning |
|---|---|
X3 | Arrived at pickup location |
AF | Carrier departed pickup location with shipment |
X6 | En route to delivery |
X1 | Arrived at delivery location |
D1 | Delivered |
AG | Estimated delivery / appointment update |
SD | Shipment delayed |
A7 | Refused by consignee |
Where it breaks
- A required status not sent by the deadline in the routing guide — a common source of retailer chargebacks.
- A status with a timestamp that contradicts the delivery record, which triggers a manual review.
- Duplicate or out-of-order status messages, if the carrier’s system re-sends without sequencing.
How Trailflow handles it
Trailflow EDI (beta) can send a 214 for a load that is linked to a trading partner, so status flows from the same place dispatch works the load rather than a separate portal.
See Trailflow EDI for the product. It is in beta; supported behavior may change.