Carriers integration

Reddaway EDI: legacy documents and migration

Reddaway ceased operations in 2023. How its EDI documents were typically exchanged, and how to reconcile, archive and move that volume to current carriers.

Company status: Reddaway was an LTL carrier owned by Yellow Corporation. Yellow ceased operations on July 30, 2023 and filed for Chapter 11 bankruptcy. This guide is for teams that still hold Reddaway documents, claims or invoices, or that are moving lanes to other LTL carriers. Checked 2026-11-12 · source.

At a glance

Reddaway integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Reddaway program or a customer relationship.

Illustration of a freight truck on a highway, representing the carriers industry that Reddaway operates in.
Industry. Carriers: where Reddaway operates.
Workflow diagram: your TMS, ERP and finance systems exchange documents with Reddaway through ECOM. You send 204; you receive 990, 214, 210; 997 acknowledgments go both ways. Your systems TMS · ERP · finance ECOM integration map · validate · connect · monitor Reddaway 204 204 990 214 210 990 214 210 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Tenders and invoices re-keyed Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Reddaway

Tell us which Reddaway documents and open items you still hold, which ERP you run and where the volume is moving. A specialist will outline how to reconcile, archive and migrate. This page is a guide based on typical practice; it does not mean ECOM works with Reddaway.

  • Review of the Reddaway documents and open items you still hold
  • EDI and API integration with your TMS, ERP and finance systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Reddaway

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Reddaway integration fits your systems

Your systemsTMS, ERP and accounting
ECOMMapping, validation, connectivity and monitoringHistorical connection (not for new setups) · Replacement partners · Archive and retrieval
ReddawayLegacy program
  1. InventoryList the Reddaway documents, partners and open items you still hold.
  2. MapMap the same internal data to the partners that replace it.
  3. ConnectStand up the replacement connections.
  4. TestRun parallel tests before cutover.
  5. RetireRetire the old connection with monitoring in place.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Reddaway integration

Who this is for: Teams that still hold Reddaway documents, claims or invoices, or are moving volume to other carriers, and the finance, logistics and EDI staff who support them.

Scope: This guide describes typical practice for this kind of trading relationship and helps read and reconcile Reddaway documents held from before it ceased operating.

Reddaway ceased operations in 2023. Reddaway was an LTL carrier owned by Yellow Corporation. Yellow ceased operations on July 30, 2023 and filed for Chapter 11 bankruptcy. This guide is for teams that still hold Reddaway documents, claims or invoices, or that are moving lanes to other LTL carriers.

This guide describes how Reddaway documents were typically exchanged, so you can reconcile, archive and migrate them. It does not include Reddaway's specification and no Reddaway document was read for it.

Start with what you still hold: open invoices, credits and claims, maps and partner profiles that are still scheduled, and the historical documents that finance or audit may ask for. Then plan the replacement carriers, because no new volume can go to Reddaway.

ECOM can map and archive the historical documents, match open items in your TMS, ERP and finance systems, and connect the carriers that replace Reddaway, as software, as a managed service or both.

Business scenarios

Where Reddaway integration gets complicated

Typical requirements—confirm with your trading partner.

Open freight bills and claims

Freight bills, claims and refunds tied to Reddaway can still be open. Matching each one to its tender and delivery record decides what is owed or recoverable.

How ECOM helps: ECOM maps the historical 210 and 214 records to your ERP or archive and matches open items to the original orders, tenders or shipments, so open balances and claims can be reviewed.

What you gain: A clear record of what is open and what is settled.

Moving lanes to other carriers

Lanes and volume that went to Reddaway need new carriers, with tenders, status and invoices flowing the same way into your TMS and ERP.

How ECOM helps: ECOM connects the replacement partners, maps the same internal data to their formats and runs the test cycles with you, so volume can move in stages.

What you gain: Volume moves to current partners without a gap in documents.

Historical shipment records

Past Reddaway tenders, status messages and invoices may be needed for audit, claims or lane analysis.

How ECOM helps: ECOM can map and archive the historical documents with their transfer history, so they stay searchable for audit, claims and tax review.

What you gain: Records are available when a claim, audit or dispute needs them.

Retiring the old connection

Maps, schedules and partner profiles for Reddaway should be removed so nothing is sent to a connection that no longer exists.

How ECOM helps: ECOM reviews which maps, schedules and partner profiles still point to the former partner and retires them with you.

What you gain: No document is sent to a connection that no longer exists, and the partner list stays clean.

Workflows

Typical Reddaway business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not Reddaway's published process.

Reconcile open items

  1. 1Gather the 210, 214, 204 history
  2. 2Match each to its source document
  3. 3Settle or dispute open items
  4. 4Archive history and transfer log

Move volume to current carriers

  1. 1Choose the replacement partners
  2. 2Map your data to their formats
  3. 3Test and run in parallel
  4. 4Retire the old maps and profile

Documents and APIs

Reddaway documents by program

General guidance. We could not verify Reddaway's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Reddaway's confirmed requirements. Confirm the list, versions and programs with Reddaway.

DocumentNameDirectionProgramStatusPurpose
204 Motor Carrier Load Tender To Reddaway Not stated General guidance Typically offers a load to a carrier with pickup, delivery and shipment details.
990 Response to a Load Tender From Reddaway Not stated General guidance Typically accepts or declines an offered load.
214 Transportation Carrier Shipment Status Message From Reddaway Not stated General guidance Typically reports pickup, location updates and delivery.
210 Motor Carrier Freight Details and Invoice From Reddaway Not stated General guidance Typically bills for freight, with charge detail, in the shipper's payables format.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • Historical connection (not for new setups)

    Reddaway documents were typically exchanged over AS2, SFTP or a value-added network. Do not build a new connection to Reddaway; use this only to read historical files.

    General guidance

  • Replacement partners

    Plan the connections to the carriers that take over the volume: each new partner sets its own method, identifiers and test cycles.

    General guidance

  • Archive and retrieval

    Keep the historical documents and their transfer history where finance and audit can retrieve them, in your ERP or an archive.

    General guidance

Challenges

Common integration challenges

  • Open balances and claims

    Invoices, credits, claims and refunds tied to Reddaway may still be open, and the people who handled them may have moved on.

  • Schedules that still point to it

    Maps, schedules and partner profiles for Reddaway may still exist in your systems and keep producing documents nobody will receive.

  • Records for audit and claims

    Past Reddaway documents may be needed for audit, tax or claims, so they need to stay searchable with their transfer history.

  • No current specification

    Reddaway no longer supports new connections, so no new connection can be set up. Plan the replacement partners instead.

Automation options for Reddaway shippers

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. Reddaway sets its own requirements; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

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.

Discuss Your Trading Partner Requirements

Legacy EDI flow

How Reddaway documents were exchanged

This is the sequence these documents typically followed. Use it to read and reconcile historical files, not to set up a new connection to Reddaway.

  1. 204 Motor Carrier Load Tender

    From you to Reddaway

    Typically offers a load to a carrier with pickup, delivery and shipment details.

  2. 990 Response to a Load Tender

    From Reddaway to you

    Typically accepts or declines an offered load.

  3. 214 Transportation Carrier Shipment Status Message

    From Reddaway to you

    Typically reports pickup, location updates and delivery.

  4. 210 Motor Carrier Freight Details and Invoice

    From Reddaway to you

    Typically bills for freight, with charge detail, in the shipper's payables format.

  5. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

Need help with the legacy documents?

Tell ECOM what you still hold and where the volume is moving. A specialist will outline how to reconcile, archive and migrate. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your Reddaway migration

Each request goes to an ECOM EDI specialist with Reddaway's name attached, so the reply starts from your program.

  • Review what you still hold

    Tell us which Reddaway documents, open items and schedules remain; we explain how to reconcile and archive them.

    Request a legacy review
  • Connect Reddaway to your ERP

    Tenders, status and freight invoices in and out of the TMS, ERP and finance systems you already run.

    Discuss ERP integration
  • Migrate to current partners

    Map the same internal data to the partners that replace Reddaway, test them and retire the old connection.

    Plan the migration

Reddaway integration FAQs

Can I still connect to Reddaway by EDI?

No. Reddaway ceased operations in 2023, so no new connection can be set up. Use this guide to reconcile and archive what you hold, and to connect the carriers that replace it.

What should I do with open Reddaway invoices, claims and deductions?

Match each open item to its original order, tender or shipment, then settle or dispute it with finance. ECOM can map the historical documents to your TMS, ERP and finance systems so open items can be reviewed.

Which EDI documents were typical for an LTL carrier?

Typical documents were 204, 990, 214, 210, 997. That is general practice, not Reddaway's published list.

How can ECOM help me move from Reddaway?

ECOM maps your internal data to the replacement carriers' formats, runs the test cycles with you and retires the old maps and partner profile, as software, as a managed service or both.

Does this guide mean Reddaway endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Reddaway.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Reddaway sets its own requirements and can change them at any time; your Reddaway implementation guide, supplier portal or account contact is the authoritative source for your program.

Request help with your Reddaway migration

Tell us which Reddaway documents and open items you still hold, which ERP you run and where the volume is moving. We will outline how to reconcile, archive and migrate.