Channel
DHL (formerly Exel) (US and CAN)
Plan a reliable EDI exchange for DHL (formerly Exel) (US and CAN). Explore 4 document references, map them to your business records and test the complete workflow before launch.
- Documents
- 4 transactions
- Standards
- X12
- Implementation
- Mapping and launch plan
Implementation guide
DHL (formerly Exel) (US and CAN): EDI implementation plan
Build a reliable EDI workflow for DHL (formerly Exel) (US and CAN). Use 4 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 204 Motor Carrier Load TenderListed for DHL (formerly Exel) (US and CAN) | load tender load reference, pickup and delivery stop identifiers |
|
| X12 990 Response To A Load TenderListed for DHL (formerly Exel) (US and CAN) | load-tender response original load reference, carrier and response |
|
| X12 214 Transportation Carrier Shipment Status MessageListed for DHL (formerly Exel) (US and CAN) | shipment status event shipment reference, event code, event time and location |
|
| X12 210 Motor Carrier Freight Details And InvoiceListed for DHL (formerly Exel) (US and CAN) | freight invoice carrier invoice, shipment reference and charge line |
|
Implementation steps
-
Choose the trading account and channel
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for DHL (formerly Exel) (US and CAN). Compare other DHL (formerly Exel) (US and CAN) channels before reusing a mapping.
-
Map records and assign owners
Start with load tender, load-tender response, shipment status event. 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.
-
Test a complete exchange
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 DHL (formerly Exel) (US and CAN) production handoff and save the results of each approved test.
-
Check results after launch
Match records between systems using load reference, pickup and delivery stop identifiers. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Go-live checklist
- The required X12 documents, versions and sample files are agreed.
- Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
- Delivery receipts, document validation and business responses have monitoring and a named owner.
- Tests cover duplicates, partial processing and reconciliation with realistic business records.
Document catalog
EDI documents listed for DHL (formerly Exel) (US and CAN)
4 EDI transactions listed in this catalog.
Document flow on this channel
Document relationships on DHL (formerly Exel) (US and CAN)
This channel lists all 4 document types in the DHL (formerly Exel) (US and CAN) directory. Example relationships are shown below; confirm the required sequence in the channel guide.
DHL (formerly Exel) (US and CAN) questions
Which EDI documents are listed for DHL (formerly Exel) (US and CAN)?
X12 204 Motor Carrier Load Tender; X12 990 Response To A Load Tender; X12 214 Transportation Carrier Shipment Status Message; X12 210 Motor Carrier Freight Details And Invoice. Confirm which documents, directions and versions apply to your account.
How should I choose the DHL (formerly Exel) (US and CAN) EDI channel?
DHL (formerly Exel) (US and CAN) lists 4 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.
Which identifiers should the DHL (formerly Exel) (US and CAN) mapping preserve?
For X12 204 Motor Carrier Load Tender, plan around load reference, pickup and delivery stop identifiers. 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.
Does a successful EDI receipt mean DHL (formerly Exel) (US and CAN) accepted the business document?
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.
What should be tested before launching DHL (formerly Exel) (US and CAN) EDI?
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 missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
Connect DHL (formerly Exel) (US and CAN) 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.
