Logistics
Some example steps listed- 204 Motor Carrier Load Tender
- 990 Response To A Load Tender
- 214 Transportation Carrier Shipment Status Message
- 210 Motor Carrier Freight Details and Invoice not listed on Keurig (via Ryder)
Channel
Plan a reliable EDI exchange for Keurig (via Ryder). Explore 3 document references, map them to your business records and test the complete workflow before launch.
Implementation guide
Build a reliable EDI workflow for Keurig (via Ryder). Use 3 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.
The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 214 Transportation Carrier Shipment Status MessageListed for Keurig (via Ryder) | shipment status event shipment reference, event code, event time and location |
|
| X12 990 Response To A Load TenderListed for Keurig (via Ryder) | load-tender response original load reference, carrier and response |
|
| X12 204 Motor Carrier Load TenderListed for Keurig (via Ryder) | load tender load reference, pickup and delivery stop identifiers |
|
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Keurig (via Ryder). Compare other Ryder channels before reusing a mapping.
Start with shipment status event, load-tender response, load tender. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.
Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Ryder production handoff and save the results of each approved test.
Match records between systems using shipment reference, event code, event time and location. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Document catalog
3 EDI transactions listed in this catalog.
Document flow on this channel
This channel lists 3 of the 4Ryder document types; other entries appear on Ryder channels (listed below). Example relationships are shown below; confirm the required sequence in the channel guide.
Network onboarding
The directory associates Ryder with 8 partner entries across 32 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.
X12 214 Transportation Carrier Shipment Status Message; X12 990 Response To A Load Tender; X12 204 Motor Carrier Load Tender. Confirm which documents, directions and versions apply to your account.
Keurig (via Ryder) lists 3 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.
For X12 214 Transportation Carrier Shipment Status Message, plan around shipment reference, event code, event time and location. For X12 990 Response To A Load Tender, use original load reference, carrier and response. Use the partner guide to locate these values and check their allowed formats.
Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.
Deliver an older status after a newer one and retain event history without moving the current status backward. Send one milestone twice and avoid duplicate customer notifications. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
Related references
Compare the document lists for other Ryder channels.
Showing 20 of 20 references
Browse the full directorySee 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.