Skip to content
EDI 753 — EDI TransactionPublished Nov 3, 2026

EDI 753 Request for Routing Instructions Guide

EDI 753 explained: how suppliers request routing on collect freight, the BGN, N1, G62, USI and OID segments, a live two-DC example, and the 754 reply.

The EDI 753 is how a supplier says "my freight is ready, tell me how to ship it." When a retailer pays for inbound freight and chooses the carrier, you cannot book a truck yourself. You send a 753 with what is ready, where it is going and when it can be picked up. The retailer plans the load and replies with a 754 Routing Instructions. The quality of the 754 you get back depends almost entirely on the numbers you put in the 753.

This guide covers what the 753 carries, when to send it, every segment you will map, a live example with two distribution centers, and the errors that lead to the wrong truck or no truck at all.

What Is an EDI 753?

An EDI 753 is the Request for Routing Instructions transaction set defined by ASC X12, used by a supplier to request routing for merchandise that is ready to ship and to give the buyer the details it needs to plan the move. X12 describes it as a way to request routing instructions and provide general information about merchandise ready to be shipped. It travels in functional group RF (the GS01 value). The reply, the 754, travels in group RG.

Authoritative references for 753 work:

  • The X12 transaction set catalog defines the 753 structure, segment order and loops
  • The National Motor Freight Traffic Association (NMFTA) issues the carrier SCACs used in the 754 reply and maintains the NMFC freight classes a 753 can carry in its CMC segment
  • Each retailer publishes a routing guide and a 753/754 implementation guide that set lead times, required references and the ship-to IDs to use

Who sends it? The supplier, or the 3PL or warehouse shipping on the supplier's behalf.

Who receives it? The retailer's inbound transportation team, or the logistics provider that plans its freight.

When is it sent? Once purchase orders are picked and packed, or close enough that cartons, weight and cube are known, and early enough to meet the retailer's lead time. One published retailer guide, for example, requires at least 48 hours between sending the 753 and the earliest pickup date. Your retailer's guide sets its own rule.

Why does it matter? On collect freight the retailer decides the carrier, the mode and the pickup appointment. Without a 753, or with a late one, nothing gets scheduled. With wrong weights or cube, the retailer books the wrong equipment.

When You Need a 753: Collect vs Prepaid Freight

Prepaid (vendor-routed)Collect (buyer-routed)
Who chooses the carrierSupplierRetailer
Who pays freightSupplierRetailer
Do you send a 753?NoYes, where the retailer routes by EDI
What you get backNothing; you book your own carrierA 754 with carrier, load and appointment
What you send after shipping856 ASN856 ASN, with the carrier and references from the 754

The freight terms on the 850 purchase order and the retailer's routing guide tell you which POs are collect. Retailers that publish 753/754 guides include Kohl's, Amazon (for vendor shipments), JCPenney, and military exchanges such as AAFES and the Navy Exchange (NEXCOM). Walmart and Target also route much of their inbound freight under collect programs; depending on the program, the routing request goes through EDI or the retailer's supplier portal. Check the current routing guide for each retailer, because requirements change and can differ by vendor.

The Routing Request Cycle, Step by Step

  1. Orders released. The retailer sends 850s. Collect POs are flagged by their freight terms.
  2. Pick and pack. Your warehouse picks the orders, packs cartons and builds pallets. Now you know real cartons, weight and cube.
  3. Send the 753. One request covers a ship-from location and one or more destinations, each with a pickup window and the POs going there.
  4. Receive a 997. The retailer's system confirms the 753 arrived and was structurally valid. See the 997 Functional Acknowledgment guide.
  5. Retailer plans the load. It groups your POs, perhaps with other suppliers' freight, into loads and books a carrier, often with a 204 load tender.
  6. Receive the 754. It names the carrier (by SCAC), the load number, the pickup appointment, and which POs ship together.
  7. Ship. Print the bill of lading with the 754's references, load the trailer, and send the 856.
  8. Changes. If quantities change before pickup, send a replacement or change 753; if the order is no longer ready, cancel it. The retailer may send a revised 754.

Interactive Example: 753 for Two Distribution Centers

A home goods supplier in Grand Rapids has three purchase orders ready: two for DC 6021 in Columbus and one for DC 6043 in Savannah. The 753 opens with the ship-from in the heading N1 loop and a contact in PER. A single LX starts the detail. Each destination gets its own N1 loop with its own routing request number (L11 qualifier RRC), an earliest and latest pickup time (G62 with EP and LP), a pallet count with a stackability flag (USI), and one OID per purchase order with cartons, weight in pounds and cube in cubic feet. All names, IDs and numbers are fictional.

Use the Plain English tab for a readable summary, including totals per destination, or click any segment to see each element.

Live exampleBig-Box RetailerEDI 753

Big-Box Retailer 753 Routing Request (Two DCs)

A supplier tells a retailer that three purchase orders are ready for collect pickup to two distribution centers: pickup window in G62 (EP/LP), pallet count and stackability in USI, cartons, weight and cube per PO in OID

Document
753 Request for Routing Instructions
From / to
LAKESHOREHG → BIGBOXRETAIL
Segments
29
Ship From
LAKESHORE HOME GOODS
4100 EASTERN AVE SE, GRAND RAPIDS, MI, 49508
Ship To
BIG-BOX RETAILER DC 6043
88 COMMERCE CENTER DR, SAVANNAH, GA, 31408
Interchange date
Nov 4, 2026

Raw EDI (X12)

1
ISA*00* *00* *ZZ*LAKESHOREHG *ZZ*BIGBOXRETAIL *261104*0930*^*00403*000007531*0*P*>~
2
GS*RF*LAKESHOREHG*BIGBOXRETAIL*20261104*0930*7531*X*004030~
3
ST*753*0001~
4
BGN*00*RR-20261104-01*20261104*0930~
5
PER*IC*DANA PRICE*TE*6165550142*EM*SHIPPING@LAKESHORE.EXAMPLE~
6
N1*SF*LAKESHORE HOME GOODS*92*V48213~
7
N3*4100 EASTERN AVE SE~
8
N4*GRAND RAPIDS*MI*49508*US~
9
LX*1~
10
N1*ST*BIG-BOX RETAILER DC 6021*92*6021~
11
N3*1200 DISTRIBUTION PKWY~
12
N4*COLUMBUS*OH*43217*US~
13
L11*RR784501*RRC~
14
G62*EP*20261110*EP*0800~
15
G62*LP*20261112*LP*1600~
16
USI*14*PLT*N~
17
OID*SO-55120*4500781234**CTN*220*L*4180*E*610~
18
OID*SO-55121*4500781240**CTN*96*L*1530*E*240~
19
N1*ST*BIG-BOX RETAILER DC 6043*92*6043~
20
N3*88 COMMERCE CENTER DR~
21
N4*SAVANNAH*GA*31408*US~
22
L11*RR784502*RRC~
23
G62*EP*20261110*EP*0800~
24
G62*LP*20261112*LP*1600~
25
USI*6*PLT*Y~
26
OID*SO-55130*4500781255**CTN*130*L*2210*E*330~
27
SE*25*0001~
28
GE*1*7531~
29
IEA*1*000007531~

Human-Readable

Interchange

Sender ID(ZZ)LAKESHOREHG
Receiver ID(ZZ)BIGBOXRETAIL
Date261104
Time0930
Standards ID^
Version00403
Control Number000007531
Acknowledgment RequestedNo
UsageProduction
Included Groups (IEA01)1

Functional Group

Functional IDRFRF
SenderLAKESHOREHG
ReceiverBIGBOXRETAIL
Date20261104
Time0930
Control Number7531
Agency CodeX
Version004030
Transactions1
Reported Transaction Count (GE01)1

Transaction 753

Request for Routing Instructions
Transaction Type753
Control Number0001
Segments, ST to SE25
Count in SE0125 (matches)

Segment Detail

BGNBeginning Segment
BGN01Transaction Set Purpose Code00
BGN02Reference IdentificationRR-20261104-01
BGN03Date20261104
BGN04Time0930
PERAdministrative Communications Contact
PER01Contact FunctionIC
PER02NameDANA PRICE
PER03Comm QualifierTE
PER04Comm Number6165550142
PER05Comm QualifierEM
PER06Comm NumberSHIPPING@LAKESHORE.EXAMPLE
N1Party Identification
N101Entity CodeSF
N102NameLAKESHORE HOME GOODS
N103ID Qualifier92
N104ID CodeV48213
N3Party Location
N301Address4100 EASTERN AVE SE
N4Geographic Location
N401CityGRAND RAPIDS
N402State/ProvinceMI
N403Postal Code49508
N404CountryUS
LXAssigned Number
LX01Assigned Number1
N1Party Identification
N101Entity CodeST
N102NameBIG-BOX RETAILER DC 6021
N103ID Qualifier92
N104ID Code6021
N3Party Location
N301Address1200 DISTRIBUTION PKWY
N4Geographic Location
N401CityCOLUMBUS
N402State/ProvinceOH
N403Postal Code43217
N404CountryUS
L11Business Instructions and Reference Number
L1101Reference IdentificationRR784501
L1102Reference Identification QualifierRRC
G62Date/Time
G6201Date QualifierEP
G6202Date20261110
G6203Time QualifierEP
G6204Time0800
G62Date/Time
G6201Date QualifierLP
G6202Date20261112
G6203Time QualifierLP
G6204Time1600
USIUnitized Shipment Information
USI01Quantity14
USI02Packaging Form CodePLT
USI03Stackable (Yes/No)N
OIDOrder Identification Detail
OID01Seller's Order NumberSO-55120
OID02Purchase Order Number4500781234
OID04Packaging Form CodeCTN
OID05Quantity220
OID06Weight Unit CodeL
OID07Weight4180
OID08Volume Unit QualifierE
OID09Volume610
OIDOrder Identification Detail
OID01Seller's Order NumberSO-55121
OID02Purchase Order Number4500781240
OID04Packaging Form CodeCTN
OID05Quantity96
OID06Weight Unit CodeL
OID07Weight1530
OID08Volume Unit QualifierE
OID09Volume240
N1Party Identification
N101Entity CodeST
N102NameBIG-BOX RETAILER DC 6043
N103ID Qualifier92
N104ID Code6043
N3Party Location
N301Address88 COMMERCE CENTER DR
N4Geographic Location
N401CitySAVANNAH
N402State/ProvinceGA
N403Postal Code31408
N404CountryUS
L11Business Instructions and Reference Number
L1101Reference IdentificationRR784502
L1102Reference Identification QualifierRRC
G62Date/Time
G6201Date QualifierEP
G6202Date20261110
G6203Time QualifierEP
G6204Time0800
G62Date/Time
G6201Date QualifierLP
G6202Date20261112
G6203Time QualifierLP
G6204Time1600
USIUnitized Shipment Information
USI01Quantity6
USI02Packaging Form CodePLT
USI03Stackable (Yes/No)Y
OIDOrder Identification Detail
OID01Seller's Order NumberSO-55130
OID02Purchase Order Number4500781255
OID04Packaging Form CodeCTN
OID05Quantity130
OID06Weight Unit CodeL
OID07Weight2210
OID08Volume Unit QualifierE
OID09Volume330
1 functional group1 transactionControl #000007531Valid

The retailer's reply to this exact request, with a carrier per DC, is the first example in the EDI 754 guide.

753 Structure at a Glance

The table follows X12 release 004030, the first release that includes the 753. Note the shape: one LX, then a repeating ship-to N1 loop, with the order detail nested inside each ship-to.

PositionSegmentNameUsageNotes
HeadingSTTransaction Set HeaderMandatoryST01 = 753
HeadingBGNBeginning SegmentMandatoryPurpose code, request number, date and time
HeadingPERAdministrative Communications ContactOptionalWho the carrier or retailer should call
Heading loopN1 / N2 / N3 / N4Name and addressMandatory, onceThe ship-from location
DetailLXAssigned NumberMandatory, onceStarts the detail area
Ship-to loopN1 / N2 / N3 / N4Name and addressMandatory, repeatsOne loop per destination
Ship-to loopL11Business Instructions and Reference NumberOptional, up to 5Routing request number, vendor number, notes
Ship-to loopG62Date/TimeOptional, up to 2Earliest and latest pickup
Ship-to loopUSIUnitized Shipment InformationOptionalPallet count and whether pallets stack
Order loopOIDOrder Identification DetailMandatory, repeatsOne per purchase order: packages, weight, cube
Order loopCMCCommodity ClassificationOptionalNMFC commodity code and freight class
SummarySETransaction Set TrailerMandatorySegment count and control number

Some retailers allow only one destination per 753. Others accept several. Retailer guides also tighten "optional": L11, G62 and USI are often required.

Key Segments Explained

BGN: Beginning Segment

BGN*00*RR-20261104-01*20261104*0930~
ElementNameExampleWhat it means
BGN01Transaction Set Purpose Code0000 original, 01 cancellation, 04 change, 05 replace. Some guides also use 06 (confirmation)
BGN02Reference IdentificationRR-20261104-01Your number for this request. Keep it unique
BGN03Date20261104Date of the request
BGN04Time0930Time of the request
BGN06Reference IdentificationThe earlier transaction this one affects, used on changes and cancellations where the guide asks for it

Retailer guides differ on what goes in BGN02 and BGN06. Some ask for your bill of lading number in BGN02; some ask for the load ID from their 754 in BGN06 when you change a request that has already been routed. Follow the guide exactly here, because these fields are how the retailer finds the request to update.

PER: Contact

PER*IC*DANA PRICE*TE*6165550142*EM*SHIPPING@LAKESHORE.EXAMPLE~

PER01 = IC (information contact), then a name and up to three communication numbers, each with a qualifier (TE telephone, EM email, FX fax). Some retailers pass this to the carrier so it can call your dock to set the pickup.

N1 Loop (Heading): Ship-From

N1*SF*LAKESHORE HOME GOODS*92*V48213~
N3*4100 EASTERN AVE SE~
N4*GRAND RAPIDS*MI*49508*US~

N101 = SF (ship from). The ID in N103/N104 is whatever the guide asks for: often a location ID the retailer assigned (92), sometimes a DUNS number (1). The address must be the physical dock the carrier will drive to, not your billing address.

N1 Loop (Detail): Ship-To

N1*ST*BIG-BOX RETAILER DC 6021*92*6021~

N101 = ST (ship to). Use the DC or store ID exactly as it appeared on the purchase order's ship-to. If one PO is split across DCs, each DC gets its own ship-to loop with its share of the cartons.

L11: Business Instructions and Reference Number

L11*RR784501*RRC~
ElementNameExampleWhat it means
L1101Reference IdentificationRR784501The reference value
L1102Reference Identification QualifierRRCRRC routing request control number. Others a guide may ask for: IA vendor number, PUA pick up appointment number, CN carrier PRO number
L1103DescriptionFree text, used by some retailers for equipment or handling notes

The routing request control number is the reference the retailer will echo back on the 754, so make it unique per destination and store it against the POs.

G62: Date/Time (Pickup Window)

G62*EP*20261110*EP*0800~
G62*LP*20261112*LP*1600~
ElementNameExampleWhat it means
G6201Date QualifierEPEP earliest pickup date, LP latest pickup date
G6202Date20261110The date
G6203Time QualifierEPEP earliest pickup time, LP latest pickup time
G6204Time0800The time

The window is a promise. The retailer can schedule the pickup anywhere inside it, so only offer dates and hours your dock can actually meet. A window that is too narrow, or that starts before the retailer's minimum lead time, is a common reason for rejection.

USI: Unitized Shipment Information

USI*14*PLT*N~
ElementNameExampleWhat it means
USI01Quantity14Number of unitized handling units
USI02Packaging Form CodePLTWhat they are, here pallets
USI03Yes/No Condition or Response CodeNY stackable, N not stackable

Pallet count and stackability decide how much trailer space your freight needs. Fourteen non-stackable pallets take fourteen floor positions; the same freight stacked might take seven. Getting this wrong is how a load gets planned for a trailer it does not fit.

OID: Order Identification Detail

OID*SO-55120*4500781234**CTN*220*L*4180*E*610~
ElementNameExampleWhat it means
OID01Reference IdentificationSO-55120Your order number for the PO
OID02Purchase Order Number4500781234The retailer's PO number, exactly as on the 850
OID03Reference IdentificationA consignee reference that further defines the PO, used when the guide asks for it
OID04Packaging Form CodeCTNCTN carton, PLT pallet, PCS pieces
OID05Quantity220Packages in that form
OID06Weight Unit CodeLL pounds
OID07Weight4180Gross weight of the PO's freight
OID08Volume Unit QualifierEE cubic feet
OID09Volume610Cube of the PO's freight

X12 requires the packaging code and quantity together, the weight unit and weight together, and the volume unit and volume together. Send one OID per PO. The retailer adds them up to choose parcel, LTL or truckload, so take the numbers from what was packed, not from the PO's ordered quantities.

CMC: Commodity Classification

CMC01 carries the NMFC commodity code and CMC02 the freight class (for example 70 or 92.5). Many retailers do not ask for it; some require it only for hazardous or temperature-controlled freight. Use the class from your carrier or NMFC classification, not a guess, because class drives LTL pricing.

753 vs 754, 856 and 204

DocumentSent byPurpose
753 Request for Routing InstructionsSupplierFreight is ready: orders, packages, weight, cube and pickup window
754 Routing InstructionsRetailerThe answer: carrier, load number, pickup appointment, which POs ship together
856 Ship Notice/ASNSupplierWhat actually shipped, with carrier and BOL details
204 Motor Carrier Load TenderShipper (here, the retailer)Offers the planned load to a carrier
940 Warehouse Shipping OrderSupplierTells a 3PL warehouse what to ship; the 3PL may then send the 753 for you

The 753 is the only one of these that happens before anything is booked. It is a planning document: the retailer uses it to decide how to move your freight, and the 856 later confirms what actually moved.

Which X12 Version Does the 753 Use?

The 753 and 754 were added in X12 release 004030 and do not exist in 004010. Many suppliers run their 850, 856 and 810 on 004010, so a retailer may use 004010 for orders and 004030 or later for routing. The retailer's 753 guide names the version, and GS08 in each functional group carries it. Check that your translator has the right dictionary before you start mapping.

Common 753 Errors and How to Prevent Them

ErrorWhat happensPrevention
Sent too lateNo pickup in time for the PO's ship windowSend as soon as orders are packed, and track the retailer's minimum lead time
Weights or cube from the PO, not the packWrong equipment booked; load does not fitTake OID weight and cube from packed cartons and pallets
Stackability wrong in USI03Trailer space underestimatedRecord stackability per pallet type in the warehouse system
Ship-to ID does not match the PORequest rejected or routed to the wrong DCCopy the ship-to ID from the 850, never retype it
PO number typo in OID02Request cannot be matched to an open POBuild OID02 from the order record, not free text
Pickup window your dock cannot meetCarrier arrives to unready freightOffer only windows the warehouse has confirmed
Duplicate routing request numberSecond request rejected, or replies crossGenerate RRC values from one sequence
Change sent as a new originalRetailer plans the same freight twiceUse the change or replace purpose code with the reference the guide asks for
No 754 and nobody noticesFreight sits on the dockAlert when a 753 has no 754 within the expected time

753 Implementation Checklist

  • Get the retailer's routing guide and 753/754 guide, and confirm the X12 version
  • Confirm which POs are collect and how the 850 shows it
  • Confirm the IDs it expects for ship-from (N1*SF) and ship-to (N1*ST)
  • Confirm how many destinations one 753 may carry
  • Agree the reference numbers: what goes in BGN02, BGN06, L11 and OID03
  • Pull packages, weight, cube, pallet count and stackability from your warehouse system
  • Set the minimum lead time and default pickup window per ship-from location
  • Map changes and cancellations with the right purpose codes
  • Match each returning 754 to its 753 and feed the carrier and appointment into shipping
  • Test an original, a change, a cancellation, a multi-PO request and a multi-destination request

For the wider picture, see our EDI compliance guide, the EDI document types reference, and retailer notes for Walmart, Target and Amazon.

Where OrderSync Fits

Every 753 is built from purchase orders, so the request is only as accurate as the orders behind it. Those orders reach you as EDI 850s and 875s, PDFs, emails and spreadsheets, and the ship-to IDs, items and units have to be right before your warehouse can pick and pack them.

OrderSync reads inbound orders in any format, matches customers, items and units to your catalog, and outputs clean ERP data or valid X12, so the orders your warehouse ships and routes start out correct. Paste any 753 into the free EDI inspector to see it parsed with a plain-English summary and totals per destination, or book a 15-minute walkthrough to see your own orders processed.

Frequently Asked Questions

What is an EDI 753?

The EDI 753 Request for Routing Instructions is an X12 transaction a supplier sends to a buyer when freight is ready and the buyer controls the shipping. It lists the ship-from and ship-to locations, the pickup window, pallet counts, and each purchase order's packages, weight and cube, so the buyer can plan the load.

What is the difference between EDI 753 and 754?

The 753 is the supplier's request: here is what is ready and when it can be picked up. The 754 is the retailer's reply: here is the carrier, load number and pickup appointment, and which purchase orders ship together. You send the 753 and receive the 754.

When should I send an EDI 753?

Once the purchase orders are packed and you know real cartons, weight and cube, and early enough to meet the retailer's minimum lead time before the earliest pickup date. The retailer's routing guide sets that lead time.

Do I need to send a 753 for prepaid freight?

No. The 753 is for collect, buyer-routed freight, where the retailer picks and pays the carrier. On prepaid freight you book your own carrier. Retailers often mix both, so check the freight terms on each purchase order.

What does the OID segment contain in an EDI 753?

One OID per purchase order: your order number in OID01, the retailer's PO number in OID02, the packaging form and quantity in OID04 and OID05, weight unit and weight in OID06 and OID07, and volume unit and volume in OID08 and OID09.

What does G62 EP and LP mean in a 753?

They define the pickup window. G62 with EP gives the earliest pickup date and time, and G62 with LP gives the latest. The retailer schedules the carrier inside that window.

What X12 version is the EDI 753?

The 753 first appears in X12 release 004030 and is not part of 004010. Retailers publish 753 guides in 004030 or later releases, and the version appears in GS08 of the functional group.

What happens if I do not receive a 754?

Do not ship collect freight on your own carrier. Check that the retailer's 997 accepted your 753, then contact its routing desk. Many suppliers set an alert for any 753 that has no 754 within the expected turnaround.

James Darby
Last updated: 11/3/2026

Related Resources