972-836-7750 Request a Demo Talk to an EDI/API Expert Search
    See all results Browse the sitemap Tip: press / to search from any page
    Talk to an EDI/API Expert Request a Demo Call Sales 972-836-7750

    X12 transaction guide · Catalogs and pricing

    EDI 602 Transportation Services Tender

    The X12 document carriers use to submit rate tenders, with the parties, commodities, points, conditions, rates and charges in one docket.

    Sent by
    Carrier
    Received by
    Shipper or government transportation office
    Standard
    ANSI ASC X12

    What is an EDI 602?

    The EDI 602 Transportation Services Tender is the ANSI X12 transaction set for communicating rates and tender information. One docket can carry all the data for a tender: the parties, commodities, location points, shipment conditions, notes, point-to-point or scale rates and other charges. Carriers use it to submit a new tender or an amendment.

    Rate tenders are common in government transportation, where carriers offer rates to a transportation office that then rates shipments against them. The 602 appears in the 004010 and 005010 releases.

    How the EDI 602 worksDiagram of the EDI 602 Transportation Services Tender. Carrier sends it to shipper or government transportation office. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 005010 requires, in the heading: DK (Docket Header). 3 optional loops are listed by their first segment.How the EDI 602 worksTransportation Services Tender: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 602SENDERCarrierRECEIVERShipper or governmenttransportation office997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 005010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TSGS … GETransaction set 602ST … SEHEADINGDKDocket Header+ 2 optional loops, starting with:N1PRDETAIL+ 1 optional loop, starting with:SBBlue 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 005010 listing for the 602. Your trading partner's implementation guide adds its own requirements.
    How the EDI 602 worksDiagram of the EDI 602 Transportation Services Tender. Carrier sends it to shipper or government transportation office. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 005010 requires, in the heading: DK (Docket Header). 3 optional loops are listed by their first segment.How the EDI 602 worksTransportation Services Tender: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 602SENDERCarrierRECEIVERShipper orgovernmenttransportationoffice997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 005010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code TS (GS … GE)Transaction set 602 (ST … SE)HEADINGDKDocket Header+ 2 optional loops, starting with:N1PRDETAIL+ 1 optional loop, starting with:SBBlue 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 X12005010 listing for the 602. Your trading partner'simplementation guide adds its own requirements.

    How to read this diagram: the top row shows who sends the 602, to whom, and which documents usually come before and after it. The lower part shows what X12 release 005010 itself requires: the envelopes around the 602 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

    • Submitting a rate tender to a shipper or government agency
    • Amending rates or conditions in an existing tender
    • Offering scale or point-to-point rates for a program

    Where it fits in the document flow

    This document 602 Transportation Services Tender
    Usually followed by 997 Functional Acknowledgment

    Structure

    Mandatory segments in the 602 (X12 release 005010)

    The segments X12 release 005010 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
    • DK
    • N1
    • PR
    • SB
    • SC
    • RA
    • RH
    • SRT
    • LX
    • SRM
    • SE

    Practical example

    The 602 in practice

    A trucking company bids for freight under a government shipping program. It submits a 602 tender listing the origin and destination points, the commodities covered, the rates per mile and per hundredweight, accessorial charges and the effective period. The transportation office loads the tender and uses it to rate shipments routed to the carrier.

    Implementation

    Implementation considerations for the 602

    • Follow the receiving agency's tender format and submission rules.
    • Version tenders and amendments clearly with effective dates.
    • Keep tender rates consistent with the invoices that follow.
    • Confirm the release, since the 602 is not in later X12 releases.

    How ECOM helps

    Automate the 602 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.

    Solution

    EDI Integration

    Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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

    Related transactions

    Related catalogs and pricing documents

    All 23 catalogs and pricing documents

    From the guide to go-live

    Put this into practice with ECOM

    Reading about EDI is the first step. When you are ready to meet a trading partner's requirements, an ECOM specialist can help.

    Need help with the EDI 602?

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

    Talk to an EDI/API Expert Request a Demo Get help with EDI 602