# EDI 754 Routing Instructions: The 753 Response
> EDI 754 Routing Instructions explained: how retailers answer a 753 routing request, the BLR, L11, OID, G62 and MSI segments, live examples and common errors.
The EDI 754 Routing Instructions is the X12 transaction a retailer sends a supplier to say how a buyer-controlled shipment will move: which carrier collects it (by SCAC), the load and pickup appointment numbers, the scheduled pickup date, and which purchase orders travel together. It usually answers the supplier's 753 Request for Routing Instructions.
**The EDI 754 is the retailer's answer to "who is picking this up, and when?"** When a retailer pays for inbound freight and picks the carrier, the supplier cannot just book a truck. It asks for routing with a [753 Request for Routing Instructions](/guides/edi/753-request-for-routing-instructions), and the retailer's transportation team replies with a 754. Everything your dock, your bill of lading and your ASN need about the move comes from that reply.
This guide covers what the 754 carries, how the 753 and 754 work together on collect freight, every segment you will map, two live examples (a two-carrier response and a multi-stop truckload), and the errors that cause missed pickups and refused loads.
## What Is an EDI 754?
**An EDI 754 is the Routing Instructions transaction set defined by [ASC X12](https://x12.org/products/transaction-sets), used by a buyer to tell a supplier how a specific shipment will be routed: the carrier, the pickup date and appointment, the load it belongs to, and the destination.** The X12 standard describes it as communicating routing instructions to a supplier for a specific shipment, and notes it can be sent in response to a 753. It travels in functional group `RG` (the `GS01` value), and its partner, the 753, travels in group `RF`.
Authoritative references for 754 work:
- The [X12 transaction set catalog](https://x12.org/products/transaction-sets) defines the 753 and 754 structures, segment order and loops
- The [National Motor Freight Traffic Association (NMFTA)](https://nmfta.org/what-is-scac-and-how-do-carriers-get-it) issues the Standard Carrier Alpha Codes (SCACs) the 754 uses to name the carrier
- Each retailer publishes its own routing guide and 753/754 implementation guide, which set the lead times, the reference numbers it sends, and what it expects on the bill of lading
**Who sends it?** The buyer, usually the retailer's inbound transportation team or the logistics provider that manages its freight.
**Who receives it?** The supplier, or the supplier's warehouse or 3PL that will load the truck.
**When is it sent?** After the supplier's 753, once the retailer has planned the load and booked a carrier. Some retailers also send a 754 without a 753, for example when they plan loads straight from open purchase orders.
**Why does it matter?** On collect freight the retailer owns the move. Ship with a carrier it did not assign, or outside the appointment it gave, and the routing guide's compliance rules apply. The 754 is your written instruction, and your proof that you followed it.
## Collect Freight and Why Retailers Route It
Two freight terms decide whether you ever see a 754.
| | Prepaid (vendor-routed) | Collect (buyer-routed) |
|---|---|---|
| **Who books the carrier** | Supplier | Retailer or its logistics provider |
| **Who pays the freight** | Supplier, often built into cost | Retailer, under its own carrier contracts |
| **How you learn the carrier** | You choose it | The retailer tells you, often on a 754 |
| **What you send first** | An [856 ASN](/guides/edi/856-ship-notice) once it ships | A 753 routing request when freight is ready, then the 856 |
| **Main risk** | Freight cost | Missing the appointment or using the wrong carrier |
Large retailers move a lot of inbound freight on collect terms because they can consolidate many suppliers' orders onto full truckloads, use their own negotiated carrier rates, and schedule arrivals at the distribution center to match dock capacity. The freight terms on your [850 purchase order](/guides/edi/850-purchase-order) and the retailer's routing guide tell you which applies. See our glossary entry on [FOB shipping terms](/glossary/fob-shipping) for how freight terms and title interact.
### Which retailers use the 753 and 754?
Retailers that publish 753/754 implementation guides include Kohl's, Amazon (for vendor shipments), JCPenney, and the military exchanges, such as AAFES and the Navy Exchange (NEXCOM). Walmart and Target also route a large share of their inbound freight under collect programs. Depending on the program, the routing request goes through EDI or through the retailer's own supplier portal, so read the retailer's current routing guide before you build a map. Whether the 753/754 is required, optional or replaced by a web form varies by retailer and sometimes by vendor.
## How the 753 and 754 Work Together
The pair runs as a request and an answer, with the carrier's own documents happening in the background.
1. **Freight is ready.** Your warehouse has picked and packed the purchase orders. You know cartons, weight, cube and pallet count.
2. **Supplier sends a 753.** It lists the ship-from location, each destination, the pickup window and, per PO, the cartons, weight and volume. See the [EDI 753 guide](/guides/edi/753-request-for-routing-instructions) for the full structure.
3. **Retailer plans the load.** Its transportation system groups your orders, sometimes with other suppliers' freight, into loads and picks a mode (parcel, LTL or truckload).
4. **Retailer books the carrier.** It tenders the load to a carrier, often with an [EDI 204 load tender](/guides/edi/204-motor-carrier-load-tender) that the carrier accepts with a [990](/guides/edi/990-response-to-load-tender).
5. **Retailer sends the 754.** It names the carrier, the load number, the pickup appointment and date, and which POs go on which shipment.
6. **Supplier prepares the load.** You print the bill of lading with the 754's references, stage the freight and confirm the dock schedule.
7. **Carrier picks up.** The carrier collects under the retailer's account and reports progress with [214 status messages](/guides/edi/214-transportation-carrier-shipment-status) to the retailer.
8. **Supplier sends the 856.** Your ASN carries the carrier and bill of lading details that match the 754.
If something changes after step 5, the retailer can send another 754 with a change or cancellation purpose code, and you can update or cancel your request with a new 753. The retailer's guide says which reference numbers tie the revisions together.
## Interactive Example: 754 Response to a Routing Request
A home goods supplier in Grand Rapids sent a 753 for three purchase orders going to two distribution centers. The retailer answers with one `LX` loop per shipment. Each loop echoes the supplier's routing request number in `L11` (qualifier `RRC`), adds a load number (`LO`) and a pickup appointment number (`PUA`), names the carrier in `BLR`, lists the purchase orders in `OID`, schedules the pickup in `G62`, and closes with the destination in the `N1` loop. The two DCs get two different LTL carriers. All names, IDs and SCACs are fictional.
Use the **Plain English** tab for a readable summary, or click any segment to break it down element by element.
## Interactive Example: 754 Multi-Stop Truckload
Here the retailer consolidates two of the supplier's orders onto one truckload that delivers to two DCs. Both `LX` loops carry the same carrier, load number and pickup appointment. The `MSI` segment flags the shipment as multi-stop and gives each destination its stop sequence, so the supplier knows to load stop 2's freight first, at the nose of the trailer, and stop 1's freight at the doors.
## 754 Structure at a Glance
The table follows the X12 004030 release, the first release that includes the 753 and 754. Later releases (such as 005010) keep the same core.
| Position | Segment | Name | Usage | Notes |
|---|---|---|---|---|
| Heading | **ST** | Transaction Set Header | Mandatory | `ST01` = `754` |
| Heading | **BGN** | Beginning Segment | Mandatory | Purpose code, routing instruction number, date and time |
| Heading | **PER** | Administrative Communications Contact | Optional | The retailer's routing desk |
| Heading loop | **N1 / N2 / N3 / N4** | Name and address | Mandatory, up to 5 | The ship-from location, plus other parties the guide names |
| Detail loop (LX) | **LX** | Assigned Number | Mandatory, repeats | One loop per routed shipment |
| Detail loop | **L11** | Business Instructions and Reference Number | Optional, up to 5 | Routing request, load, appointment and other references |
| Detail loop | **BLR** | Transportation Carrier Identification | Optional | The assigned carrier's SCAC |
| Detail loop | **OID** | Order Identification Detail | Optional, repeats | One per purchase order on the shipment |
| Detail loop | **G62** | Date/Time | Optional, up to 2 | Scheduled pickup date and time |
| Detail loop | **MSI** | Multi-stop Shipment Information | Optional | Multi-stop flag and stop sequence |
| Nested loop | **QTY / AT9** | Quantity, trailer dimensions and weight | Optional | Used by some retailers for load or equipment detail |
| Nested loop | **N1 / N2 / N3 / N4** | Name and address | Optional | The destination for this shipment |
| Summary | **SE** | Transaction Set Trailer | Mandatory | Segment count and control number |
"Optional" in the standard often means "required" in a retailer's guide. Many guides make `L11`, `BLR`, `OID` and `G62` mandatory in every loop.
## Key Segments Explained
### BGN: Beginning Segment
```
BGN*00*RI-20261105-3318*20261105*1415~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **BGN01** | Transaction Set Purpose Code | `00` | `00` original, `01` cancellation, `04` change, `05` replace. Guides list the codes they send |
| **BGN02** | Reference Identification | `RI-20261105-3318` | The retailer's number for this set of routing instructions |
| **BGN03** | Date | `20261105` | Date the instructions were issued |
| **BGN04** | Time | `1415` | Time issued |
| **BGN06** | Reference Identification | | The number of an earlier transaction this one affects, used on some changes and cancellations |
Store `BGN02` with the shipment. If the retailer later sends a change or cancellation, you will need it to find the right load. Some retailers put their load or shipment ID in `BGN02` instead of in an `L11`; the guide says which.
### N1 Loop (Heading): Ship-From
```
N1*SF*LAKESHORE HOME GOODS*92*V48213~
N3*4100 EASTERN AVE SE~
N4*GRAND RAPIDS*MI*49508*US~
```
The heading `N1` loop identifies the pickup location (`N101` = `SF`, ship from), usually with the ID the retailer assigned to that location (`N103` = `92`, assigned by buyer). If you ship from several warehouses, check that the ID matches the one you sent on the 753, or the carrier may be sent to the wrong building.
### LX: Assigned Number
```
LX*1~
```
`LX01` numbers each routed shipment in the transaction. Everything until the next `LX` belongs to that shipment: references, carrier, orders, pickup time and destination.
### L11: Business Instructions and Reference Number
```
L11*RR784501*RRC~
L11*LD6021-88412*LO~
L11*PU-30917*PUA~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **L1101** | Reference Identification | `LD6021-88412` | The reference value |
| **L1102** | Reference Identification Qualifier | `LO` | What the value is (see below) |
| **L1103** | Description | | Free-text note, used by some retailers for loading instructions |
Common qualifiers on a 754 include `RRC` (routing request control number, echoing the number on your 753), `LO` (load planning number), `PUA` (pick up appointment number), `CN` (carrier's PRO number) and `BM` (bill of lading number). Which ones a retailer sends, and which it wants printed on the bill of lading, is set by its guide. The load number is the reference retailers most often ask to see on the BOL and the ASN.
### BLR: Transportation Carrier Identification
```
BLR*QLTX~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **BLR01** | Standard Carrier Alpha Code | `QLTX` | The SCAC of the carrier the retailer assigned |
| **BLR02** | Date | | Effective date of the data |
| **BLR03** | Time | | Effective time of the data |
The SCAC is a two-to-four letter code issued by NMFTA. It is how the carrier is named on your bill of lading and in the `TD5` segment of your 856. Your shipping system should look the SCAC up in a carrier table rather than accept free text, so the dock prints the right carrier name and the ASN carries the right code. See our [SCAC code glossary entry](/glossary/scac-code) for background.
### OID: Order Identification Detail
```
OID*SO-55120*4500781234**CTN*220*L*4180*E*610~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **OID01** | Reference Identification | `SO-55120` | The seller's order number, as sent on the 753 |
| **OID02** | Purchase Order Number | `4500781234` | The retailer's PO number |
| **OID03** | Reference Identification | | A consignee reference that further defines the PO; some retailers send a shipment ID here |
| **OID04** | Packaging Form Code | `CTN` | `CTN` carton, `PLT` pallet, `PCS` pieces |
| **OID05** | Quantity | `220` | Number of packages in that form |
| **OID06** | Weight Unit Code | `L` | `L` pounds |
| **OID07** | Weight | `4180` | Weight of the order |
| **OID08** | Volume Unit Qualifier | `E` | `E` cubic feet |
| **OID09** | Volume | `610` | Cube of the order |
The `OID` lines tell you which POs the retailer put on which shipment. Compare them with what you asked for on the 753. If a PO you requested is missing from every `LX` loop, it has not been routed yet; do not load it on this truck. If the cartons or weight differ from your 753, the retailer planned on the numbers it shows, so check whether your warehouse changed the order after you sent the request.
### G62: Date/Time
```
G62*69*20261111*U*0900~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **G6201** | Date Qualifier | `69` | `69` scheduled pick-up date. Some guides use `77` (pickup appointment scheduled date) |
| **G6202** | Date | `20261111` | The pickup date |
| **G6203** | Time Qualifier | `U` | `U` scheduled pick up time. Some guides use `2` (pickup appointment scheduled time) |
| **G6204** | Time | `0900` | The pickup time |
This is the appointment your dock has to meet. Put it straight into your shipping schedule, and flag any 754 whose pickup date falls outside the window you offered on the 753 (`G62` with `EP` and `LP` qualifiers on the request).
### MSI: Multi-stop Shipment Information
```
MSI*Y*2~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **MSI01** | Yes/No Condition or Response Code | `Y` | `Y` the shipment is multi-stop, `N` it is not |
| **MSI02** | Stop Sequence Number | `2` | This shipment's place in the stop sequence |
When a load has more than one stop, loading order matters: the last stop's freight goes on first. The retailer's guide says how it numbers stops and whether the sequence covers pickups, deliveries or both.
### N1 Loop (Detail): Destination
```
N1*ST*BIG-BOX RETAILER DC 6021*92*6021~
N3*1200 DISTRIBUTION PKWY~
N4*COLUMBUS*OH*43217*US~
```
The last loop inside each `LX` names where the shipment is going (`N101` = `ST`). The ID in `N104` is normally the same DC or store number that appeared on the purchase order's ship-to. A mismatch here is worth stopping for: it usually means the retailer re-routed the freight to a different building.
## 753 vs 754 vs 856, 204 and 214
The routing documents sit between the purchase order and the shipment, and they are easy to confuse with carrier-side documents.
| Document | Sent by | Sent to | Purpose |
|---|---|---|---|
| **[753 Request for Routing Instructions](/guides/edi/753-request-for-routing-instructions)** | Supplier | Retailer | Freight is ready; here are the orders, weights, cube and pickup window |
| **754 Routing Instructions** | Retailer | Supplier | Here is the carrier, load number, appointment and which POs ship together |
| **[856 Ship Notice/ASN](/guides/edi/856-ship-notice)** | Supplier | Retailer | What actually shipped, down to carton, with carrier and BOL details |
| **[204 Motor Carrier Load Tender](/guides/edi/204-motor-carrier-load-tender)** | Shipper (here, the retailer) | Carrier | Offers the load to the carrier |
| **[990 Response to Load Tender](/guides/edi/990-response-to-load-tender)** | Carrier | Shipper | Accepts or declines the tender |
| **[214 Shipment Status](/guides/edi/214-transportation-carrier-shipment-status)** | Carrier | Shipper | Pickup, in-transit and delivery events |
The short version: the 753 and 754 are a supplier-to-retailer conversation about a move the retailer controls. The 204, 990 and 214 are the retailer's conversation with the carrier about the same move. The 856 closes the loop by telling the retailer what was actually on the truck.
## Which X12 Version Do the 753 and 754 Use?
The 753 and 754 were added to X12 in release 004030. They do not exist in 004010, the release many suppliers still use for their 850, 856 and 810. So a retailer can run its order cycle on 004010 and its routing on 004030 or later, and the 753/754 implementation guide will state the version. If your translator only has 004010 maps loaded, you will need the later release's dictionary for these two sets. The `GS08` value in each functional group tells the receiver which version to parse against.
## Common 754 Errors and How to Prevent Them
| Error | What happens | Prevention |
|---|---|---|
| **754 not matched to the 753** | Routing sits unread; freight misses its appointment | Match on the routing request number in `L11*RRC` (or the reference the guide names) and alert when a 753 has no 754 within the guide's lead time |
| **Wrong carrier tendered** | Freight moves on a carrier the retailer did not assign | Take the carrier from `BLR01` only; block manual carrier changes on collect POs |
| **Load number missing from the BOL** | DC cannot match the trailer to its plan | Print every reference the guide requires from the `L11` segments onto the BOL |
| **PO loaded that was not routed** | Freight arrives with no appointment at the DC | Load only POs that appear in an `OID` on this `LX` loop |
| **Pickup appointment missed** | Carrier arrives to unready freight, or leaves without it | Feed `G62` into the dock schedule automatically, and only offer pickup windows on the 753 your warehouse can meet |
| **Change or cancellation ignored** | Supplier ships to an old plan | Process `BGN01` purpose codes and update or release the shipment on `04` and `01` |
| **Multi-stop loaded in the wrong order** | Freight for stop 1 is buried behind stop 2 | Use `MSI02` to build the load sequence |
| **ASN carrier differs from the 754** | ASN rejected or flagged at receiving | Populate the 856 `TD5` and BOL references from the 754, not from the warehouse default |
| **753 sent with wrong weights or cube** | Retailer plans the wrong equipment | Send weights and cube from the packed cartons, not from the PO |
Most of these problems start before the 754 arrives. A 753 with accurate cartons, weight and cube, sent on time, is the best way to get a usable 754 back.
## 754 Implementation Checklist
Before your first live 754 with a retailer:
- Get the retailer's routing guide and its 753/754 implementation guide, and confirm the X12 version (004030 or later)
- Confirm which POs are collect and which are prepaid, and how the PO tells you
- Agree how the 754 references your 753 (routing request number, BGN reference, shipment ID)
- List the `L11` qualifiers it sends and which ones must appear on the bill of lading
- Load its carriers' SCACs into your shipping system
- Map `G62` pickup dates and times into your dock or warehouse schedule
- Decide how changes (`04`) and cancellations (`01`) update an open shipment
- Map the 754's carrier and references into your 856 `TD5` and `REF` segments
- Confirm the 997 you will send back for each 754, and monitor the 997s you receive for your 753s
- Test an original, a change, a cancellation, a multi-PO shipment and a multi-stop load
If you are new to retail EDI, our [EDI compliance guide](/edi-compliance) and [EDI document types reference](/edi-document-types) show how routing fits next to the purchase order, ASN and invoice. Retailer-specific notes are on our [Walmart](/edi-compliance/walmart), [Target](/edi-compliance/target) and [Amazon](/edi-compliance/amazon) compliance pages.
## Where OrderSync Fits
Routing starts with an order. Before a 753 goes out, someone has to get the purchase order into your ERP with the right ship-to, items, units and freight terms, whether it arrived as an EDI 850 or 875, a PDF, an email or a spreadsheet.
OrderSync reads those inbound orders in any format, matches customers, items and units to your catalog, and outputs clean ERP data or valid X12. That gives your warehouse accurate POs to pick against and gives your routing request accurate numbers to send. Paste any 754 into the [free EDI inspector](/edi-inspector) to see it parsed segment by segment with a plain-English summary, or [book a 15-minute walkthrough](/book-call) to see your own orders processed.
## Frequently Asked Questions
### What is an EDI 754?
The EDI 754 Routing Instructions is an X12 transaction a retailer sends to a supplier to say how a shipment will be routed: the assigned carrier, the load number, the pickup appointment and date, and which purchase orders ship together. It is used for collect freight, where the retailer controls and pays for transportation.
### What is the difference between EDI 753 and 754?
The supplier sends the 753 Request for Routing Instructions when freight is ready, listing the orders, weights, cube and pickup window. The retailer replies with the 754 Routing Instructions, naming the carrier, the pickup appointment and the load. The 753 is the question and the 754 is the answer.
### What is an EDI 754 routing response?
It is the 754 sent in reply to a supplier's 753. The retailer echoes the routing request number, usually in an L11 segment, so the supplier can match the answer to its request, then adds the carrier SCAC, load number, appointment number and scheduled pickup for each shipment.
### Which segment in the 754 names the carrier?
The BLR segment. BLR01 carries the Standard Carrier Alpha Code (SCAC) of the carrier the retailer assigned. That SCAC should go on your bill of lading and in the TD5 segment of your 856 ASN.
### Do I need a 754 if I ship prepaid?
Usually not. On prepaid, vendor-routed freight you choose and pay the carrier, so there is nothing to route. The 754 applies to collect or buyer-routed purchase orders. Some retailers mix both, so check the freight terms on each PO and the retailer's routing guide.
### What X12 version is the EDI 754?
The 753 and 754 first appear in X12 release 004030. They are not part of 004010. Retailers publish 754 guides in 004030 or later releases, and the version is named in GS08 of each functional group.
### What happens if I ship with a different carrier than the 754 says?
The retailer's routing guide decides. On collect freight the retailer has contracted the carrier, so a shipment on an unassigned carrier is a routing guide violation, and the freight cost and any compliance penalties fall under the retailer's published rules.
### What should I do when a 754 changes or cancels a shipment?
Check BGN01. A change or cancellation code means the earlier instructions no longer apply. Update the carrier, load number and appointment on the open shipment, or release the freight back to stock on a cancellation, before the dock loads it.