Electronic data interchange (EDI) is how tenders, status, and invoices move between shippers, brokers, and carriers on retail and brokered lanes. Each message is an X12 transaction set identified by a number. These pages cover the sets Trailflow's EDI product handles today — Trailflow EDI is in beta.
- EDI 204 — Motor Carrier Load Tender
The EDI 204 is the electronic load tender a shipper or broker sends to a motor carrier to offer a specific shipment — the digital equivalent of the phone call and rate confirmation that offers a load.
- EDI 210 — Motor Carrier Freight Invoice
The EDI 210 is the carrier’s freight invoice sent electronically to the shipper, broker, or a paying third party — the linehaul charge, accessorials, and totals for a completed shipment.
- EDI 211 — Motor Carrier Bill of Lading
The EDI 211 communicates motor-carrier bill-of-lading information electronically. It represents shipment and transportation-document context while legal effect and document requirements remain governed by the applicable agreement.
- EDI 212 — Delivery Trailer Manifest
The EDI 212 communicates delivery trailer manifest information for freight moving on a trailer or through a related delivery operation. It gives participants a structured view of associated freight.
- EDI 214 — Transportation Carrier Shipment Status Message
The EDI 214 is the status update a carrier sends during a shipment — pickup, in transit, arrival, delivery, and exceptions — so the shipper or broker can track the load without a check call.
- EDI 315 — Status Details (Ocean)
The EDI 315 communicates ocean shipment status details between transportation participants. It reports movement or milestone context for a booking, container, or related ocean shipment record.
- EDI 322 — Terminal Operations and Intermodal Activity
The EDI 322 communicates terminal or intermodal activity related to shipment or equipment movement. It can exchange operational milestones without treating a terminal event as delivery or invoicing.
- EDI 404 — Rail Carrier Shipment Information
The EDI 404 is rail carrier shipment information used to communicate commercial and movement context for rail freight. Its exact direction and companion messages depend on the rail relationship.
- EDI 753 — Request for Routing Instructions
The EDI 753 is a request for routing instructions. A shipper or supplier asks a buyer or routing authority how freight should be tendered instead of independently choosing a carrier or route.
- EDI 754 — Routing Instructions
The EDI 754 communicates routing instructions in response to a request or another agreed trigger. It tells a shipping party how the buyer expects freight to move, subject to later operational changes.
- EDI 810 — Invoice
The EDI 810 is an electronic invoice from a seller or supplier to a buyer or payer. It requests payment and provides references needed to compare the request with the order and receipt.
- EDI 820 — Payment Order or Remittance Advice
The EDI 820 communicates a payment order, payment information, or remittance detail from a payer to a payee. It explains which invoices or adjustments a payment is intended to settle; the bank or payment rail is separate.
- EDI 824 — Application Advice
The EDI 824 reports the result of applying a received transaction to business rules. It can identify accepted information, warnings, or application errors beyond a transport or envelope acknowledgment.
- EDI 850 — Purchase Order
The EDI 850 is a buyer’s electronic purchase order to a supplier. It communicates a request to provide identified goods or services under agreed commercial terms and delivery expectations.
- EDI 856 — Advance Ship Notice
The EDI 856, commonly called an advance ship notice or ASN, tells a receiver what a supplier has shipped before freight arrives. It helps receiving identify, count, and route expected goods.
- EDI 861 — Receiving Advice
The EDI 861 is a receiving advice message from a receiving party to a supplier or upstream participant. It reports what was received, accepted, rejected, or found different from the expected order or shipment.
- EDI 864 — Text Message
The EDI 864 is a structured text-message transaction for human-readable or partner-defined explanatory information. It is generally communication around a formal transaction, not a replacement for an order, status, or invoice.
- EDI 990 — Response to a Load Tender
The EDI 990 is the carrier’s reply to a 204 load tender — accept, decline, or (where the partner allows it) accept with conditions.
- EDI 997 — Functional Acknowledgment
The EDI 997 is the technical receipt one system sends back for another’s transmission — confirming the message arrived and whether it was structurally accepted, rejected, or accepted with errors.
- EDI 999 — Implementation Acknowledgment
The EDI 999 is a stricter acknowledgment than the 997 — it confirms a transaction not only parsed as valid X12 but conformed to the specific implementation guideline agreed with the trading partner.