Skip to content
X12 EDI

Starbucks Coffee Company X12 204 Motor Carrier Load Tender

X12 204 (Motor Carrier Load Tender) is the EDI transaction exchanged between Starbucks Coffee Company (Starbucks Coffee Company (ISA ID: SBUXCT4)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
21
Loops
6
X12 204
All partners ↗

Transaction context

Where 204 Motor Carrier Load Tender fits on Starbucks Coffee Company (ISA ID: SBUXCT4)

On Starbucks Coffee Company (ISA ID: SBUXCT4), the X12 204 Motor Carrier Load Tender precedes the 990 Response To A Load Tender and 214 Transportation Carrier Shipment Status Message in the Logistics cycle.

Starbucks Coffee Company channels
2 of 3

2 of Starbucks Coffee Company's 3 channels carry 204

Trading partners
386

partners across the Stacksync network trade 204

Channels
534

channels network-wide carry 204

The 204 carries a shipper's or broker's offer of a truckload shipment to a motor carrier, including pickup and delivery scheduling, stop-off details, equipment requirements, commodities, and shipping instructions. It opens the routing-guide tender cycle: the carrier answers with a 990 Response to Load Tender, then reports movement on 214 status messages and bills on a 210 freight invoice. Trading partners require it because dispatch, tracking, and freight-pay matching all key off the tender's reference numbers. A shipper, freight broker, or 3PL responsible for contracting the move sends the 204 to a full-truckload motor carrier.

When it fires: A shipper's TMS plans a truckload and tenders it to the next carrier in the routing guide, requesting acceptance before the stated respond-by time.

Common 204 rejection causes
  • Missing or wrong mandatory header data: ST, B2, and B2A are must-use segments, and an incorrect Standard Carrier Alpha Code in B2 routes the tender to the wrong carrier or fails validation.
  • Slow or missing 990 responses: shippers expect acceptance or rejection within a defined window (the header G62 carries the must-respond-by date and time), and late answers damage the carrier's standing with the shipper.
  • Stop-level weight reconciliation failures: totals in the stop-off AT8 segment (loop 0300) must equal the accumulated commodity-level AT8 amounts (loop 0320), and mismatches break rating and downstream invoice audit.
  • Loop misuse: specifications require the LAD lading detail and G62 dates in either loop 0300 or loop 0350, not both, and order-level detail sent in the wrong loop fails partner validation.

Specification summary

X12 204 Motor Carrier Load Tender at the element level

The X12 204 specification defines 82 segments carrying 470 data elements, 63 of which are mandatory.

Segments
82
Data elements
470
Mandatory elements
63
Segments with mandatory elements
Segment Elements Mandatory
B2 12 1
B2A 2 1
MS3 5 2
PLD 4 1
NTE 2 1
N1 6 1
N2 2 1
N3 2 1
G61 5 2
N7 24 1
M7 5 1
S5 11 2
Key identifiers in 204
  • Shipment Method of Payment
  • Transaction Set Purpose Code
  • Standard Carrier Alpha Code
  • Routing Sequence Code
  • Quantity of Pallets Shipped
  • Description
  • Entity Identifier Code
  • Name
Full segment guideline — 21 segments 6 loops · X12 204 Motor Carrier Load Tender
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

B2 Beginning Segment for Shipment Information Transaction 3 elements

To transmit basic data relating to shipment information

B2A Set Purpose 2 elements

To allow for positive identification of transaction set purpose

C3 Currency Identifier 1 element

To specify the currency being used in the transaction set

L11 Business Instructions and Reference Number 2 elements

To specify instructions in this business relationship or a reference number

G62 Date/Time 5 elements

To specify pertinent dates and times

AT5 Loop Repeat: 6
AT5 Bill of Lading Handling Requirements 5 elements

To identify Bill of Lading handling and service requirements

N7 Loop Repeat: 10
N7 Equipment Details 2 elements

To identify the equipment

S5 Loop Repeat: 999
S5 Stop-off Details 2 elements

To specify stop-off detail reference numbers and stop reason

NTE Note/Special Instruction 2 elements

To transmit information in a free-form format, if necessary, for comment or special instruction

N1 Loop Repeat: 1
N1 Party Identification 4 elements

To identify a party by type of organization, name, and code

L3 Total Weight and Charges 7 elements

To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

N2 Additional Name Information 1 element

To specify additional names

N3 Party Location 2 elements

To specify the location of the named party

N4 Geographic Location 6 elements

To specify the geographic place of the named party

G61 Contact 4 elements

To identify a person or office to whom communications should be directed

L5 Loop Repeat: 99,999
L5 Description, Marks and Numbers 5 elements

To specify the line item in terms of description, quantity, packaging, and marks and numbers

OID Loop Repeat: 99,999
OID Order Information Detail 4 elements

To specify order information detail

Trading partners

1+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Browse the full directory

Trading partners

4+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Starbucks Coffee Company Starbucks Coffee Company (ISA ID: SBUXCT4) EDI 204 FAQ

Common questions about 204 Motor Carrier Load Tender on the Starbucks Coffee Company (ISA ID: SBUXCT4) channel.

What is X12 204 Motor Carrier Load Tender?
X12 204 (Motor Carrier Load Tender) is the EDI transaction set used to exchange motor carrier load tender data. Starbucks Coffee Company's Starbucks Coffee Company (ISA ID: SBUXCT4) channel requires it from trading partners.
Does Starbucks Coffee Company Starbucks Coffee Company (ISA ID: SBUXCT4) require 204 for trading partners?
Yes, Starbucks Coffee Company (Starbucks Coffee Company (ISA ID: SBUXCT4)) supports X12 204 Motor Carrier Load Tender. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Starbucks Coffee Company 204 with Stacksync?
Most companies go live with Starbucks Coffee Company 204 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other Starbucks Coffee Company channels accept 204?
X12 204 runs on 2 of Starbucks Coffee Company's 3 channels. Besides Starbucks Coffee Company (ISA ID: SBUXCT4), it is accepted on Starbucks Coffee Company (ISA ID: SBUXGTMSP). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.

Ready to automate your Starbucks Coffee Company EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.