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 107 Request for Motor Carrier Rate Proposal

The X12 document a shipper or receiver uses to ask a motor carrier for a rate and service proposal.

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

What is an EDI 107?

The EDI 107 Request for Motor Carrier Rate Proposal is the ANSI X12 transaction set a shipper, receiver or other party uses to request that a motor carrier provide a rate and service proposal. It describes the lanes or points, the expected volumes and freight characteristics, the equipment and the service requirements.

The 107 opens an electronic rate negotiation: the carrier answers with a 106 proposal, and the requester responds with a 108. Sending requests in a structured form lets shippers compare carriers' answers lane by lane.

How the EDI 107 worksDiagram of the EDI 107 Request for Motor Carrier Rate Proposal. Shipper, receiver or logistics provider sends it to motor carrier. It usually starts the exchange. It is usually followed by 106 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required 0100 loop with N1 (Party Identification) and detail: the required 0200 loop with LX (Transaction Set Line Number), GY (Geography) and the required 0230 loop with CA1 (Rate Request Identifier) and GY (Geography). 5 optional loops are listed by their first segment.How the EDI 107 worksRequest for Motor Carrier Rate Proposal: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 107SENDERShipper, receiver orlogistics providerRECEIVERMotor carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY106Motor Carrier RateProposal997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MCGS … GETransaction set 107ST … SEHEADINGBGNBeginning SegmentRequired loop 0100 · repeats up to 10N1Party Identification+ 1 optional loop, starting with:MS2DETAILRequired loop 0200 · repeats up to 99,999LXTransaction Set Line NumberGYGeographyRequired loop 0230 · repeats up to 99,999CA1Rate Request IdentifierGYGeography+ 4 optional loops, starting with:MS2N1Blue 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 107. Your trading partner's implementation guide adds its own requirements.
How the EDI 107 worksDiagram of the EDI 107 Request for Motor Carrier Rate Proposal. Shipper, receiver or logistics provider sends it to motor carrier. It usually starts the exchange. It is usually followed by 106 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required 0100 loop with N1 (Party Identification) and detail: the required 0200 loop with LX (Transaction Set Line Number), GY (Geography) and the required 0230 loop with CA1 (Rate Request Identifier) and GY (Geography). 5 optional loops are listed by their first segment.How the EDI 107 worksRequest for Motor Carrier Rate Proposal: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 107SENDERShipper,receiver orlogisticsproviderRECEIVERMotor carrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY106Motor Carrier Rate Proposal997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code MC (GS … GE)Transaction set 107 (ST … SE)HEADINGBGNBeginning SegmentRequired loop 0100 · repeats upto 10N1Party Identification+ 1 optional loop, starting with:MS2DETAILRequired loop 0200 · repeats upto 99,999LXTransaction Set LineNumberGYGeographyRequired loop 0230 · repeatsup to 99,999CA1Rate RequestIdentifierGYGeography+ 4 optional loops, starting with:MS2N1Blue 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 107. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 107, 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 107 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

  • Running a periodic carrier bid
  • Requesting rates for new lanes or facilities
  • Re-pricing lanes after volume changes

Where it fits in the document flow

This document 107 Request for Motor Carrier Rate Proposal
Usually followed by 106 Motor Carrier Rate Proposal997 Functional Acknowledgment

Structure

Mandatory segments in the 107 (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
  • MS2
  • N1
  • LX
  • GY
  • CA1
  • SE

Practical example

The 107 in practice

A food distributor opens a new warehouse and needs carriers for outbound deliveries. It sends five carriers a 107 listing the destination zones, weekly shipment counts, average weights, the need for refrigerated equipment and delivery appointment requirements. Each carrier replies with a 106 proposal, which the distributor compares before awarding the lanes.

Implementation

Implementation considerations for the 107

  • Describe freight accurately, including weight, class, equipment and handling needs.
  • Give each lane a stable identifier that carriers must return in their proposals.
  • Set a response deadline and the rate format you expect.
  • Plan how accepted rates will be loaded into routing and freight audit systems.

How ECOM helps

Automate the 107 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

Wholesale Distribution

Customer orders, supplier purchasing, catalogs and drop-ship for distributors.

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 107?

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

Request a Demo Contact us