972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Shipping and logistics

EDI 754 Routing Instructions

The X12 document a retailer or its routing provider sends to tell a supplier how to ship an order, including the carrier and pickup details.

Sent by
Retailer or buyer (or its routing provider)
Received by
Supplier or vendor
Standard
ANSI ASC X12

What is an EDI 754?

The EDI 754 Routing Instructions is the ANSI X12 transaction set a buyer uses to send a supplier the routing for a specific shipment. It identifies the ship-from location and, for each shipment, the reference numbers, the carrier by its SCAC code, the pickup date and the purchase orders and quantities the routing covers. It can answer a 753 request for routing instructions or be sent on its own.

Routing instructions are part of buyer-controlled freight programs, where the retailer chooses the carrier to consolidate loads and manage inbound costs. A supplier that ships without following the 754, or ships before the scheduled pickup, can face chargebacks. Like the 753, the 754 first appears in X12 release 4030.

How the EDI 754 worksDiagram of the EDI 754 Routing Instructions. Retailer or buyer (or its routing provider) sends it to supplier or vendor. It usually follows 753. It is usually followed by 856 and 997. Inside the ISA, GS and ST envelopes, X12 release 005010 requires, in the heading: BGN (Beginning Segment) and the required 0100 loop with N1 (Party Identification) and detail: the required 0200 loop with LX (Transaction Set Line Number). 2 optional loops are listed by their first segment.How the EDI 754 worksRouting Instructions: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS753Request for RoutingInstructionsEDI 754SENDERRetailer or buyer (orits routing provider)RECEIVERSupplier or vendor997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY856Advance Ship Notice997FunctionalAcknowledgment2 WHAT X12 RELEASE 005010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RGGS … GETransaction set 754ST … SEHEADINGBGNBeginning SegmentRequired loop 0100 · repeats up to 5N1Party IdentificationDETAILRequired loop 0200 · repeats up to 9,999LXTransaction Set Line Number+ 2 optional loops, starting with:QTYN1Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 005010 listing for the 754. Your trading partner's implementation guide adds its own requirements.
How the EDI 754 worksDiagram of the EDI 754 Routing Instructions. Retailer or buyer (or its routing provider) sends it to supplier or vendor. It usually follows 753. It is usually followed by 856 and 997. Inside the ISA, GS and ST envelopes, X12 release 005010 requires, in the heading: BGN (Beginning Segment) and the required 0100 loop with N1 (Party Identification) and detail: the required 0200 loop with LX (Transaction Set Line Number). 2 optional loops are listed by their first segment.How the EDI 754 worksRouting Instructions: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS753Request for Routing InstructionsEDI 754SENDERRetailer or buyer(or its routingprovider)RECEIVERSupplier orvendor997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY856Advance Ship Notice997Functional Acknowledgment2 WHAT X12 RELEASE 005010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code RG (GS … GE)Transaction set 754 (ST … SE)HEADINGBGNBeginning SegmentRequired loop 0100 · repeats upto 5N1Party IdentificationDETAILRequired loop 0200 · repeats upto 9,999LXTransaction Set LineNumber+ 2 optional loops, starting with:QTYN1Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12005010 listing for the 754. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 754, to whom, and which documents usually come before and after it. The lower part shows what X12 release 005010 itself requires: the envelopes around the 754 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Answering a supplier's 753 request for routing
  • Assigning a carrier and pickup date for buyer-controlled freight
  • Consolidating several purchase orders into one shipment
  • Changing routing after an earlier instruction

Where it fits in the document flow

Usually follows 753 Request for Routing Instructions
This document 754 Routing Instructions
Usually followed by 856 Advance Ship Notice997 Functional Acknowledgment

Structure

Key segments in the 754

The segments most implementations use, described in plain language. The last column shows what X12 release 005010 itself requires: "Required" marks a segment the standard requires in every 754; "Optional, common" marks a segment the standard leaves optional, or that sits in an optional loop, but that implementations often use. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, makes some optional segments mandatory and restricts the values, and requirements can differ between releases. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

SegmentNameWhat it carriesIn X12 005010
BGNBeginning SegmentPurpose code, the routing instruction reference number and its date.Required
N1 loop (ship from)Party IdentificationThe ship-from location the routing applies to.Required
LXTransaction Set Line NumberStarts each routed shipment in the detail loop.Required
L11Business Instructions and Reference NumberReference numbers such as the supplier's routing request or a load identifier.Optional, common
BLRTransportation Carrier IdentificationThe assigned carrier's SCAC code and when the routing takes effect.Optional, common
G62Date/TimeDates such as the scheduled pickup date.Optional, common
OIDOrder Information DetailThe purchase orders, quantities, weight and volume included in the routed shipment.Optional, common

Example

Sample EDI 754

An original (00) routing instruction answering request RR12345 (L11 qualifier CR). It schedules a pickup (G62 qualifier 69) on 23 October for 24 cartons on PO45001. Real 754s also name the carrier, typically by its SCAC code in the BLR segment.

Illustrative data only, not tied to one X12 release or trading partner. The interchange (ISA/IEA) and functional group (GS/GE) envelopes are omitted for readability.

ST*754*0001~
BGN*00*RI7781*20261021~
N1*SF*Example Supplier DC~
LX*1~
L11*RR12345*CR~
G62*69*20261023~
OID**PO45001**CTN*24*L*480~
SE*8*0001~
Reading a sample EDI 754, line by lineAnnotated sample EDI 754 with 8 lines. Notes explain the ST, BGN, N1, LX, L11, G62, OID and SE segments.Reading a sample EDI 754, line by lineEach numbered note explains the segment on that line. The data is illustrative.ST*754*0001~11Transaction Set Header. Opens the 754 and gives it a controlnumber, which SE repeats.BGN*00*RI7781*20261021~22Beginning Segment. Purpose code, the routing instructionreference number and its date.N1*SF*Example Supplier DC~33Party Identification. The ship-from location the routing appliesto.LX*1~44Transaction Set Line Number. Starts each routed shipment in thedetail loop.L11*RR12345*CR~55Business Instructions and Reference Number. Referencenumbers such as the supplier's routing request or a loadidentifier.G62*69*20261023~66Date/Time. Dates such as the scheduled pickup date.OID**PO45001**CTN*24*L*480~77Order Information Detail. The purchase orders, quantities,weight and volume included in the routed shipment.SE*8*0001~88Transaction Set Trailer. Closes the set with the number ofsegments, including ST and SE, and the same control number.Illustrative data only, not tied to one trading partner. Envelopes (ISA/GS) are omitted for readability.
Reading a sample EDI 754, line by lineAnnotated sample EDI 754 with 8 lines. Notes explain the ST, BGN, N1, LX, L11, G62, OID and SE segments.Reading a sample EDI 754, lineby lineEach numbered note explains the segment onthat line. The data is illustrative.ST*754*0001~Transaction Set Header. Opens the 754 andgives it a control number, which SE repeats.BGN*00*RI7781*20261021~Beginning Segment. Purpose code, the routinginstruction reference number and its date.N1*SF*Example Supplier DC~Party Identification. The ship-from locationthe routing applies to.LX*1~Transaction Set Line Number. Starts eachrouted shipment in the detail loop.L11*RR12345*CR~Business Instructions and Reference Number.Reference numbers such as the supplier'srouting request or a load identifier.G62*69*20261023~Date/Time. Dates such as the scheduledpickup date.OID**PO45001**CTN*24*L*480~Order Information Detail. The purchaseorders, quantities, weight and volume includedin the routed shipment.SE*8*0001~Transaction Set Trailer. Closes the set withthe number of segments, including ST and SE,and the same control number.Illustrative data only, not tied to one trading partner.Envelopes (ISA/GS) are omitted for readability.

The sample is the same one shown above, with a note beside each segment the first time it appears. Segment IDs are highlighted at the start of each line; the fields after them are separated by asterisks, and each segment ends with a tilde.

Expand diagram Download SVG

Avoid problems

Common 754 errors and how to prevent them

Shipping with the wrong carrier

Using a carrier other than the one in the 754 usually breaks the retailer's routing guide and can lead to freight chargebacks. Route the instruction to the shipping team automatically.

Not matching replies to requests

Each 754 should be matched to the 753 it answers. Unmatched or duplicate instructions need review before goods are released.

Ignoring changed routing

A later 754 can change an earlier instruction. Use the latest instruction for each shipment and keep the history for disputes.

Trading partners

Integration guides that include the 754

  • AT&T EDI integration

How ECOM helps

Automate the 754 with ECOM

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

EDI 754 FAQs

What does a supplier do after receiving a 754?

It books or prepares the pickup with the assigned carrier, ships on the scheduled date and then sends the ship notice (856) that the retailer requires.

Is a 754 always a reply to a 753?

No. It often answers a 753, but a buyer can also send routing instructions without a request, for example for a standing pickup schedule.

How is the carrier identified in a 754?

Usually by its Standard Carrier Alpha Code (SCAC), carried in the BLR segment, so suppliers and carriers can match the instruction to the right company.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related shipping and logistics documents

All 15 shipping and logistics documents

Need help with the EDI 754?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us