EDI 204 – Motor Carrier Load Tender

What is an EDI 204?

EDI 204 (Motor Carrier Load Tender) is sent by a shipper or 3PL/broker to a motor carrier to offer a load for pickup and delivery. It specifies the shipment, stops, dates/times, references, equipment, and charges so the carrier can accept, reject, or counter via the EDI 990. Replacing phone calls and spreadsheets, the 204 delivers structured, machine-readable instructions that speed booking and reduce errors.

Primary purpose: Tender a load with all operational details so a carrier can respond and plan capacity.
Typical receivers: Asset-based carriers, dedicated fleets, and carrier portals/TMS.
Often paired with: EDI 990 (response), EDI 214 (status), EDI 210 (invoice), EDI 997 (control).

Why EDI 204 Matters in 2025

Speed to book: Automated tenders reduce dwell time and speed carrier acceptance.
Capacity alignment: Precise lanes, service levels, and dates help carriers plan tractors/teams.
Chargeback prevention: Clear requirements reduce appointment misses and accessorial disputes.
AI planning: 204 data feeds TMS forecasting, pricing engines, and network optimization tools.

EDI 204 Structure & Key Segments

Typical Segment Order

ST – Transaction Set Header
B2 – Beginning Segment for Shipment Information (shipper, SCAC)
B2A – Set Purpose (e.g., Original, Replace, Cancel)
L11 – Reference Numbers (PO, PRO, BOL, Shipment ID)
NTE – Notes/Special Instructions (optional)
N1/N3/N4 – Parties & Addresses (shipper, consignee, bill-to, broker)
G62 – Dates/Times (pickup, delivery, ready-by, must-arrive-by)
S5 – Stop-off Details (stop sequence and action)
L5 – Commodity Description (optional)
AT8 – Weight, Pieces, Volume
L0 – Line Item – Quantity/Packaging
L1 – Rate and Charges (base, fuel, accessorials)
MS3 – Interline Information (optional)
SE – Transaction Set Trailer

Core Data Elements (Pointers)

Identifiers: L11 for PO/BOL/Shipment ID; B2-04 for SCAC.
Stops & Actions: S5 (sequence + pickup/delivery code) with matching N1/N3/N4 addresses.
Dates/Times: G62 (appointment windows, ready times, delivery deadlines).
Equipment/Service: Service level, equipment type (e.g., van, reefer, team) via codes and notes.
Freight Details: AT8 (weight/pieces), L0 (units), L1 (rates/charges).

Common Tender Elements

Examples of frequently used EDI 204 tender fields
Element	Where	Example
Pickup Appointment	`G62`	Ready 2025-10-08 08:00; Appt Required
Delivery Deadline	`G62`	Must Arrive By 2025-10-10 16:00
Load Specs	`AT8` / `L0`	40,000 lb; 22 pallets; 1 trailer
Charges	`L1`	Linehaul + Fuel + Accessorials
References	`L11`	PO 12345 / BOL 67890 / Stop IDs

Note: Exact segments and qualifiers vary by each trading partner’s Implementation Guide (IG).

204 in the Transportation Lifecycle

Tender: Shipper/broker sends 204 with all load details.
Response: Carrier replies via 990 (Accept/Reject/Substitute).
In-Transit: Carrier transmits 214 status events.
Billing: Carrier issues 210 after POD and service completion.
Control: 997 to reconcile control numbers.

Implementation Checklist (Pointers)

Gather partner IGs; confirm required codes for service level, equipment, accessorials.
Standardize references (PO, BOL, Shipment ID) and define system-of-record.
Normalize time zones; specify appointment windows and lead times in G62.
Validate addresses and stop sequencing (N1/N3/N4 + S5).
Configure rates/charges in L1; document accessorial triggers.
Automate retries and 997 reconciliation; alert on negative/late acknowledgments.
Pilot on one lane/carrier; scale once SLA and on-time metrics stabilize.

Validation & Compliance

Syntax: ISA/GS envelope; ST/SE control; delimiters/terminators.
Semantic: Required elements present, stop sequence valid, date windows realistic.
Business rules: Appointments honored; equipment matches load; accessorials justified.
Security: AS2/AS4 with MDN, SFTP, or VAN; certificate rotation and TLS minimums.

2025 Search & AI-Result Optimization

Search-Engine Signals

Intent match: Targets “what is EDI 204,” “EDI 204 segments,” “load tender EDI,” “204 vs 990.”
Topical depth: Definitions, segments, lifecycle, compliance, and FAQs.
Entity SEO: Internal links to 990/214/210/997 pages to strengthen knowledge graph.
UX/Core Web Vitals: Scannable lists, accessible tables, minimal CLS, fast LCP.

Need help implementing EDI 204? Cogential IT provides mapping, testing, certification, carrier onboarding, and 24/7 monitoring for reliable tender-to-invoice automation.