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 · Catalogs and pricing

EDI 466 Rate Request

The X12 document used to request rail rates applicable to specific movements.

Sent by
Shipper or pricing agent
Received by
Railroad
Standard
ANSI ASC X12

What is an EDI 466?

The EDI 466 Rate Request is the ANSI X12 transaction set used to request rail rates applicable to specific movements. It identifies the commodity, origin, destination, equipment and other conditions of the move for which rates are wanted.

Shippers use rate requests when planning new business or comparing routing options. The railroad answers with rate information, typically through a 460 price distribution. Requests can cover several movements at once, such as alternative destinations or routes. They are often the first step in negotiating new contract rates.

How the EDI 466 worksDiagram of the EDI 466 Rate Request. Shipper or pricing agent sends it to railroad. It usually starts the exchange. It is usually followed by 460 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information). 0 optional loops are listed by their first segment.How the EDI 466 worksRate Request: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 466SENDERShipper or pricingagentRECEIVERRailroad997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY460Railroad Price DistributionRequest or Response997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TPGS … GETransaction set 466ST … SEHEADINGRENRate Request InformationBlue 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 466. Your trading partner's implementation guide adds its own requirements.
How the EDI 466 worksDiagram of the EDI 466 Rate Request. Shipper or pricing agent sends it to railroad. It usually starts the exchange. It is usually followed by 460 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information). 0 optional loops are listed by their first segment.How the EDI 466 worksRate Request: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 466SENDERShipper orpricing agentRECEIVERRailroad997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY460Railroad Price Distribution Request orResponse997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code TP (GS … GE)Transaction set 466 (ST … SE)HEADINGRENRate Request InformationBlue 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 466. Your trading partner'simplementation guide adds its own requirements.

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

  • Requesting rates for a new origin-destination pair
  • Asking for rates on alternative routes
  • Requesting rates for new commodities

Where it fits in the document flow

This document 466 Rate Request
Usually followed by 460 Railroad Price Distribution Request or Response997 Functional Acknowledgment

Structure

Mandatory segments in the 466 (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
  • REN
  • SE

Practical example

The 466 in practice

A fertilizer producer considers shipping to a new distribution terminal. It sends the railroad a 466 asking for rates for covered hopper shipments from its plant to the terminal. The railroad replies with a 460 giving the applicable rates and conditions.

Implementation

Implementation considerations for the 466

  • Describe the movement completely, including equipment and volumes.
  • Use station and commodity codes from the industry master files.
  • Track requests until rates are received.
  • Compare answers across routes where alternatives exist.

How ECOM helps

Automate the 466 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 catalogs and pricing documents

All 21 catalogs and pricing documents

Need help with the EDI 466?

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

Request a Demo Contact us