**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.
Direct Fulfillment X12 850
Order Fulfillment Request
Version: 2.3 Final
Company: | Amazon |
Created: | 1/12/2015 |
Modified: | 12/6/2023 |
850 Purchase Order
Functional Group=PO
Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
Not Defined
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
| ISA | Interchange Control Header | M | 1 |
|
| Must use |
| GS | Functional Group Header | M | 1 |
|
| Must use |
Heading
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
010 | ST | Transaction Set Header | M | 1 |
|
| Must use |
020 | BEG | Beginning Segment for Purchase Order | M | 1 |
|
| Must use |
040 | CUR | Currency | M | 1 |
|
| Must use |
050 | REF | Reference Identification - Customer Order Number | M | >1 |
|
| Must use |
050 | REF | Reference Identification - Web-Site Code | M | >1 |
|
| Must use |
150 | DTM | Date/Time Reference | M | 10 |
|
| Must use |
150 | DTM | Date/Time Reference | M | 10 |
|
| Must use |
| LOOP ID - N9 |
|
|
| 1000 |
|
|
295 | N9 | Reference Identification | M | 1 |
|
| Must use |
300 | MSG | Message Text | M | 1000 |
|
| Must use |
| LOOP ID - N1 |
|
|
| 1 |
|
|
310 | N1 | Name - Amazon Bill To Location | M | 1 |
|
| Must use |
| LOOP ID - N1 |
|
|
| 200 |
|
|
310 | N1 | Name - Vendor Warehouse | M | 1 |
|
| Used |
| LOOP ID - N1 |
|
|
| 1 |
|
|
310 | N1 | Name - Ship To Party | M | 1 |
|
| Must use |
320 | N2 | Additional Name Information | O | 2 |
|
| Used |
330 | N3 | Address Information | M | 2 |
|
| Must use |
340 | N4 | Geographic Location | M | >1 |
|
| Must use |
390 | TD5 | Carrier Details (Routing Sequence/Transit Time) | M | 1 |
|
| Must use |
| LOOP ID - N1 |
|
|
| 1 |
|
|
310 | N1 | Name - Customer Bill To Party | O | 1 |
|
| Used |
320 | N2 | Additional Name Information | O | 2 |
|
| Used |
330 | N3 | Address Information | O | 2 |
|
| Used |
340 | N4 | Geographic Location | O | >1 |
|
| Used |
360 | PER | Administrative Communications Contact | O | >1 |
|
| Used |
Detail
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
| LOOP ID - PO1 |
|
|
| 100000 | N2/010L |
|
010 | PO1 | Baseline Item Data | M | 1 |
| N2/010 | Must use |
| LOOP ID - CTP |
|
|
| >1 |
|
|
040 | CTP | Pricing Information - Price to Customer | O | 1 |
|
| Used |
289 | MSG | Message Text - Item Description | O | >1 |
|
| Used |
289 | MSG | Message Text - Gift Message | C | >1 |
|
| Dependent |
Summary
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
| LOOP ID - CTT |
|
|
| 1 | N3/010L |
|
010 | CTT | Transaction Totals | M | 1 |
| N3/010 | Must use |
030 | SE | Transaction Set Trailer | M | 1 |
|
| Must use |
Not Defined
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
| GE | Functional Group Trailer | M | 1 |
|
| Must use |
| IEA | Interchange Control Trailer | M | 1 |
|
| Must use |
ISA Interchange Control Header | ||||
Pos: | Max: 1 | Loop: N/A | Not Defined - Mandatory | Elements: 16 |
User Option (Usage): Must use | ||||
Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control segments
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
ISA01 | I01 | Authorization Information Qualifier Notes: Always "00" | M | ID | 2/2 |
ISA02 | I02 | Authorization Information Notes: Always 10 spaces | M | AN | 10/10 |
ISA03 | I03 | Security Information Qualifier Notes: Always "00" | M | ID | 2/2 |
ISA04 | I04 | Security Information Notes: Always 10 spaces | M | AN | 10/10 |
ISA05 | I05 | Interchange ID Qualifier Notes: Always "ZZ" | M | ID | 2/2 |
ISA06 | I06 | Interchange Sender ID Notes: Always "AMAZONDS" | M | AN | 15/15 |
ISA07 | I05 | Interchange ID Qualifier Notes: This will be the Vendor's ISA ID Qualifier | M | ID | 2/2 |
ISA08 | I07 | Interchange Receiver ID Notes: This field will contain the vendor's receiver ISA ID. | M | AN | 15/15 |
ISA09 | I08 | Interchange Date Notes: Interchange Date (Format: YYMMDD). Expressed in UTC format. | M | DT | 6/6 |
ISA10 | I09 | Interchange Time Notes: Interchange Time | M | TM | 4/4 |
ISA11 | I10 | Interchange Control Standards Identifier Notes: Always "U" | M | ID | 1/1 |
ISA12 | I11 | Interchange Control Version Number Notes: Always "00401" | M | ID | 5/5 |
ISA13 | I12 | Interchange Control Number Notes: A unique control number assigned by the interchange sender | M | N0 | 9/9 |
ISA14 | I13 | Acknowledgment Requested Notes: Always "1" | M | ID | 1/1 |
ISA15 | I14 | Usage Indicator | M | ID | 1/1 |
ISA16 | I15 | Component Element Separator Notes: Always ">" | M |
| 1/1 |
Code Values:
Code | Name |
00 | No Authorization Information Present (No Meaningful Information in I02) |
ZZ | Mutually Defined |
00401 | Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997 |
1 | Interchange Acknowledgment Requested |
P | Production Data |
Segment Usage: Please note: Only one ISA/ IEA loop is allowed per message.
Example: ISA*00* *00* *ZZ*AMAZONDS *ZZ*RECEIVERID *231205*1310*U*00401*000000043*1*P*>
GS Functional Group Header | ||||
Pos: | Max: 1 | Loop: N/A | Not Defined - Mandatory | Elements: 8 |
User Option (Usage): Must use | ||||
Purpose: To indicate the beginning of a functional group and to provide control information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
GS01 | 479 | Functional Identifier Code Notes: Always "PO" | M | ID | 2/2 |
GS02 | 142 | Application Sender's Code Notes: Always "AMAZONDS" | M | AN | 2/15 |
GS03 | 124 | Application Receiver's Code Notes: This is the vendor's GS ID. | M | AN | 2/15 |
GS04 | 373 | Date Notes: Interchange Date | M | DT | 8/8 |
GS05 | 337 | Time Notes: Interchange Time | M | TM | 4/8 |
GS06 | 28 | Group Control Number Notes: Group Control Number assigned by sender | M | N0 | 1/9 |
GS07 | 455 | Responsible Agency Code Notes: Always "X" | M | ID | 1/2 |
GS08 | 480 | Version / Release / Industry Identifier Code Notes: Always "004010" | M | AN | 1/12 |
Code Values:
Code | Name |
PO | Purchase Order (850) |
X | Accredited Standards Committee X12 |
004010 | Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997 |
Segment Usage: Only one GS/GE loop is allowed per transmission.
Example: GS*PO*AMAZONDS*RECEIVERID*20231205*131004*43*X*004010
ST Transaction Set Header | ||||
Pos: 010 | Max: 1 | Loop: N/A | Heading - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Purpose: To indicate the start of a transaction set and to assign a control number
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
ST01 | 143 | Transaction Set Identifier Code Notes: Always "850" | M | ID | 3/3 |
ST02 | 329 | Transaction Set Control Number Notes: Transaction Control Number assigned by sender | M | AN | 4/9 |
Code Values:
Code | Name |
850 | Purchase Order |
Segment Usage: Multiple ST/SE loops are only allowed if they are for the same message type.
Example: ST*850*0010
BEG Beginning Segment for Purchase Order | ||||
Pos: 020 | Max: 1 | Loop: N/A | Heading - Mandatory | Elements: 4 |
User Option (Usage): Must use | ||||
Purpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
BEG01 | 353 | Transaction Set Purpose Code Notes: Always "00" | M | ID | 2/2 |
BEG02 | 92 | Purchase Order Type Code | M | ID | 2/2 |
BEG03 | 324 | Purchase Order Number Notes: This will be the Amazon encrypted Shipment ID (PO number), which is case sensitive. This number is unique - if a duplicate Shipment ID is ever received it should be rejected via a corresponding OFR (855). Format: AlphaNumeric. Example: DjntsVrFN (Note: Dj2sV3fN is a different Shipment ID than Dj2Sv3FN). This number should appear on the Amazon-branded packing slip and must be returned to Amazon in the OFR (855), ASN (856), and INV (810) messages. | M | AN | 1/22 |
BEG05 | 373 | Date Notes: This is the Order Date. Format: CCYYMMDD. Expressed in UTC format. This customer's order date should be included on the packing slip. | M | DT | 8/8 |
Code Values:
Code | Name |
00 | Original |
DS | Dropship |
SS | Supply or Service Order |
ZZ | Mutually Defined |
Example: BEG*00*DS*TesT0008596**20231205
CUR Currency | ||||
Pos: 040 | Max: 1 | Loop: N/A | Heading - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
CUR01 | 98 | Entity Identifier Code Notes: Always "BT" | M | ID | 2/3 |
CUR02 | 100 | Currency Code Notes: Valid ISO currency code. | M | ID | 3/3 |
Code Values:
Code | Name |
BT | Bill-to-Party |
Segment Usage: This segment provides the currency code for the order.
Example: CUR*BT*USD | CUR*BT*CAD | CUR*BT*EUR | CUR*BT*JPY | CUR*BT*GBP
REF Reference Identification - Customer Order Number | ||||
Pos: 050 | Max: >1 | Loop: N/A | Heading - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Purpose: To specify identifying information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
REF01 | 128 | Reference Identification Qualifier Notes: Always "OQ" | M | ID | 2/3 |
REF02 | 127 | Reference Identification Notes: This will be the Amazon.com 19 digit Customer Order Number. Format: Numeric 3-7-7. Example: 123-1234567-1234567. *Dashes will be included. This number is NOT unique and may be used with more than one shipment. This number needs to be included on the packing slip and must be returned to Amazon in the INV (810) message. | M | AN | 1/30 |
Code Values:
Code | Name |
OQ | Order Number |
Segment Usage: This segment is used to provide the Amazon.com 19 digit Customer Order Number.
Example: REF*OQ*100-0000000-3091800
REF Reference Identification - Web-Site Code | ||||
Pos: 050 | Max: >1 | Loop: N/A | Heading - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Purpose: To specify identifying information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
REF01 | 128 | Reference Identification Qualifier Notes: Always "ST" | M | ID | 2/3 |
REF02 | 127 | Reference Identification Notes: This is an internal Amazon.com code representing the website where the customer order was placed. This value does not need to be returned to Amazon in any other messages. | M | AN | 1/30 |
Code Values:
Code | Name |
ST | Store Number |
Segment Usage: This segment provides an internal Amazon code specifying the website on which the order was placed.
Example: REF*ST*1
DTM Date/Time Reference (Requested Ship) | ||||
Pos: 150 | Max: 10 | Loop: N/A | Heading - Mandatory | Elements: 4 |
User Option (Usage): Must use | ||||
Purpose: To specify pertinent dates and times
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
DTM01 | 374 | Date/Time Qualifier | M | ID | 3/3 |
DTM02 | 373 | Date Notes: Date expressed CCYYMMDD | M | DT | 8/8 |
DTM03 | 337 | Time Notes: Time expressed HHMM | M | TM | 4/8 |
DTM04 | 623 | Time Code Notes: Always 'GM' | M | ID | 2/2 |
Code Values:
Code | Name |
010 | Requested Ship |
GM | Greenwich Mean Time |
Segment Usage: Date/Time by which the order is expected to be shipped. Also known as Requested Ship date (RSD) or Expected Ship date (ExSD). Time is always expressed in Greenwich Mean Time.
Example: DTM*010*20231225*1200*GM
DTM Date/Time Reference (Delivery Requested) | ||||
Pos: 150 | Max: 10 | Loop: N/A | Heading - Mandatory | Elements: 4 |
User Option (Usage): Must use | ||||
Purpose: To specify pertinent dates and times
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
DTM01 | 374 | Date/Time Qualifier | M | ID | 3/3 |
DTM02 | 373 | Date Notes: Date expressed CCYYMMDD | M | DT | 8/8 |
DTM03 | 337 | Time Notes: Time expressed HHMM | M | TM | 4/8 |
DTM04 | 623 | Time Code Notes: Always 'GM' | M | ID | 2/2 |
Code Values:
Code | Name |
002 | Delivery Requested |
GM | Greenwich Mean Time |
Segment Usage: Date/Time by which the order is expected to be delivered to the customer. Also known as Delivery Requested date or Promised Delivery date (PDD). Time is always expressed in Greenwich Mean Time.
Example: DTM*002*20231227*1200*GM
Loop Reference Identification - Order Status Message
Pos: 295 Repeat: 1000 Loop: N9 Mandatory
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
295 | N9 | Reference Identification | M | 1 |
| Must use |
300 | MSG | Message Text | M | 1000 |
| Must use |
N9 Reference Identification | ||||
Pos: 295 | Max: 1 | Loop: N9 | Heading - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Loop Path: N9
Purpose: To transmit identifying information as specified by the Reference Identification Qualifier
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N901 | 128 | Reference Identification Qualifier Notes: Always "ZZ" | M | ID | 2/3 |
N902 | 127 | Reference Identification Notes: Code Representing Order Status Message Number (e.g. 01,02,03,04,05,06,07). Explanatory messages for each Order Status Message Number is in the MSG segment. | X | AN | 1/30 |
Code Values:
Code | Name |
ZZ | Mutually Defined |
Example: N9*ZZ*01
MSG Message Text | ||||
Pos: 300 | Max: 1000 | Loop: N9 | Heading - Mandatory | Elements: 1 |
User Option (Usage): Must use | ||||
Loop Path: N9
Purpose: To provide a free-form format that allows the transmission of text information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
MSG01 | 933 | Free-Form Message Text Notes: Text of Order Status Message, related to Order Status Message Code. The most current order status message will be provided by Amazon.com. 01: This shipment completes your order. 02: We've sent this part of your order to ensure quicker service. The other items will ship separately at no additional shipping cost. 03: As you requested, we've sent this part of your order to ensure quicker service. The other items will ship separately. 04: This shipment represents part of your gift. The other portion of your gift is shipping separately. 05: We hope you enjoy your gift, and we'd love to see you soon at www.amazon.com. 06: For detailed information about your orders, please visit Your Account... 07: Visit http://www.amazon.com/returns to return any item within 30 days for a full refund. This will appear on the Amazon-branded packing slip. | M | AN | 1/264 |
Example: MSG*This shipment completes your order.
Loop Name - Amazon Bill To Location
Pos: 310 Repeat: 1 Loop: N1 Mandatory
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
310 | N1 | Name - Amazon Bill To Location | M | 1 |
| Must use |
N1 Name - Amazon Bill To Location | ||||
Pos: 310 | Max: 1 | Loop: N1 | Heading - Mandatory | Elements: 4 |
User Option (Usage): Must use | ||||
Loop Path: N1
Purpose: To identify a party by type of organization, name, and code
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N101 | 98 | Entity Identifier Code Notes: Always "BT" | M | ID | 2/3 |
N102 | 93 | Name Notes: This will be the name of the Amazon location to bill for goods and services. This may vary by ship-from warehouse. May vary by order. (e.g. Amazon.com.kydc.Inc) | M | AN | 1/60 |
N103 | 66 | Identification Code Qualifier Notes: Always "92" | M | ID | 1/2 |
N104 | 67 | Identification Code Notes: Amazon location code to bill for goods and services. Possible Values: KYDC = Amazon.com.kydc, Inc | TNDS = Fulfill.tnds, Inc | NVDC = Amazon.com.nvdc, Inc | ASI = Amazon.com Services, Inc. | M | AN | 2/80 |
Code Values:
Code | Name |
BT | Bill-to-Party |
92 | Assigned by Buyer or Buyer's Agent |
Segment Usage: Always "BT"
Example: N1*BT*Amazon.com.kydc,Inc.*92*KYDC
Loop Name - Vendor Warehouse
Pos: 310 Repeat: 200 Loop: N1 Mandatory
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
310 | N1 | Name - Vendor Warehouse | M | 1 |
| Used |
N1 Name - Vendor Warehouse | ||||
Pos: 310 | Max: 1 | Loop: N1 | Heading - Mandatory | Elements: 4 |
User Option (Usage): Used | ||||
Loop Path: N1
Purpose: To identify a party by type of organization, name, and code
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N101 | 98 | Entity Identifier Code Notes: Always "SF". Ship From. | M | ID | 2/3 |
N102 | 93 | Name Notes: This will be the Amazon code representing the warehouse from which the order should ship. This is usually a four character alpha code (e.g. ABCD). | M | AN | 1/60 |
N103 | 66 | Identification Code Qualifier Notes: Always "92" | M | ID | 1/2 |
N104 | 67 | Identification Code Notes: This will be the Amazon code representing the vendor warehouse from which the order should ship. This is usually a four character alpha code (e.g. ABCD). This will be the same code as used in the N102 element. | M | AN | 2/80 |
Code Values:
Code | Name |
SF | Ship From |
92 | Assigned by Buyer or Buyer's Agent |
Segment Usage: This segment indicates the vendor's warehouse from which the order should ship.
Example: N1*SF*ABCD*92*ABCD
Loop Name - Ship To Party
Pos: 310 Repeat: 1 Loop: N1 Mandatory
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
310 | N1 | Name - Ship To Party | M | 1 |
| Must use |
320 | N2 | Additional Name Information | O | 2 |
| Used |
330 | N3 | Address Information | M | 2 |
| Must use |
340 | N4 | Geographic Location | M | >1 |
| Must use |
390 | TD5 | Carrier Details (Routing Sequence/Transit Time) | M | 1 |
| Must use |
N1 Name - Ship To Party | ||||
Pos: 310 | Max: 1 | Loop: N1 | Heading - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Loop Path: N1
Purpose: To identify a party by type of organization, name, and code
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N101 | 98 | Entity Identifier Code Notes: Always "ST" | M | ID | 2/3 |
N102 | 93 | Name Notes: Ship To Name. This is a free form text field and may contain special characters (standard UTF8). Max length is 50 characters. This should appear on the Amazon-branded packing slip. | M | AN | 1/60 |
Code Values:
Code | Name |
ST | Ship To |
Segment Usage: The customer's ship-to name. This data is not provided for Amazon Label vendors, but is replaced with "XXXXX". For Vendor Own Carrier/ Vendor Own Label orders, this segment will contain the ship-to name.
Example: N1*ST*Ship To Name
N2 Additional Name Information | ||||
Pos: 320 | Max: 2 | Loop: N1 | Heading - Optional | Elements: 2 |
User Option (Usage): Used | ||||
Loop Path: N1
Purpose: To specify additional names or those longer than 35 characters in length
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N201 | 93 | Name Notes: Ship To Attention. This is a free form text field and may contain special characters (standard UTF8). Max length is 50 characters. This should appear on the Amazon-branded packing slip. Note: If Ship To Attention is not provided by the customer, but Address Line 3 is provided, N201 will contain a space and N202 will contain Address Line 3. | M | AN | 1/60 |
N202 | 93 | Name Notes: Ship To Address Line 3. This is a free form text field and may contain special characters (standard UTF8). Max length is 60 characters. This should appear on the Amazon-branded packing slip. | O | AN | 1/60 |
Segment Usage: Additional name information. This data is not provided for Amazon Label vendors, but is replaced with "XXXXX". For Vendor Own Carrier/ Vendor Own Label orders, this segment can contain additional name information.
Example: N2*Darla Dinkins
N3 Address Information | ||||
Pos: 330 | Max: 2 | Loop: N1 | Heading - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Loop Path: N1
Purpose: To specify the location of the named party
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N301 | 166 | Address Information Notes: Ship To Address Line 1. Free form text, may contain special characters (UTF8). Max length 60 characters. Should appear on the Amazon-branded packing slip. | M | AN | 1/55 |
N302 | 166 | Address Information Notes: Ship To Address Line 2. Free form text, may contain special characters (UTF8). Max length 60 characters. Should appear on the Amazon-branded packing slip. | O | AN | 1/55 |
Segment Usage: The ship-to street address. This data is not provided for Amazon Label vendors, but is replaced with "XXXXX". For Vendor Own Carrier/ Vendor Own Label orders, this segment will contain the relevant details.
Example: N3*4 Privet Drive
N4 Geographic Location | ||||
Pos: 340 | Max: >1 | Loop: N1 | Heading - Mandatory | Elements: 6 |
User Option (Usage): Must use | ||||
Loop Path: N1
Purpose: To specify the geographic place of the named party
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N401 | 19 | City Name Notes: Ship To City Name. Max length 30 characters. Should appear on packing slip. | M | AN | 2/30 |
N402 | 156 | State or Province Code Notes: Ship To State or Province. Should appear on packing slip. | M | ID | 2/2 |
N403 | 116 | Postal Code Notes: Ship To Postal Code. Max length 15 characters. Should appear on packing slip. | M | ID | 3/15 |
N404 | 26 | Country Code Notes: Ship To Country Code. ISO 2 character country code. Should appear on packing slip. | M | ID | 2/3 |
N405 | 309 | Location Qualifier Notes: Always "CC" | X | ID | 1/2 |
N406 | 310 | Location Identifier Notes: Ship To Country code or name | O | AN | 1/30 |
Code Values:
Code | Name |
CC | Country |
Segment Usage: The ship-to city, state, zip code, and country code. For Amazon Label vendors, state, zip, country code will be provided. Ship-to city will be replaced with "XXXXX". For Vendor Own Carrier/ Vendor Own Label orders, this segment will contain all data.
Example: N4*Little Whinging*CA*90033-4310*US*CC*US
TD5 Carrier Details (Routing Sequence/Transit Time) | ||||
Pos: 390 | Max: 1 | Loop: N1 | Heading - Mandatory | Elements: 4 |
User Option (Usage): Must use | ||||
Loop Path: N1
Purpose: To specify the carrier and sequence of routing and provide transit time information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
TD502 | 66 | Identification Code Qualifier Notes: Always "92" | M | ID | 1/2 |
TD503 | 67 | Identification Code Notes: Amazon.com defined Ship Method Codes indicating shipping carrier and shipment service level. Ship Method Codes are case and format sensitive. The Ship Method Code sent in the 850 should be the same Ship Method Code returned in the corresponding 856. Note: Ship Method Codes are vendor specific and will be provided to each vendor during the implementation process. Value examples: USPS_DS (Priority Mail), USPS_SMART_MAIL, UPS_2ND, UPS_DOM_3DAY_RES, UPS_GR_COM, UPS_GR_RES, UPS_NEXT, UPS_NEXT_SAVER, FEDEX_NEXT_PRI, FEDEX_NEXT_STD, FEDEX_SECOND, FEDEX_3DAY | M | AN | 2/80 |
TD507 | 309 | Location Qualifier | M | ID | 1/2 |
TD508 | 310 | Location Identifier Notes: This field specifies the "Ship to Address Type" | M | AN | 1/30 |
Code Values:
Code | Name |
92 | Assigned by Buyer or Buyer's Agent |
ZZ | Mutually Defined |
Example: TD5**92*UPS_DOM_3DAY_RES****ZZ*RES
Loop Name - Customer Bill To Party
Pos: 310 Repeat: 1 Loop: N1 Mandatory
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
310 | N1 | Name - Customer Bill To Party | O | 1 |
| Used |
320 | N2 | Additional Name Information | O | 2 |
| Used |
330 | N3 | Address Information | O | 2 |
| Used |
340 | N4 | Geographic Location | O | >1 |
| Used |
360 | PER | Administrative Communications Contact | O | >1 |
| Used |
N1 Name - Customer Bill To Party | ||||
Pos: 310 | Max: 1 | Loop: N1 | Heading - Optional | Elements: 2 |
User Option (Usage): Used | ||||
Loop Path: N1
Purpose: To identify a party by type of organization, name, and code
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N101 | 98 | Entity Identifier Code Notes: Always "LW" | O | ID | 2/3 |
N102 | 93 | Name Notes: Customer Bill To Name. Free form text, may contain special characters (UTF8). Max length 50 characters. Should appear on packing slip. | O | AN | 1/60 |
Code Values:
Code | Name |
LW | Customer |
Segment Usage: The customer's bill-to name for the order. This data is not provided on the DF 850, but is replaced with "XXXXX".
Example: N1*LW*XXXXX
N2 Additional Name Information (Customer Bill To) | ||||
Pos: 320 | Max: 2 | Loop: N1 | Heading - Optional | Elements: 2 |
User Option (Usage): Used | ||||
Loop Path: N1
Purpose: To specify additional names or those longer than 35 characters in length
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N201 | 93 | Name Notes: Customer Bill To Address Line 3. Free form text, may contain special characters (UTF8). Max length 60 characters. Should appear on packing slip. Note: Bill To Address can be International. | M | AN | 1/60 |
N202 | 93 | Name | O | AN | 1/60 |
Segment Usage: Additional name information. This data is not provided on the DF 850, but is replaced with "XXXXX".
Example: N2*XXXXX
N3 Address Information (Customer Bill To) | ||||
Pos: 330 | Max: 2 | Loop: N1 | Heading - Optional | Elements: 2 |
User Option (Usage): Used | ||||
Loop Path: N1
Purpose: To specify the location of the named party
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N301 | 166 | Address Information Notes: Customer Bill To Address Line 1. Free form text, may contain special characters (UTF8). Max length 60 characters. Should appear on packing slip. Note: Bill To Address can be International. | O | AN | 1/55 |
N302 | 166 | Address Information Notes: Customer Bill To Address Line 2. Free form text, may contain special characters (UTF8). Max length 60 characters. Should appear on packing slip. Note: Bill To Address can be International. | O | AN | 1/55 |
Segment Usage: The customer bill-to street address. This data is not provided on the DF 850, but is replaced with "XXXXX".
Example: N3*XXXXX
N4 Geographic Location (Customer Bill To) | ||||
Pos: 340 | Max: >1 | Loop: N1 | Heading - Optional | Elements: 4 |
User Option (Usage): Used | ||||
Loop Path: N1
Purpose: To specify the geographic place of the named party
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
N401 | 19 | City Name Notes: Customer Bill To City Name. Max length 50 characters. Should appear on packing slip. Note: Bill To Address can be International. | O | AN | 2/30 |
N402 | 156 | State or Province Code Notes: Customer Bill To State. Should appear on packing slip. Note: Bill To Address can be International. | O | ID | 2/2 |
N403 | 116 | Postal Code Notes: Customer Bill To Postal Code. Max length 15 characters. Should appear on packing slip. Note: Bill To Address can be International. | O | ID | 3/15 |
N404 | 26 | Country Code Notes: Customer Bill To Country Code. ISO 2 character country code. Should appear on packing slip. Note: Bill To Address can be International. | O | ID | 2/3 |
Segment Usage: The customer's bill-to city, state, zip code, and country code. This data is not provided on the DF 850, but is replaced with "XXXXX".
Example: N4*XXXXX*XX*XXXXX*XX
PER Administrative Communications Contact | ||||
Pos: 360 | Max: >1 | Loop: N1 | Heading - Optional | Elements: 6 |
User Option (Usage): Used | ||||
Loop Path: N1
Purpose: To identify a person or office to whom administrative communications should be directed
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
PER01 | 366 | Contact Function Code Notes: Always "ZZ" | M | ID | 2/2 |
PER02 | 93 | Name Notes: Customer Bill To Party Name. Free form text, may contain special characters (UTF8). This field is optional and only sent when provided by the customer. | O | AN | 1/60 |
PER03 | 365 | Communication Number Qualifier Notes: Always "EM" | X | ID | 2/2 |
PER04 | 364 | Communication Number Notes: Customer Bill To Party Email Address. Free form text, may contain special characters (UTF8). Optional, only sent when provided by the customer. | X | AN | 1/80 |
PER05 | 365 | Communication Number Qualifier Notes: Always "TE" | X | ID | 2/2 |
PER06 | 364 | Communication Number Notes: Customer Bill To Party Phone Number. Free form text, may contain special characters (UTF8). Optional, only sent when provided by the customer. | X | AN | 1/80 |
Code Values:
Code | Name |
ZZ | Mutually Defined |
EM | Electronic Mail |
TE | Telephone |
Segment Usage: The customer's bill-to phone number. This data is not provided on the DF 850, but is replaced with "XXXXX".
Example: PER*ZZ****TE*XXXXXXXXXX
Loop Baseline Item Data
Pos: 010 Repeat: 100000 Loop: PO1 Mandatory
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
010 | PO1 | Baseline Item Data | M | 1 |
| Must use |
040 | Loop CTP | Pricing Information - Price to Customer | O | >1 |
| Used |
289 | MSG | Message Text - Item Description | O | >1 |
| Used |
289 | MSG | Message Text - Gift Message | C | >1 |
| Dependent |
PO1 Baseline Item Data | ||||
Pos: 010 | Max: 1 | Loop: PO1 | Detail - Mandatory | Elements: 15 |
User Option (Usage): Must use | ||||
Loop Path: PO1
Purpose: To specify basic and most frequently used line item data
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
PO101 | 350 | Assigned Identification Notes: Line Item ID. The Line Item ID must be retained and referred to in subsequent messages (855, 856, 810). This number is generally sequential (1, 2, 3, etc.). Note: The combination of PO101 and PO107 should remain constant throughout the order cycle and across messages. | M | AN | 1/20 |
PO102 | 330 | Quantity Ordered Notes: Quantity Ordered. This should appear on the Amazon-branded packing slip. | M | R | 1/15 |
PO103 | 355 | Unit or Basis for Measurement Code Notes: Always "EA" | M | ID | 2/2 |
PO104 | 212 | Unit Price Notes: This is Amazon's Expected Cost for the product, not including fulfillment charges. Format: Two Decimals (e.g. 9.00). This should not be included on the Amazon-branded packing slip. | O | R | 1/17 |
PO105 | 639 | Basis of Unit Price Code Notes: Always "NT" | O | ID | 2/2 |
PO106 | 235 | Product/Service ID Qualifier Notes: Always "SK" | M | ID | 2/2 |
PO107 | 234 | Product/Service ID Notes: This will be the Product ID of the item being ordered. This should appear on the Amazon-branded packing slip. Note: Product ID's will vary by vendor and will be agreed upon before beginning the implementation process (SKU, UPC, ASIN, etc.) | M | AN | 1/48 |
PO108 | 235 | Product/Service ID Qualifier Notes: Always "B6" | X | ID | 2/2 |
PO109 | 234 | Product/Service ID Notes: Author Name. This will only be sent when applicable. If sent, this should appear on the Amazon-branded packing slip. | O | AN | 1/48 |
PO110 | 235 | Product/Service ID Qualifier Notes: B4 = Binding Code, TP = Product Type Code | X | ID | 2/2 |
PO111 | 234 | Product/Service ID Notes: This will be the Binding Description (e.g. Hardback). This will only be sent when applicable. If sent, this should appear on the Amazon-branded packing slip. | O | AN | 1/48 |
PO112 | 235 | Product/Service ID Qualifier Notes: Always "BL" | X | ID | 2/2 |
PO113 | 234 | Product/Service ID Notes: This will be the Merchant Branding of the item. This value does not need to be printed on the Amazon-branded packing slip or returned to Amazon in any corresponding messages. | O | AN | 1/48 |
PO114 | 235 | Product/Service ID Qualifier Notes: Always "ZZ" | M | ID | 2/2 |
PO115 | 234 | Product/Service ID Notes: This will be the Seller Of Record of the item. This should appear on the Amazon-branded packing slip. | M | AN | 1/48 |
Code Values:
Code | Name |
EA | Each |
NT | Net |
SK | Stock Keeping Unit (SKU) |
B6 | Author Code |
B4 | Binding Code |
TP | Product Type Code |
BL | Brand/Label |
ZZ | Mutually Defined |
Example: PO1*1*1*EA*6.35*NT*SK*1110007***TP*Kitchen*BL*1*ZZ*Amazon.com, LLC
Loop Pricing Information - Price to Customer
Pos: 040 Repeat: >1 Loop: CTP Optional Loop Path: PO1
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
040 | CTP | Pricing Information - Price to Customer | O | 1 |
| Used |
CTP Pricing Information - Price to Customer | ||||
Pos: 040 | Max: 1 | Loop: CTP | Detail - Optional | Elements: 2 |
User Option (Usage): Used | ||||
Loop Path: PO1-CTP
Purpose: To specify pricing information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
CTP02 | 236 | Price Identifier Code Notes: COD is applicable for JP vendors only. | X | ID | 3/3 |
CTP03 | 212 | Unit Price Notes: This segment provides Amazon price to the customer. The price indicated in CTP03 should be included on the Amazon branded packing slip, unless it's a gift order. Format: Two Decimals (e.g. 9.00). This will be in the currency expressed in CUR02. This should appear on the Amazon-branded packing slip. | X | R | 1/17 |
Code Values:
Code | Name |
COD | Cash on Delivery Amount |
PUR | Purchase Price |
Segment Usage: Price Identifier code COD (Cash on Delivery amount) is ONLY used for JP vendors. (JP vendors need to configure their system to receive this code without error)
Example: CTP**PUR*14.17 | CTP**COD*14.17
MSG Message Text - Item Description | ||||
Pos: 289 | Max: >1 | Loop: PO1 | Detail - Optional | Elements: 1 |
User Option (Usage): Used | ||||
Loop Path: PO1
Purpose: To provide a free-form format that allows the transmission of text information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
MSG01 | 933 | Free-Form Message Text Notes: Title or Description of goods. May contain special characters (standard UTF8). Max length is 264. This should appear on the Amazon-branded packing slip. | M | AN | 1/264 |
Segment Usage: Product description or book title to be printed at the line item level on the Amazon-branded packing slip.
Example: MSG*Designer Mug with Lid, Red
MSG Message Text - Gift Message | ||||
Pos: 289 | Max: >1 | Loop: PO1 | Detail - Conditional | Elements: 1 |
User Option (Usage): Dependent | ||||
Loop Path: PO1
Purpose: To provide a free-form format that allows the transmission of text information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
MSG01 | 933 | Free-Form Message Text Notes: This will be the Gift Message. Free form text field, may contain special characters (standard UTF8). This field is not edited, it is sent as the customer has entered it. Max length is 264 characters. This should appear on the Amazon-branded packing slip. | M | AN | 1/264 |
Segment Usage: Gift Message to be printed beneath line item on Amazon-branded packing slip.
Example: MSG*Happy Birthday, I hope you enjoy your gift!
Loop Transaction Totals
Pos: 010 Repeat: 1 Loop: CTT Mandatory
Loop Summary:
Pos | Id | Segment Name | Req | Max Use | Repeat | Usage |
010 | CTT | Transaction Totals | M | 1 |
| Must use |
CTT Transaction Totals | ||||
Pos: 010 | Max: 1 | Loop: CTT | Summary - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Loop Path: CTT
Purpose: To transmit a hash total for a specific element in the transaction set
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
CTT01 | 354 | Number of Line Items Notes: Total number of line items in the transaction set | M | N0 | 1/6 |
CTT02 | 347 | Hash Total Notes: This will be the total number of units being requested | M | R | 1/10 |
Example: CTT*1*1
SE Transaction Set Trailer | ||||
Pos: 030 | Max: 1 | Loop: N/A | Summary - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
SE01 | 96 | Number of Included Segments Notes: Total number of segments included in a transaction set including ST and SE segments | M | N0 | 1/10 |
SE02 | 329 | Transaction Set Control Number Notes: Same as ST02 | M | AN | 4/9 |
Example: SE*26*0001
GE Functional Group Trailer | ||||
Pos: | Max: 1 | Loop: N/A | Not Defined - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Purpose: To indicate the end of a functional group and to provide control information
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
GE01 | 97 | Number of Transaction Sets Included | M | N0 | 1/6 |
GE02 | 28 | Group Control Number Notes: Same as GS06 | M | N0 | 1/9 |
Example: GE*1*136926
IEA Interchange Control Trailer | ||||
Pos: | Max: 1 | Loop: N/A | Not Defined - Mandatory | Elements: 2 |
User Option (Usage): Must use | ||||
Purpose: To define the end of an interchange of zero or more functional groups and interchange-related control segments
Element Summary:
Ref Id | Id | Element Name | Req | Type | Min/Max |
IEA01 | I16 | Number of Included Functional Groups | M | N0 | 1/5 |
IEA02 | I12 | Interchange Control Number | M | N0 | 9/9 |
Example: IEA*1*000136926
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article