FourKites X12 204 Motor Carrier Load Tender

A FourKites EDI 204 is an electronic request from a shipper or broker to a carrier to transport a load. It contains the pickup and delivery locations, commodity descriptions, weight, equipment requirements, and requested dates. FourKites sends 204s to carriers in their network to tender freight for acceptance. The carrier responds with a 990 (Response to a Load Tender) to accept or decline. Stacksync processes FourKites 204 tenders automatically, extracting shipment details and routing them to your TMS or dispatch system for immediate action by your operations team.

A FourKites EDI 204 is an electronic request from a shipper or broker to a carrier to transport a load. It contains the pickup and delivery locations, commodity descriptions, weight, equipment requirements, and requested dates. FourKites sends 204s to carriers in their network to tender freight for acceptance. The carrier responds with a 990 (Response to a Load Tender) to accept or decline. Stacksync processes FourKites 204 tenders automatically, extracting shipment details and routing them to your TMS or dispatch system for immediate action by your operations team.

Carriers respond to a FourKites 204 Load Tender with an EDI 990 (Response to a Load Tender). The 990 includes an acceptance or rejection code — carriers can accept the load as tendered, accept with modifications, or decline. FourKites typically expects a 990 response within a specific timeframe (often 30 minutes to 2 hours). Failure to respond may result in the load being retendered to another carrier. Stacksync automates 990 responses based on your fleet capacity and dispatch rules, ensuring timely acceptance of profitable loads and automatic declination when capacity is full.

Carriers respond to a FourKites 204 Load Tender with an EDI 990 (Response to a Load Tender). The 990 includes an acceptance or rejection code — carriers can accept the load as tendered, accept with modifications, or decline. FourKites typically expects a 990 response within a specific timeframe (often 30 minutes to 2 hours). Failure to respond may result in the load being retendered to another carrier. Stacksync automates 990 responses based on your fleet capacity and dispatch rules, ensuring timely acceptance of profitable loads and automatic declination when capacity is full.

A SCAC (Standard Carrier Alpha Code) is a unique 2-to-4 letter identifier assigned by the National Motor Freight Traffic Association (NMFTA) to transportation carriers. FourKites uses SCAC codes in EDI 204 tenders to identify the carrier being tendered the load, and carriers must include their SCAC in the 990 response and subsequent status updates (214). Without a valid SCAC, FourKites's system cannot route the tender or track the shipment. Stacksync stores your SCAC code and automatically includes it in all outbound EDI documents, ensuring proper carrier identification across all FourKites transactions.

A SCAC (Standard Carrier Alpha Code) is a unique 2-to-4 letter identifier assigned by the National Motor Freight Traffic Association (NMFTA) to transportation carriers. FourKites uses SCAC codes in EDI 204 tenders to identify the carrier being tendered the load, and carriers must include their SCAC in the 990 response and subsequent status updates (214). Without a valid SCAC, FourKites's system cannot route the tender or track the shipment. Stacksync stores your SCAC code and automatically includes it in all outbound EDI documents, ensuring proper carrier identification across all FourKites transactions.

Yes, FourKites EDI 204 supports multi-stop shipments through multiple S5 (Stop Off Details) segments. Each stop includes the facility address, stop type (pickup or delivery), scheduled date and time window, and the specific freight being handled at that location. The stops are sequenced to define the route order. Stacksync maps multi-stop FourKites 204 tenders into your TMS routing system, creating individual stop records with proper sequencing so your dispatch team sees the complete route plan without manually parsing the EDI document.

Yes, FourKites EDI 204 supports multi-stop shipments through multiple S5 (Stop Off Details) segments. Each stop includes the facility address, stop type (pickup or delivery), scheduled date and time window, and the specific freight being handled at that location. The stops are sequenced to define the route order. Stacksync maps multi-stop FourKites 204 tenders into your TMS routing system, creating individual stop records with proper sequencing so your dispatch team sees the complete route plan without manually parsing the EDI document.

Stacksync connects to your TMS or dispatch system and processes incoming FourKites 204 tenders in real time. When a tender arrives, Stacksync extracts the shipment details — origin, destination, commodity, weight, equipment type, and pickup/delivery windows — and creates a load record in your system. Based on your capacity rules and lane preferences, Stacksync can auto-accept loads with a 990 response or route them to your dispatch queue for manual review. The platform tracks tender acceptance rates and response times to help you maintain preferred carrier status with FourKites.

Stacksync connects to your TMS or dispatch system and processes incoming FourKites 204 tenders in real time. When a tender arrives, Stacksync extracts the shipment details — origin, destination, commodity, weight, equipment type, and pickup/delivery windows — and creates a load record in your system. Based on your capacity rules and lane preferences, Stacksync can auto-accept loads with a 990 response or route them to your dispatch queue for manual review. The platform tracks tender acceptance rates and response times to help you maintain preferred carrier status with FourKites.