Ripple Foods EDI 204 Load Tender

Schema Reference

30 segments · X12 204 Motor Carrier Load Tender

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

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

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

B202 Standard Carrier Alpha Code

O ID 2-4

B204 Shipment Identification Number

O AN 1-30

B206 Shipment Method of Payment

M ID 2-2

B2A01 Transaction Set Purpose Code

M ID 2-2

L1101 Reference Identification

C AN 1-30

L1102 Reference Identification Qualifier

C ID 2-3

L1103 Description

C AN 1-80

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

G6203 Time Qualifier

C ID 1-2

G6204 Time

C TM 4-8

MS301 Standard Carrier Alpha Code

M ID 2-4

MS302 Routing Sequence Code

M ID 1-2

MS303 City Name

C AN 2-30

MS304 Transportation Method/Type Code

O ID 1-2

MS305 State or Province Code

O ID 2-2

NTE01 Note Reference Code

O ID 3-3

NTE02 Description

M AN 1-80

N1 Loop Repeat: 5

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

G6101 Contact Function Code

M ID 2-2

G6102 Name

M AN 1-60

G6103 Communication Number Qualifier

C ID 2-2

G6104 Communication Number

C AN 1-80

N7 Loop Repeat: 10

N702 Equipment Number

M AN 1-10

N703 Weight

C R 1-10

N704 Weight Qualifier

C ID 1-2

N711 Equipment Description Code

O ID 2-2

N713 Temperature Control

O AN 3-6

S5 Loop Repeat: 999

S501 Stop Sequence Number

M N0 1-3

S502 Stop Reason Code

M ID 2-2

L1101 Reference Identification

C AN 1-30

L1102 Reference Identification Qualifier

C ID 2-3

L1103 Description

C AN 1-80

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

G6203 Time Qualifier

C ID 1-2

G6204 Time

C TM 4-8

AT801 Weight Qualifier

C ID 1-2

AT802 Weight Unit Code

C ID 1-1

AT803 Weight

C R 1-10

AT804 Lading Quantity

O N0 1-7

AT805 Lading Quantity

O N0 1-7

AT806 Volume Unit Qualifier

C ID 1-1

AT807 Volume

C R 1-8

NTE01 Note Reference Code

O ID 3-3

NTE02 Description

M AN 1-80

N1 Loop Repeat: 5

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

G6101 Contact Function Code

M ID 2-2

G6102 Name

M AN 1-60

G6103 Communication Number Qualifier

C ID 2-2

G6104 Communication Number

C AN 1-80

L5 Loop Repeat: 99

L501 Lading Line Item Number

O N0 1-3

L502 Lading Description

O AN 1-50

L503 Commodity Code

C AN 1-30

L504 Commodity Code Qualifier

C ID 1-1

L508 Commodity Code Qualifier

C ID 1-1

L509 Commodity Code

C AN 1-30

AT801 Weight Qualifier

C ID 1-2

AT802 Weight Unit Code

C ID 1-1

AT803 Weight

C R 1-10

AT804 Lading Quantity

O N0 1-7

AT805 Lading Quantity

O N0 1-7

AT806 Volume Unit Qualifier

C ID 1-1

AT807 Volume

C R 1-8

G61 Loop Repeat: 99

G6101 Contact Function Code

M ID 2-2

G6102 Name

M AN 1-60

G6103 Communication Number Qualifier

C ID 2-2

G6104 Communication Number

C AN 1-80

LH1 Loop Repeat: 25

LH101 Unit or Basis for Measurement Code

M ID 2-2

LH102 Lading Quantity

M N0 1-7

LH103 UN/NA Identification Code

O ID 6-6

LH105 Commodity Code

O AN 1-30

LH110 Packing Group Code

O ID 1-3

OID Loop Repeat: 999

OID01 Reference Identification

C AN 1-30

OID06 Weight Unit Code

C ID 1-1

OID07 Weight

C R 1-10

OID08 Volume Unit Qualifier

C ID 1-1

OID09 Volume

C R 1-8

L301 Weight

C R 1-10

L302 Weight Qualifier

C ID 1-2

L305 Charge

O N2 1-12

L312 Weight Unit Code

O ID 1-1

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Ripple Foods EDI 204 FAQ

Common questions about 204 Motor Carrier Load Tender transactions with Ripple Foods.

How long does it take to set up Ripple Foods EDI with Stacksync?

Most suppliers are fully connected and processing live Ripple Foods EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Ripple Foods?

No. Stacksync handles the entire EDI transport layer. We connect directly to Ripple Foods's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Ripple Foods compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Ripple Foods?

Stacksync supports all EDI document types required by Ripple Foods — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Ripple Foods EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Ripple Foods's EDI network and your system in real time.

What happens when Ripple Foods updates their EDI specifications?

Stacksync monitors Ripple Foods's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.