X12 754 Retail Routing Instructions
This X12 Transaction Set contains the format and establishes the data contents of the Routing Instructions Transaction Set (754) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to communicate routing instructions to a supplier for a specific shipment. It can be used also to respond to a Request for Routing Instructions Transaction Set (753).
- ~ Segment
- * Element
- > Component
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code identifying the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
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
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- RG
- Routing Instructions (754)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 754
- Routing Instructions
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment
To indicate the beginning of a transaction set
Example:
BGN0011225520220812103006UT5005337450~
Code identifying purpose of transaction set
- 00
- Original
- 05
- Replace
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
This will be the unique routing request ID that you sent to Amazon in the 753 in element BGN02.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BGN03 is the transaction set date.
Date the 754 was created.
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
- BGN04 is the transaction set time.
Time the 754 was created.
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
- BGN05 is the transaction set time qualifier.
UT = UTC universal time.
- UT
- Universal Time Coordinate
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.
This is the Amazon Reference Number (ARN). The ARN is Amazon's primary reference for this shipment. Please return this ARN on the corresponding ASN (REF*BX), and please reference the ARN in any communications with Amazon about this Routing Instructions document.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example:
PERC1Contact nameTE206-555-5555EMname@carrier.com~
PERRERNO1 ClerkTE206-555-5555EMRNO1clerk@amazon.com~
PERSHShipper contactTE425-555-5555EMname@shipping.com~
Code identifying the major duty or responsibility of the person or group named
- C1
- Carrier Contact
- RE
- Receiving Contact
- SH
- Shipper Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Party Identification
To identify a party by type of organization, name, and code
- One iteration of the N1 segment must be used to identify the ship-from location.
Example:
N1CAACME SHIPPING SERVICES2SCAC~
N1SFVENDORCODE~
Code identifying an organizational entity, a physical location, property or an individual
- CA
- Carrier
Code designating the system/method of code structure used for Identification Code (67)
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Party Identification
To identify a party by type of organization, name, and code
- One iteration of the N1 segment must be used to identify the ship-from location.
Example:
N1CAACME SHIPPING SERVICES2SCAC~
N1SFVENDORCODE~
Party Location
To specify the location of the named party
Example:
N3Address informationAddress information~
Geographic Location
To specify the geographic place of the named party
Example:
N4CityStatePostal codeCountry code~
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Detail
Transaction Set Line Number
To reference a line number in a transaction set
Example:
LX*1~
Number assigned for differentiation within a transaction set
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Example:
L111239949654F8*Load Type: TL Load Value: LOW~
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- F8
- Original Reference Number
A free-form description to clarify the related data elements and their content
Shipment information:
Load Type: PACKAGE/ TL/ LTL
Load Value: LOW/ MEDIUM/ HIGH
Order Information Detail
To specify order information detail
Example:
OID**AMAZON PO NUMBER~
Identifying number for Purchase Order assigned by the orderer/purchaser
Amazon Purchase Order Number
Requested Ship Date/Pickup Date
To specify pertinent dates and times
Example:
G626920220812U120000LT~
G6210*20220811~
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
CCYYMMDD
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
HHMMSS
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
"LT" for local time will be sent.
- LT
- Local Time
Scheduled Pickup Date
To specify pertinent dates and times
Example:
G626920220812U120000LT~
G6210*20220811~
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
CCYYMMDD
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
HHMMSS
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
"LT" for local time will be sent.
- LT
- Local Time
Quantity Information
To specify quantity information
Example:
QTYH92Pallets~
QTYH95Stacked Pallets~
Numeric value of quantity
The quantity corresponding to the shipment unit in QTY04. If either one is present, the other element is required.
Free-form information
- QTY04 is used when the quantity is non-numeric.
- Cartons
- Pallets
- Stacked Pallets
Trailer or Container Dimension and Weight
To specify trailer or container dimensions
Example:
AT9*A3L*12716.0E2704.0~
Code defining the type of weight
Shippers Declared Weight
- A3
- Shippers Weight
Numeric value of weight
- AT906 is the weight of the trailer or container. It is the tare weight of the trailer or container.
Only one weight will be sent representing the declared weight for the entire shipment sent by the Shipper in the 753.
Value of volumetric measure
- AT908 is the volumetric capacity of the trailer or container.
Only one volume will be sent representing the declared volume for the entire shipment sent by the Shipper in the 753.
Party Identification
To identify a party by type of organization, name, and code
Example:
N1STAMAZON.COM~
Party Location
To specify the location of the named party
Example:
N3*1910 E Central Ave~
Geographic Location
To specify the geographic place of the named party
Example:
N4San BernardinoCA92408US~
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Retail
GS*RG*AMAZON*SENDERID*20220811*2338*2888*X*005010~
ST*754*0001~
BGN*00*1122511*20220811*103006*UT*5005337470~
PER*C1*CarrierContact*TE*206-555-5555*EM*carrier@carrier.com~
PER*RE*RNO1Clerk*TE*206-555-5555*EM*RN01@amazon.com~
PER*SH*ShipperContact*TE*425-555-5555*EM*shipper@shipper.com~
N1*CA*FEDERAL EXPRESS CORP*2*FDE~
N1*SF*VendorCode~
N3*605 5th Ave N~
N4*Seattle*WA*98104*US~
LX*1~
L11*1239949670*F8*Load Type:TL Load Value:LOW~
OID**POnumber1~
OID**POnumber2~
OID**POnumber3~
G62*69*20220812*U*120000*LT~
G62*10*20220811~
QTY*H9*11**Pallets~
QTY*H9*5**Stacked Pallets~
AT9****A3*L*12716.0*E*2704.0~
N1*ST*AMAZON.COM~
N3*1600 EAST NEWLANDS DRIVE~
N4*FERNLEY*NV*89408*US~
SE*23*0001~
GE*1*2888~
IEA*1*000002888~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.