X12
Inbound

Amazon X12 754 Routing Instructions

Amazon Retail - Canada
The EDI 754 is Amazon's response to a routing request, providing the assigned carrier, pickup date, and delivery instructions. Suppliers must use the specified carrier and schedule to remain compliant.
18segments
4loops
8mandatory

Schema Reference

18 segments · X12 754 Routing Instructions

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Interchange Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
ST03 Implementation Convention Reference
O AN 1-35
BGN Beginning Segment
Mandatory Max: 1
BGN01 Transaction Set Purpose Code
M ID 2-2
BGN02 Reference Identification
M AN 1-50
BGN03 Date
M DT 8-8
BGN04 Time
C TM 4-8
BGN05 Time Code
O ID 2-2
BGN06 Reference Identification
O AN 1-50
PER Administrative Communications Contact
Optional Max: 5
PER01 Contact Function Code
M ID 2-2
PER02 Name
O AN 1-60
PER03 Communication Number Qualifier
C ID 2-2
PER04 Communication Number
C AN 1-256
PER05 Communication Number Qualifier
C ID 2-2
PER06 Communication Number
C AN 1-256
N1 Loop Repeat: 5
N1 Party Identification
Mandatory Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
N3 Party Location
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
C ID 2-2
N403 Postal Code
O ID 3-15
N404 Country Code
C ID 2-3
N405 Location Qualifier
C ID 1-2
N406 Location Identifier
O AN 1-30
N407 Country Subdivision Code
C ID 1-3
LX Loop Repeat: 9,999
LX Transaction Set Line Number
Mandatory Max: 1
LX01 Assigned Number
M N0 1-6
L11 Business Instructions and Reference Number
Optional Max: 5
L1101 Reference Identification
C AN 1-50
L1102 Reference Identification Qualifier
C ID 2-3
L1103 Description
C AN 1-80
OID Order Information Detail
OID02 Purchase Order Number
C AN 1-22
G62 Date/Time
Optional Max: 2
G6201 Date Qualifier
C ID 2-2
G6202 Date
C DT 8-8
G6203 Time Qualifier
C ID 1-2
G6204 Time
C TM 4-8
G6205 Time Code
O ID 2-2
QTY Loop Repeat: 25
QTY Quantity Information
Optional Max: 1
QTY01 Quantity Qualifier
M ID 2-2
QTY02 Quantity
C R 1-15
QTY04 Free-form Information
C AN 1-30
AT9 Trailer or Container Dimension and Weight
Optional Max: 1
AT904 Weight Qualifier
C ID 1-2
AT905 Weight Unit Code
C ID 1-1
AT906 Weight
C R 1-10
AT907 Volume Unit Qualifier
C ID 1-1
AT908 Volume
C R 1-8
N1 Loop Repeat: 5
N1 Party Identification
Mandatory Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
N3 Party Location
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
C ID 2-2
N403 Postal Code
O ID 3-15
N404 Country Code
C ID 2-3
N405 Location Qualifier
C ID 1-2
N406 Location Identifier
O AN 1-30
N407 Country Subdivision Code
C ID 1-3
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Amazon EDI 754

Stacksync validates, transforms, and delivers your 754 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync receives Amazon 754 Routing Instructions and updates your shipping workflow with the assigned carrier, pickup window, and delivery requirements — so your warehouse team has everything they need.

Amazon EDI 754 FAQ

Common questions about 754 Routing Instructions transactions with Amazon.

What is a Amazon EDI 754 Routing Instructions?

The Amazon EDI 754 Routing Instructions is an X12 transaction set used to exchange Routing Instructions data electronically between trading partners. As a inbound document, it standardizes the communication of Routing Instructions information between Amazon and their suppliers, carriers, or partners. Stacksync processes Amazon 754 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Amazon's requirements in real time.

What is a Amazon EDI 754 Routing Instructions?

The Amazon EDI 754 Routing Instructions is an X12 transaction set used to exchange Routing Instructions data electronically between trading partners. As a inbound document, it standardizes the communication of Routing Instructions information between Amazon and their suppliers, carriers, or partners. Stacksync processes Amazon 754 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Amazon's requirements in real time.

How does Stacksync automate Amazon EDI 754 Routing Instructions transactions?

Stacksync handles Amazon EDI 754 Routing Instructions transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 754 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Amazon 754 document meets their specific formatting requirements before transmission or after receipt.

How does Stacksync automate Amazon EDI 754 Routing Instructions transactions?

Stacksync handles Amazon EDI 754 Routing Instructions transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 754 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Amazon 754 document meets their specific formatting requirements before transmission or after receipt.

What are common Amazon EDI 754 errors and how do I fix them?

Common errors in Amazon EDI 754 Routing Instructions transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Amazon 754 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

What are common Amazon EDI 754 errors and how do I fix them?

Common errors in Amazon EDI 754 Routing Instructions transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Amazon 754 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up Amazon EDI 754 with Stacksync?

Most Amazon EDI 754 Routing Instructions integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Amazon's 754 format and your system, running test transactions, and completing Amazon's certification process if required. Stacksync includes pre-built mappings for Amazon's most common 754 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

How long does it take to set up Amazon EDI 754 with Stacksync?

Most Amazon EDI 754 Routing Instructions integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Amazon's 754 format and your system, running test transactions, and completing Amazon's certification process if required. Stacksync includes pre-built mappings for Amazon's most common 754 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Amazon EDI 754 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Amazon EDI 754 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Amazon updates their 754 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Can I customize Amazon EDI 754 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Amazon EDI 754 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Amazon updates their 754 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Amazon EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding