Type = API Reference,; Topic = Multienterprise Information Network Tower (MINT), Transforms,;Persona = TraceLink Administrator, User, Solution Partner,; Orchestration = Manufacturing, Commerce,; Function = Supply Chain, IT, Procurement,
Load tender response transactions
The Load Tender Response is an electronic transaction used by a motor carrier to respond to a shipment offer (load tender) sent by a shipper, broker, or third-party logistics provider (3PL). This message communicates whether the carrier accepts or declines the shipment and confirms transportation capacity.
This response is typically sent after receiving an EDI 204 Motor Carrier Load Tender, which contains shipment and routing details. The load tender response references the original tender and provides a status such as accepted, declined, or accepted with conditions, enabling both parties to align on shipment execution.
By standardizing carrier responses, the load tender response supports automated transportation planning within Transportation Management Systems (TMS). It allows shippers to quickly confirm capacity or reassign loads when needed, while helping carriers manage commitments and communicate decisions efficiently.
Using the load tender response improves visibility, reduces manual follow-up, and streamlines coordination between trading partners, ensuring faster and more reliable transportation execution across supply chain operations.
Load Tender Response (X12)
The Load Tender Response communicates a carrier’s acceptance or rejection of a shipment, enabling the shipper’s Transportation Management System (TMS) to confirm capacity or re-tender if needed.
Contact your TraceLink Services representative for more information about integrating with this message.
- Message Type: MPC_LOAD_TENDER_RESPONSE
- X12 Format: X12 990
- Transform Names:
- B2B_EDI_X12_990_LoadTenderResponse_IB_V1
B2B_EDI_X12_990_LoadTenderResponse_OB_V1
| Input Element | Occurs | Length | Description | Example | ||
|---|---|---|---|---|---|---|
| ISA | 1…1 | - | Required. ISA interchange envelope. | - | ||
| ISA01 | 1…1 | 2/2 | Required. Qualifier for authorization control number in ISA02. | 00 | ||
| ISA02 | 1…1 | 10/10 | Required. Information used for additional identification or authorization of the interchange sender or the data in the interchange/ 10 spaces a valid entry. | - | ||
| ISA03 | 1…1 | 2/2 | Required. Qualifier for security information in ISA04. | 00 | ||
| ISA04 | 1…1 | 10/10 | Required. Identifies security information about the interchange sender or data | - | ||
| ISA05 | 1…1 | 2/2 |
Required. Interchange sender partner ID qualifier.
|
07 | ||
| ISA06 | 1…1 | 15/15 |
Required. Interchange sender identification mapping to:
|
7777776067344 | ||
| ISA07 | 1…1 | 2/2 |
Required. Interchange receiver partner ID qualifier.
|
01 | ||
| ISA08 | 1…1 | 15/15 | Required. Instance 1 EDI receiver ID mapping to file control header and to ServiceLinkId. | 888888404358877 | ||
| ISA09 | 1…1 | 6/6 | Required. Interchange date in 6 char YYMMDD format. | 231020 | ||
| ISA10 | 1…1 | 4/4 | Required. Interchange time in 4 char HHMM format. | 1420 | ||
| ISA11 | 1…1 | 1/1 |
Required. This value is dependent on X12 version.
|
^ | ||
| ISA12 | 1…1 | 5/5 | Required. Interchange control version number. This could be any X12 version. | 00501 | ||
| ISA13 | 1…1 | 9/9 |
Required. Instance 1 interchange Control Number mapping to:
|
0000000000619827 | ||
| ISA14 | 1…1 | 1/1 |
Required. Interchange level acknowledgment requested. Valid values:
|
0 | ||
| ISA15 | 1…1 | 1/1 |
Required. Indicates whether the interchange is for production, test, or information purposes. Valid values:
|
P | ||
| ISA16 | 1…1 | 1/1 | Required. Component element separator. Delimiter that separates data elements within a composite data structure. Must be different than the data element separator and segment terminator. | > | ||
| GS | 1..1 | - | Required. GS group functional envelope. Child of ISA. Only one GS group expected per interchange. | - | ||
| GS01 | 1…1 | 2/2 | Required. GS group function code. Valid value = GF
Load Tender Response Message. |
GF | ||
| GS02 | 1…1 | 2/15 | Required. Application Sender's Code. | 2222224043588 | ||
| GS03 | 1…1 | 2/15 | Required. Application Receiver's Code. | TRACELINK | ||
| GS04 | 1…1 | 8/8 | Required. Current date stamp in 8 char X12 date format YYYYMMDD. | 20241020 | ||
| GS05 | 1…1 | 4/8 | Required. Current time stamp in 6 char X12 time format HHMMSS. | 142000 | ||
| GS06 | 1…1 | 1/9 | Required. Group Control ID Number. | 619827 | ||
| GS07 | 1…1 | 1/2 | Required. Responsible Agency Code. Valid values: T = Transportation Data Coordinating Committee (TDCC) X = Accredited Standards Committee X12 | X | ||
| GS08 | 1…1 | 1/12 | Required. X12 message version code. This could be any X12 version. | 005010 | ||
| ST | 1…* | - | ST transaction set envelope. Child of GS group. Only one ST transaction expected. | - | ||
| ST01 | 1…1 | 3/3 | Required. Transaction set identifier code. | 990 | ||
| ST02 | 1…1 | 4/9 | Required. Transaction set ID number. Counter for each ST segment beginning with 1. | 0001 | ||
| B1 | 1…1 | - | Required. Load Tender Response beginning segment. Note: Add B105, B106 and B107 data element from X12_990_LoadTenderResponse schema. | - | ||
| B101 | 0..1 | 2/4 | Standard carrier alpha code (Carrier SCAC code) | 2ABC | ||
| B102 | 1…1 | 1/30 | Required. Shipment Indentification number given by shipper, ideally this would be the same as in request. | 123212332 | ||
| B103 | 0…1 | 8/8 | Document date in YYYYMMDD format. | 20070609 | ||
| B104 | 0…1 | 1/1 |
Booking confirmation status code.
|
N | ||
| B105 | 0…1 | 1/1 |
Code specifying partial load allowed in booking requirement. Valid values:
|
Y | ||
| B106 | 0…1 | 3/3 |
Code specifying reason behind booking cancel by carrier or customer.
|
CPT | ||
| B107 | 0…1 | 2/2 |
Payment terms for transportation charges. Valid values:
|
CC | ||
| N9 | 0…1 | - | Reference segment for mapping to the transaction references. | - | ||
| N901 | 1…1 | 2/3 |
Required. Reference identification qualifier for the contract class.
|
CT | ||
| N902 | 0…1 | 1/30 | Reference identifier value. | 123456 | ||
| N903 | 0…1 | 1/45 | Description defined by qualifier code in N902. | sub-340B | ||
| N904 | 0…1 | 8/8 | Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year. | 20241215 | ||
| N905 | 0…1 | 4/8 | Time. | 121314 | ||
| L11 | 0…1 | - |
Reference segment for mapping to the transaction references. Note: Add L11 segment from X12_990_LoadTenderResponse schema. |
- | ||
| L1101 | 0…1 | 1/80 | Reference identifier value. | 123456 | ||
| L1102 | 0…1 | 2/3 |
Reference identification qualifier for the contract class.
|
CT | ||
| L1103 | 0…1 | 1/45 | Description defined by qualifier code in REF02. | sub-340B | ||
| L1104 | 0…1 | 8/8 | Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year. | 20241215 | ||
| L1105 | 0…1 | 4/8 | Time. | 121314 | ||
| G62 | 0…1 | - | Dates relevant to motor carrier load tender response events. | - | ||
| G6201 | 0…1 | 2/2 |
Date type related to shipment events at port, in date format YYYYMMDD and time format (IDoc/ X12) HHMMSS.
|
53 | ||
| G6202 | 0…1 | 8/8 | Date defined by referenced date type in date format YYYY-MM-DD. Transform will pass thru whatever it finds in IDoc date and time fields. | 20241215 | ||
| G6203 | 0…1 | 1/2 | Time expressed in 24-hour clock time as follows. | 161025 | ||
| G6204 | 0…1 | 4/8 | Time zone for referenced dates. | ES | ||
| G6205 | 0…1 | 2/2 |
Describes the date format, time format, or date and time period format type. Valid values:
|
DT | ||
| N7 | 0…1 | - | Equipment details used for load tender and load tender response. | - | ||
| N701 | 0…1 | 1/4 | Equipment prefix. | SC | ||
| N702 | 1…1 | 1/10 | Required. Equipment unique identifier. | 1234 | ||
| N703 | 0…1 | 1/10 | Equipment weight value. | 10 | ||
| N704 | 0…1 | 1/2 |
Equipment weight qualifier.
|
B | ||
| N705 | 0…1 | 3/8 | Tare weight value. | 2 | ||
| N706 | 0…1 | 1/6 | Weight allowance provided for increased weight during transport such as snow. | - | ||
| N707 | 0…1 | 1/6 | Lading protected material weight. | - | ||
| N708 | 0…1 | 1/8 | Equipment volume value. | 100 | ||
| N709 | 0…1 | 1/1 |
Equipment volume unit type.
|
B | ||
| N710 | 0…1 | 1/1 | Equipment owner ship code or relationship with equipment. | - | ||
| N711 | 0…1 | 2/2 |
Type of equipment used in delivery. Valid values:
|
CN | ||
| N712 | 0…1 | 2/4 | Equipment owner Standard carrier alpha code (SCAC code). | SCAC | ||
| N713 | 0…1 | 3/6 | Temperature control free form description, like range or flash point. | - | ||
| N714 | 0…1 | 1/3 | Position of equipment in trailer or car or container. | - | ||
| N715 | 0…1 | 4/5 | Length in feet and inches of equipment used in shipment format is FFFII (FFF= feets, II = Inches. If value is 1211 = 12 feet 11 inches | 1211 | ||
| N716 | 0…1 | 1/1 |
Code identifying the type of tare. Valid values:
|
- | ||
| N717 | 0…1 | 1/1 |
Weight unit type code. Valid values:
|
E | ||
| N718 | 0…1 | 1/1 | Equipment number check digit number | 2 | ||
| N719 | 0…1 | 2/2 |
Types of transport service requested which may differ from contract conditions.
|
RE | ||
| N720 | 0…1 | 1/8 | Equipment height used in transport , in inches, can include upto 5 decimals. | 12.234 | ||
| N721 | 0…1 | 1/8 | Shorter measurement of the two horizontal dimensions measured with the object in the upright position , in inches, can include upto 5 decimals. | 12.234 | ||
| N722 | 0…1 | 4/4 | Equipment type ISO Code. | - | ||
| V9 | 0…10 | - | Load Tender Response Shipment event details. | - | ||
| V901 | 1…1 | 3/3 |
Required. Shipment event code.
|
APU | ||
| V902 | 0…1 | 1/25 | shipment Event descriptive information. | Vessel arrived | ||
| V903 | 0…1 | 8/8 | Shipment event time stamp in YYYYMMDD format. | 20070609 | ||
| V904 | 0…1 | '4/8 | Time of reported status of shipment in hhmmss format. | - | ||
| V905 | 0…1 | 2/30 | Event occurred city name. | Texas | ||
| V906 | 0…1 | 2/2 | Event occurred state or province code. | TX | ||
| V907 | 0…1 | 2/3 | Event occurred country code. | UK | ||
| V908 | 0…1 | 3/3 |
Reason indicating why a shipment status code was transmitted.
|
A03 | ||
| V913 | 0…1 | 2/2 | Time zone code. | ES | ||
| K1 | 0…10 | - | Note/Special Instruction. | - | ||
| K101 | 1…1 | 1/30 | Required. Description. | - | ||
| K102 | 0…1 | 1/30 | Description. | Free Form Text | ||
| SE | 1…1 | - | Required. ST … SE transaction set trailer envelope. Child of GS group. Only one ST transaction expected. | - | ||
| SE01 | 1…1 | 1/10 | Required. Total count of segments in ST … SE transaction set including ST and SE segments. | 10 | ||
| SE02 | 1…1 | 4/9 | Required. Transaction set control number | 0001 | ||
| GE | 1…1 | - | Required. GS … GE functional group trailer envelope. Child of ISA interchange. Only one GS group expected. | - | ||
| GE01 | 1…1 | 1/6 | Required. Number of transaction sets in functional group | 5 | ||
| GE02 | 1…1 | 1/9 | Required. Functional group control number | 619827 | ||
| IEA | 1…1 | - | Required. ISA … IEA interchange control trailer envelope. Only one interchange expected per transmission. | - | ||
| IEA01 | 1…1 | 1/5 | Required. Number of functional groups in interchange. | 1 | ||
| IEA02 | 1…1 | 9/9 | Required. Interchange control number | 0000000000619827 |
ISA*00* *00* *ZZ*PAR *11*RV0464646 *190125*0918*>*00401*000000007*0*P*>
GS*IM*PAR*RV0464646*20240126*09123456*828691477*X*004010
ST*990*0001
B1*UPS*SH-14546651*20260402*E*Y*CPU*PO
N9*9X*785222_N9*Desc_N9*20260421*111213
L11*123456*RF*786-GYU*20240915*111114
G62*18*20260410*0*111213*01
N7*s19*ADFJ117778*12.5*T*123*22*22*1.23*C*N*RR*SCAC*N713*714*1234*A*L*1*DD*25*27*N722
V9*ALV*Shipment 103*20260411*12151102*City*MA*BV*A06*V90912*111*11*V912*ET
K1*Carrier Text*Carrier Text2
SE*11*0001
GE*1*828691477
IEA*1*828691477
Tag end


