This guide outlines the key steps and considerations for using electronic dispatching to send load requests to carriers.
Electronic Dispatching Overview
Electronic dispatching allows seamless communication with carriers through EDI (Electronic Data Interchange) or API (Application Programming Interface). These methods streamline the process of sending pickup requests and receiving acknowledgments.
- API: A fully automated and efficient system requiring minimal human interaction once configured.
- EDI: A manual process where dispatch requests are sent to carriers like emails, requiring them to open and process the information. This can lead to delays of up to three hours or more.
For more details, refer to the General Overview: API vs EDI
The Importance of the "Ready" Status
The "Ready" status is vital for triggering dispatches in the system.
- Automatic Dispatch: When a shipment is updated to "Ready", the system automatically sends the dispatch (pickup request) to the carrier.
- No Dispatch: If the shipment is not set to "Ready" or is manually marked as "Dispatched" without first being "Ready", the dispatch will not be sent.
Handling Dispatch Failures
If a dispatch fails:
- The system will display the alert "Rejected By Carrier".
- The shipment status will change to "Sent" automatically.
- The Activity Log will capture any specific error messages provided by the carrier, enabling users to identify and resolve issues before retrying.
- A "Dispatch Again" button will appear, allowing you to resend the request once the issue is addressed.
NOTE: If the API attempt is unsuccessful, but we have an EDI connection with the carrier, we will use EDI as a failsafe to ensure the shipment is dispatched successfully.
You can request more information about which carriers have which integrations by reaching out to IT.
Note: