The EDI 753/754, Decoded: Routing Is a Question You Ask Before the Shipment Exists

The EDI 753 · Request for Routing Instructions and the EDI 754 · Routing Instructions are how a supplier asks its buyer, before anything ships, "how do you want this freight moved?" — and how the buyer answers. The 753 asks; the 754 decides. Neither moves freight and neither books a carrier. Together they remove the guesswork that turns into routing-guide violations and chargebacks later.

Most suppliers meet this pair the hard way. A purchase order arrives, the warehouse ships it the usual way — their regular carrier, their regular service level — and weeks later a deduction lands because the buyer's routing guide required a specific carrier, a collect freight term, or a routing request first. The 753/754 exchange exists so that argument happens in data, before the shipment, when it costs nothing to get right.

What are the EDI 753 and 754?

The 753 · Request for Routing Instructions is sent by the supplier (or its logistics function) to the buyer when a shipment is being prepared and the routing is not already fixed by the order or a standing agreement. It identifies the shipment — weight, cube, piece count, origin, destination, ship date window, and the purchase orders it covers — and asks for instructions.

The 754 · Routing Instructions is the buyer's answer. It names the carrier, the service level, the freight terms (prepaid, collect, third-party bill), and any shipment-specific conditions. When the 754 arrives, routing stops being an interpretation of a PDF guide and becomes a specific instruction for a specific shipment.

Three ideas define the pair:

• The question is shipment-specific. A routing guide is generic. A 753 describes this freight — this weight, this destination, this date — so the 754 can answer for this freight.
• The answer is authoritative. A 754 overrides habit and, where the partners agree, the standing guide for that shipment. "We always use carrier X" is not a defense when the 754 said carrier Y.
• Both sides keep the record. The pair is the evidence trail when a routing chargeback is disputed months later: what was asked, what was answered, and what was actually tendered.

How do the 753 and 754 fit with the 850, 204, and 856?

These messages get confused because they all touch the same shipment at different moments:

• The 850 · Purchase Order says what was bought. It may carry routing terms, but often only by reference to a guide.
• The 753 · Request for Routing Instructions asks how this shipment should move, once the freight is known.
• The 754 · Routing Instructions is the buyer's decision for that shipment.
• The 204 · Motor Carrier Load Tender offers the freight to the carrier the 754 named.
• The 856 · Advance Ship Notice reports what actually shipped — and receiving compares it, carrier included, against what was instructed.

Seen that way, the 754 is the reference the 856 gets graded against. A perfect ASN sent on the wrong carrier is still a routing failure.

When is a 753 actually required?

Not every shipment needs one. Standing routing for parcel, a fixed carrier agreement, or routing fully specified on the order can make a 753 unnecessary. The request earns its place when:

The freight is LTL or truckload and the buyer controls routing. Collect and third-party-billed freight almost always runs on the buyer's carrier choice, not the supplier's.

The shipment is unusual. Oversize, overweight, multi-stop, or a destination the guide does not clearly cover — the cases where interpreting a guide is most likely to go wrong are exactly the cases worth asking about explicitly.

The guide says "request routing." Many retail routing guides require a routing request above a weight or pallet threshold. Skipping it is itself the violation, regardless of which carrier you chose.

What breaks in the 753/754 exchange?

The request goes out too late. A 753 sent after the freight is already tendered is theater. Buyers publish lead times for routing responses for a reason — the answer has to arrive while changing carriers is still free.

The 754 is received but not applied. The answer lands in an inbox or an EDI queue nobody watches, and the dock ships on habit anyway. An unapplied 754 is worse than none: the buyer can prove you were told.

The shipment changes after the answer. Weight, pieces, or destination change after the 754 was issued, and nobody re-asks. The instruction covered different freight than what shipped.

The tender contradicts the instruction. The 204 goes to a different carrier or service level than the 754 named — usually a manual override at the dock that never made it back into the system of record.

How should you run routing requests cleanly?

1. Trigger the 753 from freight facts, not from the calendar. When weight, cube, and destination are known, ask — not before the facts exist, and not after tendering.
2. Hold the tender until the 754 lands, or the lead time expires. Define in advance what silence means for your partnership: wait, escalate, or ship per the guide — and write down which one you did.
3. Apply the 754 into the shipment record. Carrier, service, and freight terms should populate the tender and the ASN automatically, not be re-keyed from a message someone read.
4. Re-ask when the freight changes materially. A changed shipment is a new question.
5. Keep the pair with the shipment file. In a chargeback dispute, the 753/754 pair plus the 856 is the whole case.

Frequently asked questions

Does a 754 book the carrier?
No. It instructs which carrier and terms to use. The booking/tender step is the 204 · Motor Carrier Load Tender to that carrier.

Who sends the 753 — the supplier or the 3PL?
Whoever prepares the shipment and needs the instruction. In practice it is the shipping party: the supplier's logistics team or its 3PL acting on the supplier's behalf.

What if the buyer never answers the 753?
Follow the routing guide's fallback rule for your partnership and document that you asked and waited the published lead time. Silence is a process gap to surface with the buyer, not a permission slip to route arbitrarily.

Is the 753/754 pair only for retail?
Retail is the most common home — routing guides and chargebacks live there — but any buyer-controlled-freight relationship can use it, including distributors and manufacturers with collect-freight programs.

---

Routing looks like paperwork until you price the alternative: one wrong-carrier truckload can cost more than a year of asking first. The 753/754 pair is the cheapest conversation in the whole order-to-cash chain, because it happens before the mistake does.

I build SignalEDI to help SMB teams handle exactly this layer — routing instructions applied to the shipment record instead of living in an inbox, and tenders and ASNs checked against what the buyer actually instructed.

— Chris, founder of SignalEDI