EDI 753 and 754: Requesting Routing Instructions From Retailers

The cartons were packed on time, the ship window opened on Thursday, and nobody had heard from the retailer's transport desk. So the dock lead booked the vendor's own LTL carrier, marked the bill of lading prepaid and sent the freight out. A month later the remittance arrived short by a compliance deduction, and the vendor had also paid a freight bill the retailer would have paid had the order been routed.

That failure starts with a missing or rejected EDI 753, the request for routing instructions, or an unread 754 reply. When both messages are mapped from warehouse data, monitored against the retailer's response window and tied to the bill of lading, skipped routings drop to near zero and every deduction has a document trail that either prevents it or wins the dispute.

• What this guide covers: the X12 structure of the 753 and 754, the dates and quantities that matter, how a routed load turns into collect or third-party freight terms, and what happens when the request is skipped.
• What it adds: a sample 753 and 754 pair, a cost table in dollars and rupees for a US subsidiary of an Indian manufacturer, the Indian e-way bill contrast, and a go-live checklist.

Who controls the truck when a retailer routes its own inbound freight

When a retailer controls inbound transport, the vendor's job ends at a ready dock: it tells the buyer what is ready and waits to be told which carrier will collect it. The 753 carries that notice and the 754 carries the answer, so the vendor never chooses or pays the carrier for those orders.

X12 places both transaction sets with its Supply Chain subcommittee, X12M. Its catalogue describes the 753 as a way to request routing instructions and provide general information about merchandise ready to ship, and the 754 as a way to communicate routing instructions to a supplier for a specific shipment, including as a reply to a 753. Neither set appears in release 4010; reference guides list both from release 4030 onward.

• Vendor-controlled, prepaid: the vendor chooses and pays the carrier and recovers the cost in its price or a freight line on the invoice.
• Buyer-routed, collect or third party: the retailer's chosen carrier collects, and the freight bill goes to the retailer or its freight payer.
• Buyer-routed by portal: some retailers take the same data through a web form instead of EDI; the fields and the deadline are the same even if no 753 is sent.

Buyers route their own freight because consolidating many vendors onto their carriers and lanes lowers total transport cost and lets their DCs schedule arrivals. For the vendor, that changes three things at once: the order no longer needs a carrier quote, the freight bill goes to someone else, and a missed step costs money twice.

What the 753 must say: ship-from, ship-to and order-level OID lines

A usable 753 identifies one ship-from location, then lists each ship-to with its ready dates and, for every purchase order, the cartons, weight and cube actually packed. Send it from packed warehouse data, not from the order book, or the retailer will plan a truck for freight that does not exist yet.

In release 4030 the header holds ST, BGN and an optional PER contact, followed by a single N1 loop for the ship-from party. The detail starts with LX and then repeats an N1 loop for each ship-to, with up to five L11 references, up to two G62 dates and an optional USI unitised-shipment segment. Inside that loop, OID lines give the per-order quantities, with an optional CMC commodity classification.

The OID segment is where most rejections start. OID01 carries the seller's order reference and OID02 the purchase order number, and the standard requires at least one of them. Packaging form and quantity travel as a pair in OID04 and OID05, weight unit and weight in OID06 and OID07, and volume qualifier and volume in OID08 and OID09; sending one element of a pair without the other fails syntax.

An EDI 753 routing request built in the warehouse management system should send OID02 purchase order numbers with OID04-OID05 carton counts and OID06-OID07 scale weights for every packed order, because X12 release 4030 pairs those elements and a translator rule should hold any 753 whose weight differs from the pack record by more than 2%.

BGN01 tells the retailer what the message is doing. Code 00 is an original request, 04 a change, 05 a replacement and 01 a cancellation, and BGN06 can point back to the reference of the earlier transaction being changed. Some routing guides ask vendors to cancel and resend rather than send a change, so read yours before choosing which code the map sends.

Reading a 754: carrier SCAC, pickup window and load reference

The 754 is the instruction the vendor must follow exactly: which carrier, which pickup date and which reference the driver and bill of lading will carry. Load it into the TMS automatically and treat any shipment without a matching 754 as not yet routed, whatever the dock schedule says.

In release 4030 the 754 header carries up to five N1 loops, one of which must identify the ship-from location. Each LX detail loop then holds up to five L11 references, a BLR segment with the carrier's Standard Carrier Alpha Code in BLR01, the OID lines being routed, up to two G62 dates and an optional MSI for multi-stop loads. A nested QTY loop with AT9 trailer data and a single ship-to N1 loop close the detail.

• BLR01 carrier code: the SCAC the shipping clerk must book; BLR02 and BLR03 are the effective date and time of the instruction, not the pickup time.
• G62 pickup date: qualifier 69 is Scheduled Pick-Up Date and 10 is Requested Ship Date/Pick-up Date; partners pick one, so the map must read both.
• L11 load reference: qualifiers such as LO Load Planning Number, PUA Pick Up Appointment Number or BM Bill of Lading Number tie the order to the retailer's load; the guide says which one the BOL must show.
• OID lines: the 754 may route only some orders from the 753, or split them across two loads, so match on purchase order number, not on the request number alone.

ST*753*0001~
BGN*00*RR240117*20261103*1015~
PER*IC*SHIPPING DESK*TE*6145550100~
N1*SF*VENDOR COLUMBUS DC*92*0457~
N4*COLUMBUS*OH*43217*US~
LX*1~
N1*ST*RETAILER DC 6094*92*6094~
G62*37*20261105~
G62*38*20261109~
OID*SO88213*4581207733**CTN*312*L*6240*E*1450~
OID*SO88214*4581207740**CTN*96*L*1920*E*440~
SE*12*0001~

ST*754*0001~
BGN*00*RI556201*20261104*0830~
N1*SF*VENDOR COLUMBUS DC*92*0457~
LX*1~
L11*LD778120*LO~
BLR*XMPL*20261104~
OID*SO88213*4581207733**CTN*312*L*6240~
OID*SO88214*4581207740**CTN*96*L*1920~
G62*69*20261106~
N1*ST*RETAILER DC 6094*92*6094~
SE*11*0001~

Notes: CTN = carton, L = pounds, E = cubic feet; G62 37/38 = ship not
before / not later than; G62 69 = scheduled pick-up date; XMPL is a
placeholder SCAC. Envelope segments (ISA/GS) omitted.

Routing request timing: ready date, response window and pickup

Three clocks run on every routed order: the vendor's deadline to send the 753, the retailer's window to answer with a 754, and the pickup date inside the PO ship window. The routing guide sets all three in business days, and the vendor should monitor each as a separate timer rather than waiting for the dock to notice.

The guide's lead time usually counts back from the ship-not-before date, so a late pack shortens the retailer's planning time and pushes pickups outside the window. In our example the guide asks for the request five business days before the earliest ship date. Treat that figure as illustrative and load the real value per retailer and per ship-to programme.

• Send timer: starts when the last carton of an order is packed and scale-weighed; alert if the 753 has not left the translator within two hours.
• Acknowledgment timer: alert if no functional acknowledgment arrives, as our guide to the 997 explains; a rejected 753 is the same as an unsent one.
• Response timer: alert the transport planner if no 754 arrives within the retailer's stated window, early enough to call the routing desk before the ship window opens.
• Pickup timer: once routed, track the scheduled pickup date against the G62 38 ship-not-later-than date and escalate a missed pickup the same day.

Collect versus prepaid: how routed freight lands on the bill of lading

A routed load should leave the dock with freight terms that send the bill away from the vendor: collect if the consignee pays, third party if the retailer's freight payer does. The TMS should set those terms from the 754 automatically, because one prepaid tick box turns the retailer's freight into the vendor's cost.

The standard VICS bill of lading carries the choice in its freight charge terms block, and treats freight as prepaid unless marked otherwise. Third-party terms also need the bill-to block completed, or the carrier invoices the shipper by default. Our breakdown of the VICS bill of lading fields covers those boxes; the point here is that the 754 should drive them.

A buyer-routed shipment confirmed by an EDI 754 should print collect or third-party freight terms with the retailer's bill-to party on the VICS bill of lading, because the form treats freight as prepaid unless marked, and one prepaid 6,240 lb LTL shipment costs the vendor about $1,104.

Freight terms and transit risk are separate contract questions. The purchase order's delivery term decides when risk passes; the routing guide decides who books the truck. A vendor can ship collect on a retailer's carrier and still carry the loss until delivery if the PO says so, so check both before assuming a damaged load is the retailer's problem.

Skipped routing requests: freight leak and deduction in two currencies

Each skipped routing costs the vendor its own freight bill, the retailer's compliance charge and the time spent disputing it. For a US subsidiary that reports to an Indian parent, the same loss appears again in rupees in the consolidated accounts, which is often where the pattern is first noticed.

The table uses illustrative figures for one 312-carton, 6,240 lb order shipped from Columbus, Ohio, and a translation rate of ₹88.00 per US dollar chosen for the example. Compliance charges vary by retailer and are set in each routing or vendor guide; the $250 here is a placeholder, not any retailer's published amount.

The incident below shows how one of those nine orders slipped. Every step looked reasonable to the person taking it; the failure was a map error that no one was alerted to.

1. Tue 3 Nov, 10:15, pack complete: the WMS closes the wave for PO 4581207733 with 312 cartons and 6,240 lb, and fires the event that should build the 753.
2. Tue 3 Nov, 10:16, map failure: the order came in under a new order type, OID02 maps blank, and the translator parks request RR240131 in an error queue with no alert.
3. Thu 5 Nov, 15:30, window opens: no 754 has arrived; the dock lead books the vendor's LTL account on bill BOL-0457-110501, freight terms prepaid, PRO 4410-7702 rated at $1,104.
4. Fri 6 Nov, 08:05, retailer receipt: the DC matches the advance ship notice's carrier to its routing record, finds no load reference and logs a routing violation.
5. Fri 4 Dec, remittance: cash application posts a $250 deduction; the dispute fails because the vendor holds no 754 and no 997 showing the request was ever received.

India has no routing transaction set, so the decision sits elsewhere

The 753 and 754 are a US retail practice; Indian domestic retail has no equivalent X12 exchange, and we found no Indian standard that plays the same role. The underlying decision, whether the buyer or the supplier arranges the truck, still exists and lands in the purchase order terms, the consignment note and the e-way bill.

For a road movement above ₹50,000 in consignment value, CGST Rule 138(1) requires the registered person causing the movement to furnish Part A of FORM GST EWB-01 before it starts. Under Rule 138(3), when goods are handed to a road transporter and the consignor has not generated the bill itself, the consignor enters the transporter's details and the transporter generates the e-way bill from Part A.

India's buyer-arranged road freight has no EDI 753 or 754 exchange; the routing decision shows instead in the transporter ID entered under CGST Rule 138(3) on FORM GST EWB-01 for consignments above ₹50,000, so the supplier's ERP must hold the buyer-nominated transporter before goods leave the dock.

• Buyer-nominated transporter: the supplier still owns Part A and must obtain the transporter's ID before dispatch, which is the Indian counterpart of waiting for a 754.
• Who pays the transporter: the freight payer decides who receives a goods transport agency service and therefore who handles any reverse charge; our guide to GST on GTA services works through the rules.
• Indian exporters to US retailers: if a US subsidiary or 3PL ships domestically to the retailer, the 753 and 754 apply in full there, and the losses translate into the parent's rupee accounts as shown above.

Translator rules versus analyst judgement on routing messages

Building, validating and matching routing messages are fixed rules for the translator and TMS; deciding what to do when the retailer has not answered, or when its guide changes, needs a person. AI tools can read guide updates and draft mappings, but no shipment should go out prepaid on a routed account without a named approver.

Go-live checklist for a new retailer's routing programme

Treat a new routed customer as an integration project with testing, not as a dock procedure. The vendor is ready when every routed order produces an accepted 753, an answered 754 and a bill of lading with the right freight terms, three times in a row in test.

The routing guide compliance blueprint for B2B wholesale covers the wider set of retailer rules, including ASN and label checks. The checklist below covers only the routing request and its consequences.

More guides on EDI, transport and logistics finance sit in the Logistics & Supply Chain hub. If you are evaluating EDI, WMS or TMS software that should run the routing timers and set freight terms without manual steps, you can share your retailer list and order volumes through our request for proposal form.