Skip to content
X12 EDI

Mercury Gate X12 204 Motor Carrier Load Tender

Plan X12 204 Motor Carrier Load Tender for HD Supply via Mercury Gate. Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
25
Loops
7
X12 204
Partner references ↗
Book an EDI demo ← All HD Supply via Mercury Gate transactions

Implementation guide

HD Supply via Mercury Gate: 204 mapping and validation

X12 204 Motor Carrier Load Tender is used when a shipper offers a load to a carrier. Preserve load reference, pickup and delivery stop identifiers so the load tender in your business system stays connected to the original document.

This document is listed for HD Supply via Mercury Gate. Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record load tender

load reference, pickup and delivery stop identifiers
  • Define which combination of load reference, pickup and delivery stop identifiers identifies one business record, its lines and any later revision.
Update the receiving system Processing the load tender

ID assigned by the receiving system and processing result
  • Send an amended pickup appointment and retain the previous tender decision.
  • Test a multi-stop load whose stop sequence differs from address sorting.
Check the processing result Processing status for the load tender

Original document reference and matching response
  • Reconcile the load tender with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

The document reference includes 25 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a shipper offers a load to a carrier. Name the operational owner of the load tender and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map load reference, pickup and delivery stop identifiers. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Mercury Gate guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic load tender data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful load tender processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 204 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic load tender data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out load tender without processing it twice.

Transaction context

Where 204 Motor Carrier Load Tender fits on HD Supply via Mercury Gate

On HD Supply via Mercury Gate, the X12 204 Motor Carrier Load Tender can precede the 990 Response To A Load Tender, 214 Transportation Carrier Shipment Status Message and 210 Motor Carrier Freight Details And Invoice in an example Logistics cycle. Confirm the required sequence for your trading agreement.

Mercury Gate channels
12 of 12

12 of Mercury Gate's 12 channels list 204

Trading partners
386

partner references list 204

Channels
534

channel entries list 204

Frequently listed alongside 204

The directory associates MercuryGate and 204 with 35 channels.

Document structure

X12 204 Motor Carrier Load Tender at the element level

The X12 204 reference contains 82 segment entries and 470 data elements; 63 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
82
Data elements
470
Mandatory elements
63
Segments with elements marked mandatory in this reference
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
Segment reference — 25 segments 7 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

L11 Business Instructions and Reference Number 3 elements

To specify instructions in this business relationship or a reference number

AT5 Bill of Lading Handling Requirements 3 elements

To identify Bill of Lading handling and service requirements

PLD Pallet Information 1 element

To specify pallet information including quantity, exchange, and weight

NTE Note/Special Instruction 2 elements

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

N1 Loop Repeat: 5
N1 Name 4 elements

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

N3 Address Information 2 elements

To specify the location of the named party

N4 Geographic Location 4 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

N7 Loop Repeat: 10
N7 Equipment Details 3 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

G62 Date/Time 4 elements

To specify pertinent dates and times

AT8 Shipment Weight, Packaging and Quantity Data 4 elements

To specify shipment details in terms of weight, and quantity of handling units

L3 Total Weight and Charges 6 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)

L5 Loop Repeat: 99
L5 Description, Marks and Numbers 6 elements

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

G61 Loop Repeat: 99
OID Loop Repeat: 999
OID Order Identification Detail 2 elements

To specify order identification detail

LH1 Loop Repeat: 25
LH1 Hazardous Identification Information 7 elements

To specify the hazardous commodity identification reference number and quantity

LH2 Hazardous Classification Information 4 elements

To specify the hazardous notation and endorsement information

LH3 Hazardous Material Shipping Name 3 elements

To specify the hazardous material shipping name and additional descriptive requirements

LFH Freeform Hazardous Material Information 2 elements

To uniquely identify the variable information required by government regulation covering the transportation of hazardous material shipments

Related references

204 Motor Carrier Load Tender on other Mercury Gate channels

Compare the listed channel references and confirm their current implementation guides.

Veritiv Operating Company via Mercury Gate X12 204 Amstan Logistics via Mercury Gate X12 204 Geodis Logistics via Mercury Gate X12 204 Ferguson Enterprises via MercuryGate X12 204 Mercury Gate (Generic)(Templates) X12 204 Atrium via Mercury Gate X12 204 THE CONTAINER STORE - OTR X12 204 Graphic Packaging Spot via Mercury Gate X12 204 Moen via Mercury Gate X12 204 Sartori Cheese (via MercuryGate) X12 204 Molnlycke Health Care via Mercury Gate X12 204

Showing 11 of 11 references

Browse the full directory

Related references

Other transactions in HD Supply via Mercury Gate

Other EDI documents listed on this channel.

Response To A Load Tender X12 990 Transportation Carrier Shipment Status Message X12 214 Motor Carrier Freight Details And Invoice X12 210

Showing 3 of 3 references

Browse the full directory

HD Supply via Mercury Gate EDI 204 questions

Common questions about 204 Motor Carrier Load Tender on the HD Supply via Mercury Gate channel.

What is X12 204 Motor Carrier Load Tender used for?

204 is used when a shipper offers a load to a carrier. It carries information for the load tender. Match it to your business system using load reference, pickup and delivery stop identifiers.

Is 204 required for HD Supply via Mercury Gate?

204 is listed for HD Supply via Mercury Gate. Confirm the required version and direction for your business unit and account with the partner.

What should I map for X12 204?

Start with load reference, pickup and delivery stop identifiers and the target load tender. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 204 error handling?

Send an amended pickup appointment and retain the previous tender decision. Test a multi-stop load whose stop sequence differs from address sorting. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 204 relate to other EDI messages?

X12 990 Response To A Load Tender; X12 214 Transportation Carrier Shipment Status Message; X12 210 Motor Carrier Freight Details And Invoice are related documents also listed on HD Supply via Mercury Gate. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 204 and 990?

204 is used when a shipper offers a load to a carrier. 990 is used when a carrier responds to a tender. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

What is the difference between 204 and 214?

204 is used when a shipper offers a load to a carrier. 214 is used when the carrier reports a transport milestone or exception. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect Mercury Gate EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform