X12 753 Retail Request for Routing Instructions
This X12 Transaction Set contains the format and establishes the data contents of the Request for Routing Instructions Transaction Set (753) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to request routing instructions and provide general information about merchandise that is ready to be shipped.
- ~ 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
- RF
- Request for Routing Instructions (753)
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).
- 753
- Request for 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:
BGN0075555202208111200CT74231~
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
Vendor's unique Routing Request ID (RRID). This value needs to be unique for every 753. If you are sending a replacement 753, please use the same RRID as on the original 753.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BGN03 is the transaction set date.
Date Request 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 Request 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.
Please provide the time zone code corresponding to the time provided in the BGN04.
All valid standard codes are used.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example:
PERICVendor contactTE2065555555~
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Please provide a contact point for issues related to this request.
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:
N1SFVendor ship-from158001234~ (vendor SAN code)
N1SFVendor ship-fromZZ2811234-4567~ (Amazon-generated warehouse code from Vendor Central)
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
Ship-from ID qualifier code. For a SAN, use "15". For a value generated from Vendor Central, use "ZZ".
- 15
- Standard Address Number (SAN)
- ZZ
- Mutually Defined
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.
If your company has a registered SAN code representing your warehouse location, use that. If not, you must use an address ID generated via Vendor Central.
Please see the document titled "Address ID from Vendor Central" in the 753 specifications package for further information.
Additional Name Information
To specify additional names
Example:
N2Additional vendor name infoAdditional vendor name info~
Party Location
To specify the location of the named party
Example:
N3Additional vendor location infoAdditional vendor location info~
Geographic Location
To specify the geographic place of the named party
Example:
N4FontanaCA92337US~
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
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-to location.
Segment Usage:
Only one ship-to location is allowed per 753.
Example:
N1STAmazon.com.ksdc, LLC92TUL1~
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 15
- Standard Address Number (SAN)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Either an Amazon FC Code (qualifier 92) or a SAN(qualifier 15) is required in the Ship To.
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Segment Usage:
This segment MUST be used if non-standard pallets are being shipped.
Example:
L11222333444BM*PALLET: OVERSIZE H=5,W=6,L=10,U=ft PALLET:STACKED 3
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Bill Of Lading number for Shipment
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
A free-form description to clarify the related data elements and their content
Description MUST contain information about any non-standard pallets
PALLET: OVERSIZE H=h,W=w,L=l,U=u (h = height, w = width, l = length, u = dimension unit of measurement)
PALLET: STACKED n (n = number of pallets in stack)
Formatting Notes: Allowed dimension units of measurement:
ft
in
meter
yard
Date/Time
To specify pertinent dates and times
Segment Usage:
Use this segment to specify the earliest pick-up date for the shipment.
Example:
G62EP20220813~
Code specifying type of date
Earliest Pickup Date (EP) is required.
- EP
- Earliest Pickup Date
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)
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
Unitized Shipment Information
To specify the quantity, number of pallet spaces and stackability of unitized units
Example:
USI1PLTN~
USI15CTN~
USI7*PKG~
Numeric value of quantity
Total Quantity of Shipment units. This is a required field.
. If PLT qualifier is used in the USI02, this field is the number of pallets.
. If CTN or PKG qualifier is used in the USI02, this field is the number of cartons or packages.
Code for packaging form of the lading quantity
- USI02 defines the quantity in USI01.
. If cartons are wrapped on pallet, skid, or sheet then PLT code MUST be used, with the USI01 quantity referring to the number of pallets.
. If cartons are loose or small parcel, then CTN or PKGMUST be used, with the USI01 quantity referring to the total number of cartons or packages (sum of OID05 elements).
- CTN
- Carton
- PKG
- Package
- PLT
- Pallet
Code indicating a Yes or No condition or response
- USI03 identifies whether the unitized handling units are stackable. A "Y" indicates the unitized handling units are stackable; an "N" indicates the unitized handling units are not stackable.
If possible, provide a response via the USI03 element when shipping pallets. If the USI03 is omitted and you are shipping pallets, Amazon will default to "not stackable."
- N
- No
- Y
- Yes
Order Information Detail
To specify order information detail
- The 0210 loop is used to specify the quantities ready to ship for each purchase order.
Example:
OID1A2B3C4NCTN43L450E*74~
Identifying number for Purchase Order assigned by the orderer/purchaser
Amazon Purchase Order MUST be provided.
Formatting Notes: The first character is a digit, followed by six alphanumeric characters (without the digit zero to eliminate confusion), followed by an alphabetic character.
Numeric value of quantity
Quantity of Cartons or Packages for the given Purchase Order.
Code specifying the weight unit
Weight Unit codes must be consistent across the entire 753 document.
- G
- Grams
- K
- Kilograms
- L
- Pounds
- O
- Ounces
Numeric value of weight
If weight is only known for Shipment as a whole, then provide on first OID segment.
Code identifying the volume unit
Volume Unit codes must be consistent across the entire 753 document.
- E
- Cubic Feet
- N
- Cubic Inches
- X
- Cubic Meters
Value of volumetric measure
If volume is only known for Shipment as a whole, then provide on first OID segment.
Commodity Classification
To specify freight commodity code and freight classification
Example:
CMCDry Goods77.5~
Code describing a commodity or group of commodities
- CMC01 is the National Motor Freight Classification Commodity Code.
Fixed list of options
- Biological Materials
- Dry Goods
- Frozen Goods
- Hazardous Materials
- Magnetic Goods
- Refrigerated Goods
- Separate from Dry Goods
- Separate from Magnetic Goods
- Special Goods
- Special IT Shipments
- Unspecified
Code indicating generalized classification that applies to one or more items in the shipment, i.e., class 70, 77.5, etc.
- CMC02 is the Freight Class Code published in the National Motor Freight Classification.
NMFC Classification Code
Formatting Notes: This code must be a single number and cannot be a range.
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 Non Standard Pallets
GS*RF*SENDERID*AMAZON*20220813*0734*000000009*X*005010~
ST*753*000000002~
BGN*00*220801126*20220813*0719~
PER*IC*VendorContactName*TE*502333444~
N1*SF*ShipFromLocation*15*SANnumber~
N3*Street address~
N4*City*ST*Zip Code*US~
LX*1~
N1*ST*AMAZON.COM.NVDC, INC.*92*PHX6~
L11*222333444*BM*PALLET:OVERSIZE H=5,W=6,L=10,U=ft PALLET:STACKED 3~
G62*EP*20220814*0*1234*PS~
USI*3*PLT*N~
OID**PONumber1**CTN*3*L*60*E*50~
CMC*Dry Goods*70.5~
OID**PONumber2**CTN*3*L*10*E*10~
CMC*Dry Goods*70.5~
OID**PONumber3**CTN*3*L*10*E*5~
CMC*Dry Goods*70.5~
SE*14*000000002~
GE*1*000000009~
IEA*1*000000009~
Retail Standard Pallets
GS*RF*SENDERID*AMAZON*20220813*0734*000000008*X*005010~
ST*753*000000002~
BGN*00*287311926*20220813*0719~
PER*IC*VendorContactName*TE*502333444~
N1*SF*ShipFromLocation*15*SANnumber~
N3*Street address~
N4*City*ST*Zip Code*US~
LX*1~
N1*ST*AMAZON.COM.NVDC, INC.*92*PHX5~
G62*EP*20220814*0*1234*PS~
USI*16*PLT*N~
OID**PONumber1**CTN*544*L*10057*E*1500~
CMC*Dry Goods*77.5~
OID**PONumber2**CTN*0*L*0*E*0~
CMC*Dry Goods*77.5~
OID**PONumber3**CTN*0*L*0*E*0~
CMC*Dry Goods*77.5~
OID**PONumber4**CTN*0*L*0*E*0~
CMC*Dry Goods*77.5~
SE*14*000000002~
GE*1*000000008~
IEA*1*000000008~
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.