X12 850 Retail Purchase Order
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify 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 to identify 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)
Qualifier to designate 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
Qualifier to designate 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
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate 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
- PO
- Purchase Order (850)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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 used in conjunction with Data Element 480 to identify the issuer of the standard
- 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
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
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) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 850
- Purchase Order
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Purchase Order
To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
Example:
BEG00NE*G7984251**20221102
Code specifying the type of Purchase Order
- CN
- Consigned Order
- NE
- New Order
- NP
- New Product Introduction
- RO
- Rush Order
Identifying number for Purchase Order assigned by the orderer/purchaser
This field will contain the Amazon PO number for this order.
Formatting Notes: 8-character alpha-numeric code
Date expressed as CCYYMMDD
- BEG05 is the date assigned by the purchaser to purchase order.
This field will be the PO date
Customer Reference Number
To specify identifying information
This field contains the Amazon vendor code for which the PO is created. This is not the PO number.
Example:
REFCRAMZN_VENDORCODE
Promotion/Deal Number
To specify identifying information
This segment will be sent for import vendors only. To receive this segment
in EDI file please reach out to your Amazon business representative.
Example:
REFPDPROMO_CODE
Associated Purchase Orders
To specify identifying information
This field contains the Amazon Container Consolidation ID (CCID). All purchase orders from Amazon with the same CCID should be shipped together as a Full Truck Load (FTL). To enroll into this program please work with your respective Vendor Manager. This applies only to vendors who participate in Amazon FTL program.
Example:
REFANA131243523
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
This segment will be only sent for import vendors.
Example:
FOBBP*01CFROVYANTIAN, CHINA
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
If the recipient requests, this field will contain a the Shipment Method of Payment
- BP
- Paid by Buyer
- CC
- Collect
- DF
- Defined by Buyer and Seller
- FO
- FOB Port of Call
- PP
- Prepaid (by Seller)
- PS
- Paid by Seller
Code identifying the source of the transportation terms
- 01
- Incoterms
Code identifying the trade terms which apply to the shipment transportation responsibility
- CFR
- Cost and Freight
- CIF
- Cost, Insurance, and Freight
- CIP
- Carriage and Insurance Paid To
- CPT
- Carriage Paid To
- DAF
- Delivered at Frontier
- DDP
- Delivered Duty Paid
- DDU
- Deliver Duty Unpaid
- EXW
- Ex Works
- FCA
- Free Carrier
- FOB
- Free on Board
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- OV
- On Vessel (Free On Board [FOB] point)
A free-form description to clarify the related data elements and their content
In that field the port will be specified
Sales Requirements
To specify general conditions or requirements of the sale
This segment is used to identify if backorder is allowed for this PO.
Example:
CSH*N
Code to identify a specific requirement or agreement of sale
- N
- No Back Order
- Y
- Back Order if Out of Stock
Do Not Deliver After
To specify pertinent dates and times
Amazon paid freight: Read the date in the field as the latest date that Amazon expects to pick up the freight. If the same date is listed in both DTM02 fields, then read that date as the date that Amazon expects to pick up the freight.
Vendor paid freight: Read the date in the DTM02 field as the latest date that Amazon expects the freight to be delivered to the Amazon fulfillment center listed on the purchase order.
Example:
DTM06320221209
Do Not Deliver Before
To specify pertinent dates and times
Amazon paid freight: Read the date in the field as the earliest date that Amazon expects to pick up the freight. If the same date is listed in both DTM02 fields, then read that date as the date that Amazon expects to pick up the freight.
Vendor paid freight: Read the date in the DTM02 field as the earliest date that Amazon expects the freight to be delivered to the Amazon fulfillment center listed on the purchase order.
Example:
DTM06420221203
Marking, Packaging, Loading
To describe marking, packaging, loading, and unloading requirements
This segment is used for Direct Import POs only.
Example:
PKGFCS***40'HC
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
- F
- Free-form
Code specifying the marking, packaging, loading and related characteristics being described
- CS
- Container Shape
A free-form description to clarify the related data elements and their content
- Special marking or tagging data can be given in PKG05 (description).
This field will specify the container size
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
If segment N9 is used, segment MSG is required.
Example:
N9L1SPECIAL INSTRUCTIONS
Message Text
To provide a free-form format that allows the transmission of text information
Example:
MSG*PREFERENCE IS PALLET-LOAD, BUT IF CONTAINERS ARE FLOOR-LOADED, THEN PLEASE DO CLAMP-LOAD OR STRAIGHT FLOOR-LOAD. DO NOT USE SLIP SHEET FOR THIS FC DESTINATION. PAYMENT TERMS ARE PER CONTAINER.
Free-form message text
This field will specify additional comments or messages from the buying contact.
Name
To identify a party by type of organization, name, and code
This segment, used alone, provides the most efficient of providing organizational identification. To obtain this efficiency the identification code (N104) must provide a key to the table maintained by the transaction processing party
Example:
N1ST**151553992
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.
This field will be a code that represents the ship to location. View spreadsheet titled Amazon_North_America_Fulfillment_Center_Address_List.csv for a list of Amazon ship to values.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Example:
PO111EA4.12PEEN*9780812508420
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Quantity ordered
This field will be the quantity of this item ordered
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
- EA
- Each
Price per unit of product, service, commodity, etc.
This field will either be the Price to Amazon Each (Cost) or the Price to Amazon Each (List), depending on the price basis coding in PO105 segment.
Formatting Notes: nnnnn.nn
Please note: Only two decimals are included for values provided via this field (e.g., 8.20).
Code identifying the type of unit price for an item
- PE
- Price per Each
- RE
- Retail Price per Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
This value should be what is returned in the PO106 element in the POA(855)
- BP
- Buyer's Part Number
- EN
- European Article Number (EAN) (2-5-5-1)
- IB
- International Standard Book Number (ISBN)
- UA
- U.P.C./EAN Case Code (2-5-5)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
This field will be the item ID
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
Example:
CTT560
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
This field will be the total number of items ordered.
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 Direct Import
GS*PO*AMAZON*VENDOR*20221110*0201*12911*X*004010~
ST*850*0001~
BEG*00*NE*T82Z63Y5**20221110~
REF*CR*AMZN_VENDORCODE~
FOB*CC~
CSH*N~
DTM*064*20221203~
DTM*063*20221209~
N1*ST**92*RNO1~
PO1*1*8*EA*39*PE*UP*028877454078~
PO1*2*6*EA*40*PE*UP*028877454077~
CTT*2*14~
SE*12*0001~
GE*1*12911~
IEA*1*000012911~
Retail First Order
GS*PO*AMAZON*VENDOR*20221101*0201*12911*X*004010~
ST*850*0001~
BEG*00*NE*T82Z63Y5**20221101~
REF*CR*AMZN_VENDORCODE~
CSH*N~
DTM*064*20221203~
DTM*063*20221209~
N1*ST**92*RNO1~
PO1*1*8*EA*39*PE*UP*028877454078~
PO1*2*6*EA*40*PE*UP*028877454077~
CTT*2*14~
SE*11*0001~
GE*1*12911~
IEA*1*000012911~
Retail FTL
BEG*00*NE*T82Z63Y5**20221110~
REF*CR*AMZN_VENDORCODE~
REF*AN*AMZN_CCID~
CSH*N~
DTM*064*20221203~
DTM*063*20221209~
N1*ST**92*RNO1~
PO1*1*8*EA*39*PE*UP*028877454078~
PO1*2*6*EA*40*PE*UP*028877454077~
CTT*2*14~
SE*12*0001~
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.