Overview
Understanding Ruan Transportation Management Systems integration
Who this is for: Shippers that use Ruan dedicated or managed transportation, brokers and carriers that trade with Ruan, and their transportation and finance teams.
Scope: Ruan publishes its EDI setup form and connection methods but not its document list or specifications. The documents shown are commonly used for dedicated, managed and brokerage freight, not Ruan's published list.
Ruan describes itself as one of the largest family-owned transportation management companies in the United States, founded in 1932. Its services include dedicated contract transportation, managed transportation, contract distribution and fulfillment, freight brokerage and customs brokerage. Ruan Transportation Management Systems is the name used for its transportation management business in company directories.
Ruan publishes an EDI communication request form so its EDI team can set up a trading partner in its systems. The form asks whether you are a customer, brokerage, carrier or other partner, and offers three connection methods: SFTP hosted by Ruan, SFTP hosted on your own server, or AS2. SFTP uses an SSH public key plus a password, and AS2 uses certificates with AES encryption and SHA signatures, on standard ports 22 and 4080 or a custom port. Ruan does not publish its list of EDI documents. The documents a customer commonly exchanges with a transportation provider are the 204 tender, 990 response, 214 status and 210 invoice, and those are described here as typical practice.
ECOM helps confirm your program with Ruan, map the documents to your TMS and ERP, configure SFTP or AS2, complete testing and monitor every file after go-live.