X12 transaction code
EDI 753 Request for Routing Instructions (X12 753)
EDI 753 is the X12 Request for Routing Instructions transaction set, used when a supplier needs shipping instructions. A supplier or vendor sends the 753 to the retailer or the buyer's transportation organization, which answers with an EDI 754 Routing Instructions.
- Standard
- X12
- Code
- 753
- Partner references
- 4
At a glance
EDI 753 at a glance
What the 753 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 753 Request for Routing Instructions |
|---|---|
| Business record | Routing request |
| Who sends it to whom | A supplier or vendor sends the 753 to the retailer or the buyer's transportation organization, which answers with an EDI 754 Routing Instructions. |
| When it is sent | A supplier has an order picked and ready to ship on a collect or buyer-managed freight program and needs the retailer to assign the carrier before booking pickup. |
| Match on | Routing request, purchase order and ready-to-ship date |
| Partner references | 4 trading partners in this directory |
| Related documents | X12 754 Routing Instructions, X12 850 Purchase Order, X12 856 Ship Notice/Manifest |
Key segments in an EDI 753
The business segments that appear in at least half of the 5 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. | 5 of 5 |
| PER | Administrative Communications Contact | To identify a person or office to whom administrative communications should be directed. | 5 of 5 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 5 of 5 |
| LX | Transaction Set Line Number | To reference a line number in a transaction set. | 5 of 5 |
| G62 | Date/Time | To specify pertinent dates and times. | 5 of 5 |
| OID | Order Information Detail | To specify order information detail. | 5 of 5 |
| N3 | Party Location | To specify the location of the named party. | 4 of 5 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 4 of 5 |
| L11 | Business Instructions and Reference Number | To specify instructions in this business relationship or a reference number. | 4 of 5 |
| USI | Unitized Shipment Information | To specify the quantity, number of pallet spaces and stackability of unitized units. | 3 of 5 |
Stacksync connects EDI documents such as the X12 753 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 753 mapping and validation
X12 753 Request for Routing Instructions is used when a supplier needs shipping instructions. Preserve routing request, purchase order and ready-to-ship date so the routing request 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 request routing request, purchase order and ready-to-ship date |
|
| Update the receiving system | Processing the routing request ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the routing request 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 754 Routing Instructions
routing instruction: routing details are issued in response to a shipment need.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
- 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 a supplier needs shipping instructions. Name the operational owner of the routing request and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map routing request, purchase order and ready-to-ship date. 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 request 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 request processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 753 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic routing request 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 request without processing it twice.
Document structure
X12 753 Request for Routing Instructions at the element level
The X12 753 reference contains 20 segment entries and 70 data elements; 37 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 20
- Data elements
- 70
- Mandatory elements
- 37
| Segment | Elements | Mandatory |
|---|---|---|
| BGN | 5 | 3 |
| PER | 4 | 1 |
| N1 | 4 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| LX | 1 | 1 |
| USI | 3 | 2 |
- Transaction Set Purpose Code
- Reference Identification
- Date
- Contact Function Code
- Entity Identifier Code
- Name
- Address Information
- Assigned Number
Find your trading partner for X12 753
4 partners, 5 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 753 Request for Routing Instructions appears in this catalog
The largest groups of classified 753 catalog entries are in retail, e-commerce & marketplaces and apparel & footwear.
By industry
- retail 2 channels
- e-commerce & marketplaces 2 channels
- apparel & footwear 1 channel
FAQ
EDI 753 questions
What is an EDI 753?
EDI 753 is the X12 Request for Routing Instructions transaction set. Trading partners use it when a supplier needs shipping instructions. It carries the data for the routing request, and your system matches it on routing request, purchase order and ready-to-ship date.
Who sends an EDI 753 and who receives it?
A supplier or vendor sends the 753 to the retailer or the buyer's transportation organization, which answers with an EDI 754 Routing Instructions. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 753 sent?
A supplier has an order picked and ready to ship on a collect or buyer-managed freight program and needs the retailer to assign the carrier before booking pickup. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 753?
Across 5 partner document references listed here, the business segments that appear most often include BGN (Beginning Segment), PER (Administrative Communications Contact), N1 (Party Identification), LX (Transaction Set Line Number), G62 (Date/Time), OID (Order Information Detail). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 753 and EDI 754?
The 753 carries the routing request and is used when a supplier needs shipping instructions. The 754 carries the routing instruction and is used when routing details are issued in response to a shipment need.
What should I map for X12 753?
Start with routing request, purchase order and ready-to-ship date and the target routing request. 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 753 error handling?
Test an order split into two pickups and keep each routing request distinct. Handle a changed ready date while the original routing request is still open. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 753?
The directory on this page links 4 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.
