972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Transportation

EDI 108 Response to a Motor Carrier Rate Proposal

The X12 document a shipper or receiver uses to respond to a motor carrier's rate and service proposal.

Sent by
Shipper, receiver or logistics provider
Received by
Motor carrier
Standard
ANSI ASC X12

What is an EDI 108?

The EDI 108 Response to a Motor Carrier Rate Proposal is the ANSI X12 transaction set a shipper, receiver or other party uses to respond to a motor carrier's rate and service proposal (106). The response can accept or decline the proposal, in whole or by lane, and carries the references needed to tie it to the proposal.

The 108 closes the electronic rate negotiation started by the 107 and 106. An accepted proposal becomes the rate basis for future shipments with the carrier, so both sides should load the same agreed values.

How the EDI 108 worksDiagram of the EDI 108 Response to a Motor Carrier Rate Proposal. Shipper, receiver or logistics provider sends it to motor carrier. It usually follows 106. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), BLR (Transportation Carrier Identification), the required 0100 loop with N1 (Party Identification) and the required 0200 loop with CA1 (Rate Request Identifier) and LC1 (Lane Commitments). 0 optional loops are listed by their first segment.How the EDI 108 worksResponse to a Motor Carrier Rate Proposal: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS106Motor Carrier RateProposalEDI 108SENDERShipper, receiver orlogistics providerRECEIVERMotor carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MKGS … GETransaction set 108ST … SEHEADINGBGNBeginning SegmentBLRTransportation Carrier IdentificationRequired loop 0100 · repeats up to 10N1Party IdentificationRequired loop 0200 · repeats up to 99,999CA1Rate Request IdentifierLC1Lane CommitmentsBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 108. Your trading partner's implementation guide adds its own requirements.
How the EDI 108 worksDiagram of the EDI 108 Response to a Motor Carrier Rate Proposal. Shipper, receiver or logistics provider sends it to motor carrier. It usually follows 106. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), BLR (Transportation Carrier Identification), the required 0100 loop with N1 (Party Identification) and the required 0200 loop with CA1 (Rate Request Identifier) and LC1 (Lane Commitments). 0 optional loops are listed by their first segment.How the EDI 108 worksResponse to a Motor Carrier Rate Proposal: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWS106Motor Carrier Rate ProposalEDI 108SENDERShipper,receiver orlogisticsproviderRECEIVERMotor carrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code MK (GS … GE)Transaction set 108 (ST … SE)HEADINGBGNBeginning SegmentBLRTransportation CarrierIdentificationRequired loop 0100 · repeats upto 10N1Party IdentificationRequired loop 0200 · repeats upto 99,999CA1Rate Request IdentifierLC1Lane CommitmentsBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 108. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 108, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 108 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Accepting a carrier's proposed rates
  • Declining all or part of a proposal
  • Confirming awarded lanes after a bid

Where it fits in the document flow

Usually follows 106 Motor Carrier Rate Proposal
This document 108 Response to a Motor Carrier Rate Proposal
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 108 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • BLR
  • N1
  • CA1
  • LC1
  • SE

Practical example

The 108 in practice

After comparing proposals, a manufacturer awards a carrier 9 of the 15 lanes it quoted. It sends a 108 accepting the proposal for those lanes and declining the rest, with the effective date. Both companies load the awarded rates, and the carrier starts receiving 204 load tenders on the new lanes.

Implementation

Implementation considerations for the 108

  • Respond lane by lane where only part of a proposal is accepted.
  • Reference the carrier's proposal number exactly.
  • Load the accepted rates in the shipper's transportation and audit systems at the same time.
  • Keep a record of declined proposals for the next bid cycle.

How ECOM helps

Automate the 108 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 108?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us