Perishable delivery windows
Late deliveries to receivers lead to rejections or chargebacks.
How ECOM helps: ECOM brings status events into your TMS and flags late or missing updates early.
What you gain: Time to act before a window is missed.
Carriers integration
How EDI and API integration with Leonard's Express typically works: truckload freight documents, workflows, onboarding and common problems, as typical practice to confirm with Leonard's Express.
At a glance
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Leonard's Express program or a customer relationship.
Tell us which documents you exchange with Leonard's Express, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Leonard's Express.
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
Overview
Who this is for: Shippers, brokers and logistics providers that move truckload freight with Leonard's Express, and their transportation, customer service and finance teams.
Scope: This guide describes typical practice for this kind of trading relationship; Leonard's Express's own program details are confirmed during onboarding.
Leonard's Express is a refrigerated truckload carrier in the northeastern United States serving food and perishable shippers with temperature-controlled capacity. ECOM's directory lists Leonard's Express under Refrigerated.
Perishable freight depends on pickup and delivery windows and temperature records, and food shippers commonly tie status exceptions to quality and claims processes. With a truckload carrier the daily work is the tender cycle: a load is offered, accepted or declined, tracked through pickup and delivery, and billed with line haul, fuel and accessorial charges. Appointment changes, detention and lumper charges are where invoices most often drift from the original rate confirmation. The document set below is typical practice for this type of company; confirm the documents, X12 version, delivery method and testing steps with Leonard's Express for your own program.
ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications. It then monitors every file after go-live and handles partner changes, as software, as a managed service or both.
Business scenarios
Typical requirements—confirm with your trading partner.
Late deliveries to receivers lead to rejections or chargebacks.
How ECOM helps: ECOM brings status events into your TMS and flags late or missing updates early.
What you gain: Time to act before a window is missed.
Claims need load-level temperature proof.
How ECOM helps: ECOM links exception messages to the load and order.
What you gain: Stronger claim support.
Workflows
Typical requirements—confirm with your trading partner. Typical flows in this industry, not Leonard's Express' published process.
Documents and APIs
General guidance. We could not verify Leonard's Express' EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Leonard's Express' confirmed requirements. Confirm the list, versions and programs with Leonard's Express.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Program | Status | Purpose |
|---|---|---|---|---|---|
| 204 | Motor Carrier Load Tender | To Leonard's Express | Not stated | General guidance | Typically offers a load to the carrier with pickup, delivery, equipment and reference details. |
| 990 | Response to a Load Tender | From Leonard's Express | Not stated | General guidance | Typically accepts or declines the offered load. |
| 214 | Transportation Carrier Shipment Status Message | From Leonard's Express | Not stated | General guidance | Typically reports pickup, in-transit events, appointment and delivery. |
| 210 | Motor Carrier Freight Details and Invoice | From Leonard's Express | Not stated | General guidance | Typically bills for freight with charge detail in the shipper payables format. |
| 997 | Functional Acknowledgment | Both directions | Not stated | General guidance | Typically confirms each file was received and could be read. |
Connectivity
Carriers commonly exchange EDI over AS2, SFTP or a value-added network.
General guidance
Many carriers also provide tracking, tender or location APIs beside EDI.
General guidance
Some carriers work through a customer portal or a transportation management network instead of, or beside, direct EDI.
General guidance
Challenges
Strict receiver windows leave little slack.
Temperature records must be tied to the load.
The documents, identifiers, versions and test steps for your program are set by Leonard's Express. ECOM works from them during mapping and testing.
Automation options for Leonard's Express shippers
ECOM helps you automate the exchange, connect it to your systems, and see what needs action. Leonard's Express sets its own requirements; ECOM confirms which options fit yours.
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/APIReceive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDIConvert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvertAutomate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
Learn more about WebConnectPRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.
ECOM connects the load, status and invoice documents you exchange with Leonard's Express to your TMS, WMS and ERP, so tenders, status and freight bills move without re-keying and exceptions are visible early.
Integrate truckload, LTL and brokerage tenders, status and invoices.
IndustrySee how ECOM supports shippers, carriers, brokers and forwarders.
SolutionAutomate tenders, status, appointments and freight invoices.
ServiceHave ECOM run your EDI connections, monitoring and partner changes.
Zero Trust for freight data exchange
Freight exchanges with Leonard's Express carry tenders, status events, rates and freight invoices. A Zero Trust design assumes no connection, file or user is safe by default.
ECOM has implemented Zero Trust EDI and Zero Trust MFT in trucking.
For freight exchanges this means each carrier has its own scope, tenders, status messages and invoices are checked at the connection and the file, a late or missing file is noticed early, and every transfer has a record for freight billing disputes and security reviews.
Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.
Business outcome: A lost or reused credential affects one partner, not all of them.
Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.
Business outcome: A mistake or compromise in one account stays limited to what that account could reach.
Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.
Business outcome: Outside connections do not land directly on your internal systems.
Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.
Business outcome: Less exposure if a file is intercepted or a file store is reached.
Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.
Business outcome: Fewer outages caused by an expired certificate or key.
Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.
Business outcome: Late, missing or failed files are noticed early, before they hold up tenders, status or freight billing.
Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.
Business outcome: You can answer who sent what and when, for your own audits and partner reviews.
Each carrier or broker gets its own identity and scope. A new carrier is tested before it reaches production, and a removed carrier loses access without affecting the others.
Load tenders, status messages and freight invoices are checked at the connection and the file, and every transfer is logged.
Rate and accessorial files are limited to the roles that need them.
Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Leonard's Express may set its own security requirements, which come first.
Talk to an EDI/API Expert about Zero Trust Managed file transferSecure proxy and DMZ designSecurity at ECOM
General EDI flow
The documents, their order and the timing are Leonard's Express' to set; this is the general sequence most programs of this kind follow.
204 Motor Carrier Load Tender
From you to Leonard's Express
Typically offers a load to the carrier with pickup, delivery, equipment and reference details.
990 Response to a Load Tender
From Leonard's Express to you
Typically accepts or declines the offered load.
214 Transportation Carrier Shipment Status Message
From Leonard's Express to you
Typically reports pickup, in-transit events, appointment and delivery.
210 Motor Carrier Freight Details and Invoice
From Leonard's Express to you
Typically bills for freight with charge detail in the shipper payables format.
997 Functional Acknowledgment
Both directions
Typically confirms each file was received and could be read.
Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.
Next step
Each request goes to an ECOM EDI specialist with Leonard's Express' name attached, so the reply starts from your program.
Send us Leonard's Express' guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements reviewTenders, status and freight invoices in and out of the TMS, ERP and finance systems you already run.
Discuss ERP integrationBuild, test and certify each Leonard's Express document, then go live with monitoring from the first file.
Plan testing and certificationCompanies of this type commonly exchange EDI or APIs with their customers and partners. This guide reflects typical industry practice rather than Leonard's Express's published requirements.
Refrigerated freight carries temperature and timing requirements, so status and exception data matter more than for dry freight.
Typical documents are 204, 990, 214, 210, 997. That is general practice, not Leonard's Express's published list.
Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on Leonard's Express's requirements, test cycles and your ERP.
No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Leonard's Express.
This guide summarizes publicly available information as of November 2026. Leonard's Express sets its own requirements and can change them at any time; your Leonard's Express implementation guide, supplier portal or account contact is the authoritative source for your program.
Leonard's Express is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
How EDI and API integration with Marten Transport typically works: truckload freight documents, workflows, onboarding and common problems, as typical practice to confirm with Marten Transport.
How EDI and API integration with Shaffer Trucking typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Shaffer Trucking.
How EDI and API integration with Stevens Transport typically works: truckload freight documents, workflows, onboarding and common problems, as typical practice to confirm with Stevens Transport.
How EDI and API integration with C.R. England typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with C.R. England.
How EDI and API integration with Hirschbach Motor Lines typically works: truckload freight documents, workflows, onboarding and common problems, as typical practice to confirm with Hirschbach Motor Lines.
How EDI and API integration with KLLM Transport Services typically works: truckload freight documents, workflows, onboarding and common problems, as typical practice to confirm with KLLM Transport Services.
Tell us about your Leonard's Express program, documents and ERP. We will outline the connection, mapping and testing plan.