X12
Outbound

Kimberly X12 990 Response to a Load Tender

Kimberly-Clark (via Blue Yonder)
The EDI 990 is the carrier's response to a Kimberly 204 Load Tender — accepting, rejecting, or countering the shipment request. Timely responses are critical to maintaining preferred carrier status.
6segments
0loops
5mandatory

Schema Reference

6 segments · X12 990 Response to a Load Tender

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Interchange Control Standards Identifier
M ID 1-1
ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
B1 Beginning Segment for Booking or Pick-up/Delivery
Mandatory Max: 1
B101 Standard Carrier Alpha Code
O ID 2-4
B102 Shipment Identification Number
M AN 1-30
B104 Reservation Action Code
O ID 1-1
N9 Reference Identification
Optional Max: 1
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-30
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Kimberly EDI 990

Stacksync validates, transforms, and delivers your 990 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync sends 990 Load Tender Responses from your TMS automatically when your dispatch team accepts or rejects a Kimberly load — ensuring fast response times and carrier compliance.

Kimberly EDI 990 FAQ

Common questions about 990 Response to a Load Tender transactions with Kimberly.

What is a Kimberly EDI 990 Response to a Load Tender?

A Kimberly EDI 990 is the carrier's response to a 204 Motor Carrier Load Tender. It communicates whether the carrier accepts, rejects, or conditionally accepts the tendered load. The B1 segment contains the response code: A (accepted), D (declined), or other qualifiers for conditional responses. The 990 references the original 204 by shipment ID so Kimberly can match the response to the correct load. Stacksync generates 990 responses automatically based on your fleet capacity and lane preferences, ensuring timely tender responses that protect your preferred carrier standing with Kimberly.

How quickly must a Kimberly EDI 990 be sent after receiving a 204?

Kimberly typically expects an EDI 990 response within 30 minutes to 2 hours of sending the 204 Load Tender. The exact window depends on Kimberly's tender process — some use a waterfall approach where the load is automatically retendered to the next carrier if no 990 is received within the time limit. Slow responses mean lost loads and reduced tender volume over time. Stacksync processes incoming Kimberly 204 tenders and generates 990 responses in real time, often within seconds, based on your pre-configured acceptance rules so you never miss a tender deadline.

What happens if I decline a Kimberly EDI 204 with a 990 rejection?

When you send a Kimberly 990 with a decline code (D), Kimberly's system removes you from consideration for that specific load and retenders it to the next carrier in their routing guide. Declining loads is normal and expected — carriers cannot accept every tender. However, consistently declining Kimberly tenders may reduce your standing in their carrier ranking and lead to fewer tender opportunities over time. Stacksync tracks your acceptance ratio for Kimberly and alerts you when declining too many loads might impact your preferred carrier status.

Can Stacksync auto-accept Kimberly EDI 204 tenders with a 990?

Yes. Stacksync can automatically generate a 990 acceptance response when a Kimberly 204 matches your configured criteria — such as approved lanes, equipment type availability, weight limits, and date range. You define the rules once, and Stacksync evaluates each incoming tender against them. Loads that match are accepted automatically with a 990, while loads outside your criteria are either declined or routed to your dispatch team for manual decision. This hybrid approach ensures you capture desirable Kimberly loads instantly while maintaining human oversight for edge cases.

How does Stacksync handle Kimberly EDI 990 for multi-stop loads?

When a Kimberly 204 includes multiple stops (S5 segments), Stacksync evaluates the entire route before generating the 990 response — not just the origin and destination. The platform checks capacity for each stop, validates that pickup and delivery windows are feasible given transit times, and confirms equipment compatibility at every location. If all stops meet your criteria, Stacksync sends a 990 acceptance for the full multi-stop load. If any stop presents a conflict, the platform flags it for your dispatcher rather than auto-declining the entire tender.

Ready to automate Kimberly EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding