X12 transaction code
EDI 754 Routing Instructions (X12 754)
EDI 754 is the X12 Routing Instructions transaction set, used when routing details are issued in response to a shipment need. The retailer or the buyer's transportation organization sends the 754 to the supplier that requested routing, naming the carrier and pickup window for the shipment.
- Standard
- X12
- Code
- 754
- Partner references
- 5
At a glance
EDI 754 at a glance
What the 754 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 754 Routing Instructions |
|---|---|
| Business record | Routing instruction |
| Who sends it to whom | The retailer or the buyer's transportation organization sends the 754 to the supplier that requested routing, naming the carrier and pickup window for the shipment. |
| When it is sent | The buyer's transportation team completes carrier assignment for a supplier's routing request and releases pickup instructions ahead of the scheduled ship window. |
| Match on | Routing reference, order and shipment |
| Partner references | 5 trading partners in this directory |
| Related documents | X12 753 Request for Routing Instructions, X12 856 Ship Notice/Manifest |
Key segments in an EDI 754
The business segments that appear in at least half of the 6 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BGN | Beginning Segment | To indicate the beginning of a transaction set. | 6 of 6 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 6 of 6 |
| N3 | Party Location | To specify the location of the named party. | 6 of 6 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 6 of 6 |
| LX | Transaction Set Line Number | To reference a line number in a transaction set. | 6 of 6 |
| L11 | Business Instructions and Reference Number | To specify instructions in this business relationship or a reference number. | 6 of 6 |
| G62 | Date/Time | To specify pertinent dates and times. | 6 of 6 |
| OID | Order Information Detail | To specify order information detail. | 5 of 6 |
| PER | Administrative Communications Contact | To identify a person or office to whom administrative communications should be directed. | 4 of 6 |
| BLR | Transportation Carrier Identification | To transmit the identifying SCAC code and effective date and time for the data in the transaction set. | 4 of 6 |
Stacksync connects EDI documents such as the X12 754 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 754 mapping and validation
X12 754 Routing Instructions is used when routing details are issued in response to a shipment need. Preserve routing reference, order and shipment so the routing instruction in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | routing instruction routing reference, order and shipment |
|
| Update the receiving system | Processing the routing instruction ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the routing instruction Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 753 Request for Routing Instructions
routing request: a supplier needs shipping instructions.
- X12 856 Ship Notice/Manifest
shipment notice (ASN): an order ships, before the goods arrive.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when routing details are issued in response to a shipment need. Name the operational owner of the routing instruction and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map routing reference, order and shipment. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic routing instruction data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful routing instruction processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 754 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic routing instruction data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out routing instruction without processing it twice.
Document structure
X12 754 Routing Instructions at the element level
The X12 754 reference contains 23 segment entries and 64 data elements; 40 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 23
- Data elements
- 64
- Mandatory elements
- 40
| Segment | Elements | Mandatory |
|---|---|---|
| BGN | 4 | 3 |
| N1 | 2 | 1 |
| N2 | 1 | 1 |
| N3 | 1 | 1 |
| LX | 1 | 1 |
| BLR | 1 | 1 |
| SMD | 2 | 2 |
| MSI | 2 | 1 |
- Transaction Set Purpose Code
- Reference Identification
- Date
- Entity Identifier Code
- Name
- Address Information
- Assigned Number
- Standard Carrier Alpha Code
Find your trading partner for X12 754
5 partners, 6 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 754 Routing Instructions appears in this catalog
The largest groups of classified 754 catalog entries are in electronics & technology, retail and apparel & footwear.
By industry
- electronics & technology 2 channels
- retail 2 channels
- apparel & footwear 1 channel
- e-commerce & marketplaces 1 channel
FAQ
EDI 754 questions
What is an EDI 754?
EDI 754 is the X12 Routing Instructions transaction set. Trading partners use it when routing details are issued in response to a shipment need. It carries the data for the routing instruction, and your system matches it on routing reference, order and shipment.
Who sends an EDI 754 and who receives it?
The retailer or the buyer's transportation organization sends the 754 to the supplier that requested routing, naming the carrier and pickup window for the shipment. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 754 sent?
The buyer's transportation team completes carrier assignment for a supplier's routing request and releases pickup instructions ahead of the scheduled ship window. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 754?
Across 6 partner document references listed here, the business segments that appear most often include BGN (Beginning Segment), N1 (Party Identification), N3 (Party Location), N4 (Geographic Location), LX (Transaction Set Line Number), L11 (Business Instructions and Reference Number). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 754 and EDI 753?
The 754 carries the routing instruction and is used when routing details are issued in response to a shipment need. The 753 carries the routing request and is used when a supplier needs shipping instructions.
What should I map for X12 754?
Start with routing reference, order and shipment and the target routing instruction. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 754 error handling?
Match instructions to the correct open routing request. Test a carrier reassignment after warehouse planning and require the shipping record to be updated. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 754?
The directory on this page links 5 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
