Documentation on sending load location or status updates in a EDI 214 (.edi) file over our SFTP/FTP(s) server.
For server host and port, please ping your Chaine technical contact
All files go directly inside the home directory:
Our server is event-based, so as soon as a file is placed in the root, it will get processed. Older files will be purged by default after 30 days.
- Username: This will be provided to you upon setup.
- Password: Will be provided to you upon setup.
For SFTP, username and password will also work. For additional security, a public-private SSH keypair can be used.
What statuses are required?
Although each connections's required mapping depends on the customer, most customers require the following for EDI 214s:
1. Milestone for each stop
- Arrival for each pick and drop
- Deparated (loaded/unloaded) for each pick and drop
ST, B10, AT7 and L11 must be included in each milestone. MS1 and MS2 are optional.
2. Location every 15 minutes (ETA)
- ETA to pickup location with latitude/longitude of the shipment or equipment's location.
- ETA to delivery location with latitude/longitude of the shipment or equipment's location.
How your file will be matched to a load
The GS header will map to a specific customer. The load number will then be matched to the customer.
GS Header maps to a specific customer
Chaine will provide a unique ISA ID for a specific that begins with AC . This is referred to as the Client ID and is also used in the GS header. This is used the file to a specific Cahine customer.
Load number is matched to the customer
The load number is then matched to the customer represented by the GS header.