EDI Overview
This article provides a comprehensive overview of the EDI features available in EZ Loader and explains how the integration functions between our system and your shipper.
Summary
Electronic data interchange (EDI) is a standardized way for businesses to exchange information electronically between computer systems.
EZ Loader (EZL) partners with BitFreighter (BF) to manage all EDI connections.
BitFreighter acts as a translator between your shippers system and EZ Loader.
Please contact support@ezloadertms.com if you are interested in an EDI connection and would like an introduction to BitFreighter.
Supported EDI codes:
204 - Load Tender
BF will first receive a 204 Load Tender from your shipper, translate it into a format accepted by EZL and pass those shipment details on to your EZL account. EZL will then automatically build the load with the shipment details.
List of supported load details from 204:
- Mode (TL/LTL)
- Equipment Type
- PO#
- Cargo Value
- Customer Charges/Rate
- Reference #
- Stop Number
- Stop Name
- Stop Date
- Stop Contact Info
- Stop Address
- Pickup/Deliver #
- Stop Note
- Early / Late Time
- Item Description
- Item Quantity, Weight, and Dimensions
- Load Note / Special Instructions
When EZL receives a 204 (Load Tender) from BF, EZL automatically builds the load with the provided shipment details.
Note: The 204 is first received and held by BF until the client accepts/releases the tender. Auto acceptance is an available setting in BF.
990 - Response to Load Tender
When EZL receives a 204 from BF, EZL automatically builds the load and returns a 990 (Response to Load Tender) back through BF to acknowledge receipt and successful load creation.
214 - Shipment Status Update
There are 4 main sub 214 messages that are sent from EZL
-
Arrived at Pickup (X3)
-
Departed Pickup (AF)
-
Arrived at Delivery (X1)
-
Departed Delivery (D1)
These 214 messages are triggered by the check calls in the load profile.
Note: If a tracking integration is active and set to log check calls, those tracking events will automatically trigger 214 messages to be sent. There is an setting to disable this automation.
Click Here for Detailed Help Article on 214 Status Updates
X6 - Subcode of a 214 for continuous in-transit location updates
This 214 Subcode is sent at scheduled intervals while the load is in transit and includes updated latitude and longitude coordinates.
Note: This Subcode requires an active tracking integration to return lat/long location data to EZL. The updates do not start until the driver has departed the origin and they stop upon arrival at the destination.
Click Here for Detailed Help Article on X6's
210 - Invoices
When a shipment is invoiced in EZL, a 210 is transmitted from EZL to BF containing the invoice details. BF then forwards these invoice details to the designated recipient's system for final processing.
**Note** Enabling the 210 is optional and can be configured at the customer level.