On a collect program, the freight on your dock isn't yours to route. The retailer pays for transportation, so the retailer decides which carrier picks it up and when — and before they can decide, they need to know what you have ready to move. The EDI 753 Request for Routing Instructions is the document that asks. It's the opening move of retail transportation routing, and on the programs that require it, skipping or fumbling it stalls everything behind it.
What the retailer needs to know
A routing request describes the shipment-to-be in logistics terms. Against the PO (or POs) being fulfilled, it reports: the ready date — when freight is available for pickup; the origin — which of your facilities or your 3PL's docks; and the physical profile — carton count, pallet count, weight, and cube. Item-level detail may ride along depending on the spec, but the essence is the transportation view: enough for a routing system to consolidate your freight with others', assign a carrier, and schedule the pickup window.
Accuracy here has teeth. The retailer's transportation planning treats your declared weights and counts as fact; freight that shows up meaningfully different from its routing request — more pallets, a later ready date — disrupts a planned load, and retail compliance programs treat that as a vendor failure, not a rounding error.
The 753/754 exchange, start to finish
The request is half of a conversation. The flow runs:
- An 850 purchase order arrives and you plan fulfillment.
- Inside the retailer's stated window, you transmit the 753 declaring what's ready.
- The retailer's routing system answers with a 754 Routing Instructions: the assigned carrier, pickup detail, and load references.
- You ship per those instructions, carrying the assigned references onto carton labels and the 856 ASN.
The deadlines around step 2 are program-specific and unforgiving — routing windows are typically tied to the PO's ship window, and a missed request can mean a missed window, expedited freight at your expense, or an on-time-delivery failure charged to you. This is a calendar problem, and calendars are what automation is for: the routing request should generate from fulfillment data the moment an order is planned, not from someone remembering.
Getting the details right
Three practical rules keep 753s clean. Declare reality, not the PO — request routing for what you'll actually ship, reflecting any shorts, so the carrier arrives for the right freight. Consolidate correctly — most programs want one request covering all POs ready at the same origin on the same date, letting the retailer build efficient loads. And mind the references — the routing conversation generates identifiers the retailer's systems track end to end; dropping them between the 754, the labels, and the ASN is a classic mass-retail compliance failure.
Multi-origin suppliers add one more coordination layer: freight declared from a 3PL's dock needs the 3PL's ready dates and physical counts, which means the routing request depends on warehouse data you don't directly control. The cleanest implementations source the 753 from the same fulfillment records the warehouse confirms, so the declaration and the dock agree by construction.
EDISQ generates routing requests from your open-order and fulfillment data, validates the physical profile against your pick data, and holds the 753/754 thread together so downstream documents inherit the right references automatically — part of the broader retail flow in our retail solution.
Cost footnote
Routing documents ride EDISQ's standard meter: the first 25 documents each month are free, and past them pricing runs from $0.50 down to $0.10 per document as volume tiers fill, marginally billed. There's no transportation add-on module — the 753 is just another document, which, at those prices, is exactly what it should be.
FAQ
Why do retailers require a 753?
Because they control inbound transportation. On collect programs the retailer pays the freight and picks the carrier, so before you ship they need to know what is ready — weight, cartons, pallets, ready date — to plan routing.
What answers a 753?
The 754 Routing Instructions: carrier assignment, pickup information, and load references that must be carried onto labels and the ASN.
Does every shipment need a routing request?
Only on programs where the retailer routes freight — typically collect shipments to DCs. Prepaid programs, where you arrange carriage, skip the 753/754 exchange entirely.
What does a 753 cost to send?
It draws on the same EDISQ pool as every document: 25 free monthly, then from $0.50 apiece, decreasing with volume. No extra transportation-module fees.