EDI 754 Routing Instructions: The Complete Guide (2026)

After you tell a retailer what's ready to ship, the answer comes back as an EDI 754 Routing Instructions — and from the moment it lands, you're on the retailer's clock. The 754 is the routing verdict for freight you declared on a 753 request: which carrier is coming, when, under what references. Everything about handling it well reduces to speed and fidelity.

Reading the instructions

The core contents are operational. Carrier assignment — the SCAC and service the retailer's transportation network selected for your freight. Pickup detail — the window or appointment against your declared ready date. References — the load, shipment, or routing identifiers the retailer's systems generated, which now become the connective tissue of the shipment. And scope — which POs and quantities this routing covers, since the retailer may split or consolidate what you declared: two POs merged onto one truck, or one declaration split across pickup days.

That last behavior surprises new vendors. The 754 is not an echo of your request; it's the retailer's plan, and your warehouse executes to their plan — staging freight by assigned load, not by however your ERP grouped the orders.

References make or break compliance

The identifiers on a 754 are tracked end to end by the retailer, and they must reappear everywhere downstream: on carton and pallet labels, in shipping paperwork, and inside the 856 ASN. Amazon is explicit about the pattern — its reference number from routing must be quoted on the ASN. Mass retailers run equivalent rules with their own load and appointment identifiers. Receiving systems reconcile arriving freight against planned loads by these references; freight that arrives untraceable to its routing gets handled as an exception, and exceptions on a compliance program have invoices attached.

The failure mode is rarely malice, it's plumbing: routing data lives in a transportation inbox, labels generate from the WMS, the ASN generates from the ERP, and nobody wired the references across. The fix is structural — the 754 must land in the same integrated flow that produces labels and ship notices, so its identifiers propagate without anyone re-typing them.

A second habit worth building is verification on arrival: check the 754's scope against your open declarations, because a routing answer covering POs you didn't request — or missing ones you did — signals a crossed wire that's far easier to resolve before pickup day than at the dock. Silent scope mismatches are how freight gets orphaned.

The clock between instruction and pickup

Routing answers tend to arrive close to the action: an assigned pickup can be scheduled tight against the ready date you declared. Warehouses therefore need the 754's contents within minutes of arrival — as staging instructions, label data, and appointment expectations — not at the next batch cycle. When the assigned window genuinely can't be met, the recoverable path is proactive: notify the retailer's transportation group through the prescribed channel before the carrier is dispatched. The unrecoverable path is a truck arriving for freight that isn't ready, which is a scored failure nearly everywhere.

EDISQ lands inbound 754s against their originating requests, pushes carrier and reference data into your fulfillment flow automatically, and builds the eventual ASN with the routing references already in place — closing the loop the 753 opened.

What the exchange costs

Both directions of routing traffic bill as ordinary documents on EDISQ's pricing: after the monthly 25 free, each starts at $0.50 and steps down to $0.10 with volume, billed marginally per tier — with connectivity over AS2, SFTP, or VAN included and no mapping or setup fees. For the document pair that decides whether your freight moves on plan, the cost rounds to nothing; the compliance stakes don't.

FAQ