# EDI 213 Shipment Status Inquiry: Carrier Guide
> EDI 213 Motor Carrier Shipment Status Inquiry explained: the B11, REF, L10, N1 and K2 segments, live examples by PRO and by BOL, and how the 214 answers it.
The EDI 213 Motor Carrier Shipment Status Inquiry is the X12 transaction a shipper or consignee sends a motor carrier to ask for the status of a specific shipment, identified by PRO number, bill of lading or purchase order. The carrier answers with a 214 shipment status message. The 213 is the question; the 214 is the answer.
**The EDI 213 is a tracking request in X12 form.** Instead of typing a PRO number into a carrier's website or calling customer service, a shipper's or receiver's system sends a 213 with the shipment's references, and the carrier's system replies with a [214 status message](/guides/edi/214-transportation-carrier-shipment-status). It is a small transaction, rarely more than a dozen segments, but it is the one that lets you pull status on demand rather than wait for the carrier to push it.
This guide covers what the 213 carries, when it makes sense next to an ordinary 214 feed, every segment you will map, two live examples (a shipper asking by PRO and a DC asking by bill of lading), and the mistakes that leave inquiries unanswered.
## What Is an EDI 213?
**An EDI 213 is the Motor Carrier Shipment Status Inquiry transaction set defined by [ASC X12](https://x12.org/products/transaction-sets), used to request shipment status from a motor carrier.** The standard states that the requestor may be a shipper or a consignee. It travels in functional group `MI` (the `GS01` value).
Authoritative references for 213 work:
- The [X12 transaction set catalog](https://x12.org/products/transaction-sets) defines the 213 and its segment order, and [Stedi's X12 004010 reference for the 213](https://www.stedi.com/edi/x12-004010/213) lists every segment and element by release
- The [National Motor Freight Traffic Association (NMFTA)](https://nmfta.org/what-is-scac-and-how-do-carriers-get-it) issues the SCACs that identify the carrier you are asking, normally the receiver ID on the interchange
- Each carrier that supports the 213 publishes its own guide, which says which references it can search on and how it replies
**Who sends it?** A shipper, a consignee, or a third party acting for one of them, such as a 3PL or a freight audit firm.
**Who receives it?** The motor carrier, usually an LTL carrier, that holds the shipment.
**When is it sent?** Whenever the requester wants status it does not already have: a shipment that has gone quiet, a delivery that is late, or a customer asking where their order is.
**Why does it matter?** Most carriers push 214s at milestones, but only for the parties and events they have been set up to report. The 213 lets you ask about a single shipment when you need it, using whatever reference you hold.
## When to Use a 213 Instead of Waiting for a 214
The 213 and the 214 are two halves of one conversation, and you can run the 214 without the 213.
| Situation | Push 214 feed | 213 inquiry, then 214 reply |
|---|---|---|
| You tender all your freight to the carrier and it sends 214s for every shipment | Covers it | Rarely needed |
| A shipment has not had a status for days | Nothing arrives until the next event | Ask for current status |
| You are the consignee on inbound freight someone else tendered | You may not be on the carrier's 214 list | Ask by BOL or PO |
| A customer asks about one order | You search the 214s you received | Ask the carrier directly |
| You switch carriers often or use many small ones | Setting up push feeds for each is slow | Ask only when you need to |
Carriers differ in whether they support the 213 at all. Many now offer tracking APIs and web portals instead, and a growing share of shippers get status through visibility platforms that aggregate carrier data. If your carrier does accept 213s, it is still the simplest way to pull status into an EDI-based system without a second integration.
## How a 213 Inquiry Works
1. **Requester identifies the shipment.** It picks the strongest reference it has: the carrier's PRO number if known, otherwise the bill of lading number, the purchase order, or a combination.
2. **Requester sends the 213.** One transaction per shipment, with the references in `REF`, the pickup date in `B11`, and the shipper and consignee in the `N1` loop.
3. **Carrier acknowledges.** A 997 confirms the 213 was syntactically valid.
4. **Carrier searches its system.** The PRO number is an exact match. A BOL or PO search may need the shipper, consignee or pickup date to narrow it down.
5. **Carrier replies with a 214.** The 214's `B10` segment carries the shipment references, and its `AT7` loops give the current status, date, time and location. See the [214 guide](/guides/edi/214-transportation-carrier-shipment-status) for the status codes.
## Interactive Example: Shipper's 213 by PRO Number
Lakeshore Home Goods' freight from our [754 routing guide](/guides/edi/754-routing-instructions) was picked up on November 11. A day later its customer service team wants to confirm it is on schedule for the DC. Its system sends a 213 to carrier `QLTX` with the PRO number, bill of lading and PO in `REF` segments, the total weight in `L10`, the shipper and consignee in `N1` loops, and a free-text note in `K2`. All names, IDs and SCACs are fictional.
Use the **Plain English** tab for a readable summary, or click any segment to break it down element by element.
## Interactive Example: Consignee's 213 by Bill of Lading
Here the retailer's DC asks the same carrier about two inbound shipments. It does not have PRO numbers, only the suppliers' bill of lading numbers and its own POs from the ASNs. The interchange carries two 213 transactions, one per shipment, because the 213 is built around a single shipment: its references sit in the heading, not in a repeating loop.
## 213 Structure at a Glance
The table follows X12 004010. Later releases keep the same short layout.
| Position | Segment | Name | Usage | Notes |
|---|---|---|---|---|
| Heading | **ST** | Transaction Set Header | Mandatory | `ST01` = `213` |
| Heading | **B11** | Beginning Segment for Shipment Status Inquiry | Mandatory | Requestor ID and pickup date |
| Heading | **C3** | Currency | Optional | Rarely used |
| Heading | **REF** | Reference Identification | Optional, up to 10 | PRO, bill of lading, PO and other references |
| Heading | **L10** | Weight | Optional, up to 5 | Shipment weight, to help the carrier match |
| Loop 0100 | **N1 / N2 / N3 / N4** | Name and address | Up to 5 loops | Shipper, consignee and other parties |
| Loop 0100 | **G61** | Contact | Optional, up to 2 | Who to contact about the inquiry |
| Loop 0100 | **REF** | Reference Identification | Optional, up to 10 | Party-level references |
| Heading | **K2** | Administrative Message | Optional, up to 2 | Free-text message |
| Summary | **SE** | Transaction Set Trailer | Mandatory | Segment count and control number |
## Key Segments Explained
### B11: Beginning Segment for Shipment Status Inquiry
```
B11*25*LHG4471*20261111~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **B1101** | Identification Code Qualifier | `25` | How the requestor is identified. `25` is the carrier's customer code |
| **B1102** | Identification Code | `LHG4471` | The requestor's ID under that qualifier |
| **B1103** | Date | `20261111` | Pickup date of the shipment |
| **B1104** to **B1109** | Unit, quantity, amount and description pairs | | Optional pairs, rarely used |
| **B1110** | Service Level Code | | Optional |
| **B1111** | Report Transmission Code | | Optional |
The standard says `B1101` identifies the requestor and `B1103` is the pickup date. Which qualifier to use in `B1101` is set by the carrier's guide. The carrier's customer (account) code is a common choice because the carrier can look it up directly, but some carriers want a DUNS number or a mutually defined code.
The pickup date matters more than it looks. A BOL or PO number is not unique across a carrier's whole history, and the pickup date is often what lets the carrier find the right shipment.
### REF: Shipment References
```
REF*CN*QLTX20481557~
REF*BM*LHG-BOL-77120~
REF*PO*4500781234~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **REF01** | Reference Identification Qualifier | `CN` | `CN` carrier's PRO number, `BM` bill of lading number, `PO` purchase order number |
| **REF02** | Reference Identification | `QLTX20481557` | The value |
Send every reference you have. The PRO number is the carrier's own key and matches exactly. Without it, the BOL is the next best, because the carrier recorded it at pickup. A PO alone is weak: carriers only know it if the shipper put it on the bill of lading.
### L10: Weight
```
L10*5710*G*L~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **L1001** | Weight | `5710` | The shipment weight |
| **L1002** | Weight Qualifier | `G` | `G` gross weight |
| **L1003** | Weight Unit Code | `L` | `L` pounds, `K` kilograms |
Weight is a tiebreaker. If two shipments share a BOL number, the weight helps the carrier pick the right one.
### N1 Loop: Shipper and Consignee
```
N1*SH*LAKESHORE HOME GOODS~
N3*4100 EASTERN AVE SE~
N4*GRAND RAPIDS*MI*49508*US~
G61*IC*DANA REYES*TE*6165550142~
N1*CN*BIG-BOX RETAILER DC 6021*92*6021~
N4*COLUMBUS*OH*43217*US~
```
The loop repeats up to five times. `N101` = `SH` is the shipper and `CN` the consignee. City, state and postal code in `N4` are usually enough for the carrier to narrow its search. `G61` gives a contact (`G6101` = `IC`, information contact), with the name in `G6102` and a phone number in `G6104` after the qualifier `TE` in `G6103`.
### K2: Administrative Message
```
K2*PLEASE CONFIRM DELIVERY APPOINTMENT AT DC 6021~
```
`K201` is free text up to 80 characters. Most carriers process the 213 automatically and never read it, so do not put anything here that needs an answer. Use it for context a person might see if the automated search fails.
## 213 vs 214 vs 869 and 870
| Document | Sent by | Sent to | Purpose |
|---|---|---|---|
| **213 Shipment Status Inquiry** | Shipper or consignee | Motor carrier | Where is this shipment? |
| **[214 Shipment Status](/guides/edi/214-transportation-carrier-shipment-status)** | Carrier | Shipper, consignee or third party | Here is its status, time and location |
| **[869 Order Status Inquiry](/guides/edi/869-order-status-inquiry)** | Buyer | Seller | What is the status of my purchase order? |
| **[870 Order Status Report](/guides/edi/870-order-status-report)** | Seller | Buyer | Here is the status of the order and its lines |
| **[212 Delivery Trailer Manifest](/guides/edi/212-motor-carrier-delivery-trailer-manifest)** | Carrier | Consignee | Here is everything on the trailer coming to you |
The 869 and 870 ask about an order: has it been picked, shipped, back-ordered? The 213 and 214 ask about freight: where is the truck? A buyer chasing a late PO may need both, an 869 to the supplier to find out whether it shipped, then a 213 to the carrier to find out where it is.
## Common 213 Errors and How to Prevent Them
| Error | What happens | Prevention |
|---|---|---|
| **No PRO number and no pickup date** | Carrier cannot find the shipment; no 214 comes back | Store the PRO from the carrier's first 214 or the BOL, and always send `B1103` |
| **Wrong qualifier on a reference** | A BOL searched as a PRO returns nothing | Map `REF01` from the field the value came from, never by guess |
| **Several shipments in one 213** | Carrier answers for one, or rejects the set | Send one 213 per shipment; batch them in one functional group |
| **Requestor ID not on file** | Inquiry rejected as unauthorized | Use the `B1101` qualifier and ID the carrier set up for you |
| **No process for the 214 reply** | The answer arrives but nobody sees it | Route replies into the same tracking view as your push 214s |
| **Polling every shipment on a schedule** | Unneeded traffic on both sides, and most replies repeat what you already know | Ask only about shipments with no recent status or a past-due delivery, and follow any limits in the carrier's guide |
| **Asking a carrier that does not support 213** | Silence | Confirm support during onboarding; use the carrier's API or portal otherwise |
## 213 Implementation Checklist
- Confirm the carrier accepts the 213, and in which X12 release
- Get the requestor qualifier and ID it expects in `B11`
- Confirm which `REF` qualifiers it can search on (PRO, BOL, PO, others)
- Confirm whether it replies with a 214 and how fast
- Decide which shipments trigger an inquiry, and cap the frequency
- Store PRO numbers as soon as you receive them, from the BOL, a 214 or an invoice
- Map the reply 214s into your shipment tracking and alerts
- Test a PRO search, a BOL-only search and a shipment the carrier cannot find
The [EDI document types reference](/edi-document-types) shows how the transportation sets fit alongside order, ship notice and invoice documents, and the [SCAC code glossary entry](/glossary/scac-code) explains how carriers are identified.
## Where OrderSync Fits
Tracking questions usually start as order questions: a customer asks where their purchase order is. Answering fast depends on having the order, its PO number and its shipment references in one clean record.
OrderSync reads inbound orders in any format, from EDI 850s and 875s to PDFs, emails and spreadsheets, matches customers, items and units to your catalog, and outputs clean ERP data or valid X12. That keeps the PO numbers on your orders, bills of lading and inquiries consistent. Paste any 213 or 214 into the [free EDI inspector](/edi-inspector) to see it parsed segment by segment with a plain-English summary, or [book a 15-minute walkthrough](/book-call) to see your own orders processed.
## Frequently Asked Questions
### What is an EDI 213?
The EDI 213 Motor Carrier Shipment Status Inquiry is an X12 transaction a shipper or consignee sends a motor carrier to ask for the current status of a specific shipment. It identifies the shipment by PRO number, bill of lading, purchase order or a combination, and the carrier replies with a 214 status message.
### What is the difference between EDI 213 and EDI 214?
The 213 is the request and the 214 is the status. A shipper or consignee sends a 213 to ask where a shipment is. The carrier sends a 214 with the status code, date, time and location. Carriers also send 214s unprompted at milestones, so many shippers use 214s without ever sending a 213.
### What is the B11 segment in an EDI 213?
B11 is the 213's beginning segment. B1101 and B1102 identify the requestor, for example with the carrier's customer code, and B1103 is the shipment's pickup date. The remaining B11 elements are optional and rarely used.
### What references can I use in an EDI 213?
Use REF segments with the carrier's PRO number (qualifier CN), the bill of lading number (BM) and the purchase order (PO). Send as many as you have. The carrier's guide lists the qualifiers it can search on.
### Can one EDI 213 ask about several shipments?
The 213's references sit in the heading, so one transaction describes one shipment. To ask about several, send several 213 transactions, which can travel together in one functional group and interchange.
### Who can send an EDI 213?
The X12 standard says the requestor may be a shipper or a consignee. In practice third parties acting for them, such as 3PLs and freight audit firms, also send 213s, as long as the carrier has set them up as a trading partner.
### Do all carriers support the EDI 213?
No. Support varies, and many carriers now point customers to tracking APIs or web portals instead. Check the carrier's EDI guide or ask its EDI team during onboarding. The 214 is far more widely supported.