# EDI 214: shipment status codes, a sample message and when to send one

> EDI 214 is the X12 shipment status message carriers send as a load moves. Status codes like X3, AF and D1, a sample message, timing and common mistakes.

URL: https://roadmark.ai/glossary/edi-214
Language: en
Last updated: 2026-10-21

**What is EDI 214?** An EDI 214 (X12 Transportation Carrier Shipment Status Message) is how a carrier tells a shipper, broker or consignee where a load is. Each 214 carries a status code, such as X3 for arrived at pickup or D1 for completed unloading, with the date, time, time zone and location. A carrier sends several 214s per load, from pickup to delivery.

*Also called Transportation Carrier Shipment Status Message and shipment status message*

*Updated October 21, 2026*

A 214 is the status update of EDI freight. Where the [204](https://roadmark.ai/glossary/edi-204) and the [990](https://roadmark.ai/glossary/edi-990) happen once per load, a carrier sends 214s again and again as the truck moves. X12 describes the [214](https://x12.org/node/4214) as a carrier telling shippers, consignees and their agents where a shipment is, with dates, times, locations, route, identifying numbers and conveyance.

## When it's sent, and by whom

The carrier sends 214s to the party that tendered the load: the shipper, or a broker acting for it. A broker in the middle usually does both: it receives 214s from the carrier it covered the load with, and sends 214s to its own customer.

When to send one depends on the customer's guide. The usual minimum:

| Code | Status                                          | When                                        |
| ---- | ----------------------------------------------- | ------------------------------------------- |
| `X3` | Arrived at pickup location                      | The truck checks in at the shipper          |
| `AF` | Carrier departed pickup location, with shipment | The truck leaves loaded                     |
| `X6` | En route to delivery location                   | In transit, often with the current location |
| `X1` | Arrived at delivery location                    | The truck checks in at the receiver         |
| `D1` | Completed unloading at delivery location        | The freight is off the trailer              |
| `CD` | Carrier departed delivery location              | The truck leaves the receiver               |

Many customers also want a status with a new estimated time whenever the ETA changes, and a reason code when a load is late.

## What's in a 214

Inside the usual envelope (the ISA and GS segments), the transaction set runs from `ST` to `SE`:

| Segment | What it holds                                                                                  |
| ------- | ---------------------------------------------------------------------------------------------- |
| `B10`   | The carrier's reference number, the shipper's shipment ID from the 204, and the carrier's SCAC |
| `L11`   | References the customer wants echoed back, such as the PO or bill of lading                    |
| `N1`    | The shipper and consignee, with `N4` for city, state or province and country                   |
| `LX`    | Opens one status entry                                                                         |
| `AT7`   | The status: the code, a reason code (`NS` for normal), the date, time and time zone            |
| `MS1`   | Where the truck was: city, state and country, or coordinates                                   |
| `MS2`   | The equipment: the carrier's SCAC and the trailer or truck number                              |
| `SE`    | The end of the set, with a count of its segments                                               |

## A sample 214

Ashgrove Freight telling Prairie Foods that load 48213 left the Mississauga pickup at 06:12 Eastern on Tuesday. The companies, IDs and figures are fictional, and the envelope is left out.

```text
ST*214*0001~
B10*48213*PF778201*ASHG~
L11*4500018821*PO~
N1*SH*PRAIRIE FOODS DC~
N4*MISSISSAUGA*ON**CA~
N1*CN*JOLIET DC~
N4*JOLIET*IL**US~
LX*1~
AT7*AF*NS***20261020*0612*ET~
MS1*MISSISSAUGA*ON*CA~
MS2*ASHG*5317~
SE*12*0001~
```

`B10` ties the message to the load twice: the carrier's number 48213 and the shipper's shipment ID PF778201. `AT7*AF*NS` says departed pickup, normal status, on October 20, 2026 at 06:12 Eastern (`ET`). `MS1` puts the truck in Mississauga, and `MS2` names trailer 5317. Later 214s for the same load would carry `X1` at Joliet in Central time, then `D1` and `CD`.

## How it relates to the 204, 990 and 210

The 214 is the third of four documents about the same load:

1. **[204](https://roadmark.ai/glossary/edi-204):** the shipper or broker offers the load.
2. **[990](https://roadmark.ai/glossary/edi-990):** the carrier accepts it.
3. **214:** the carrier reports status from pickup to delivery.
4. **[210](https://roadmark.ai/glossary/edi-210):** the carrier bills the load.

The 214s also feed the 210. Arrival and departure times at each stop are what detention is billed from, so the times a carrier reports should match the times on its invoice.

## Common mistakes

- **Sending only "delivered".** A customer who sees nothing between the tender and delivery calls for status, which is the call the 214 was meant to replace.
- **Getting the time zone wrong.** `AT7` carries a time code. An arrival at 14:40 in Joliet is Central time; sent as Eastern, it reads as an hour late.
- **Losing the shipment ID.** The 214 has to quote the 204's shipment ID in `B10`. Without it, the customer's system can't attach the status to its load.
- **Statuses out of order.** An `AF` (departed pickup) before an `X3` (arrived), or a `D1` with no `X1`, tells the customer something went wrong even when it didn't.
- **No reason on a late load.** When an appointment is missed, many customers want a reason code, not just a new time.

## How Roadmark handles 214s

For a customer on EDI, Roadmark sends a 214 at each stop and from the driver's own location, so the customer's system follows the load from the shipper to delivered. The status comes from the same place as the ETA on the board: Roadmark keeps one ETA per load, fed by the ELD, the driver app, a carrier's app or EDI 214, visibility networks and check calls. [Tracking](https://roadmark.ai/tracking) shows how that ETA is built.

It works the other way too. If you're a broker, an outside carrier's own system can send you 214s, and those status codes feed the load's ETA in Roadmark like any other source. Setup is per trading partner; see the [EDI integration page](https://roadmark.ai/integrations/edi).

## Where it fits in a load.

Four EDI documents carry a truckload from the tender to the invoice, in this order.

1. [EDI 204](https://roadmark.ai/glossary/edi-204): The shipper or broker offers the carrier a load.
2. [EDI 990](https://roadmark.ai/glossary/edi-990): The carrier accepts or declines the tender.
3. **EDI 214** (This page): The carrier reports where the load is, stop by stop.
4. [EDI 210](https://roadmark.ai/glossary/edi-210): The carrier bills the load once it's delivered.

## EDI 214: common questions

### What is an EDI 214?

It's the X12 Transportation Carrier Shipment Status Message: the document a carrier sends to report where a shipment is, with a status code, the date and time, the time zone and the location. It's the one EDI document that repeats through a load.

### What do the 214 status codes mean?

Common ones are X3 (arrived at pickup location), AF (departed pickup with the shipment), X6 (en route to delivery), X1 (arrived at delivery location), D1 (completed unloading) and CD (departed delivery location). Each customer's guide lists the codes it expects.

### How often should a carrier send 214s?

As often as the customer's guide asks. Most want at least arrival and departure at each stop and delivery; some also want location updates in transit or a new estimated time whenever the ETA changes.

### Who receives a 214?

The party that tendered the load, which is the shipper or the broker, and sometimes the consignee or a visibility provider acting for them. A broker often receives 214s from its carriers and sends its own 214s on to the shipper.

### Does a 214 count as proof of delivery?

A delivered status tells the customer's system the load arrived and was unloaded. The signed POD is a separate document that usually travels with the invoice or through a portal.

### Can Roadmark send 214s automatically?

Yes. Roadmark sends a 214 at each stop and from the driver's own location, so the customer's system sees the load at the shipper, in transit, at the receiver and delivered.

## Related pages

- [EDI X12 integration: 204, 990, 214 and 210 explained](https://roadmark.ai/integrations/edi): What EDI 204, 990, 214 and 210 mean, which way each goes and when it's sent, how trading partners are set up, and how tracking status becomes 214s.
- [EDI 204: the motor carrier load tender, explained](https://roadmark.ai/glossary/edi-204): EDI 204 is the X12 load tender a shipper or broker sends a carrier. What it contains, a sample with its segments, the 990 reply and mistakes to avoid.
- [EDI 210: the motor carrier freight invoice, explained](https://roadmark.ai/glossary/edi-210): EDI 210 is the carrier's X12 freight invoice. What's in it, a sample with linehaul, fuel and detention lines, how it ties to the 204, and why 210s get rejected.
- [Tracking](https://roadmark.ai/tracking): The few loads that need you, with reasons
- [project44 integration: location and predictive ETAs](https://roadmark.ai/integrations/project44): project44 feeds Roadmark real-time location and predictive ETAs for carriers already sharing through its network, keeping tracking and the portal current.
- [Truck detention time calculator](https://roadmark.ai/tools/detention): What a truck's time at the dock past its free time comes to, on the invoice and on the driver's pay.

Companies, people and shipment figures in product examples are fictional. They illustrate workflows and are not customer testimonials or measured results.