X12 855 Direct Fulfillment Purchase Order Acknowledgment
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) 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 a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.
- ~ 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
- PR
- Purchase Order Acknowledgement (855)
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).
- 855
- Purchase Order Acknowledgment
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
BAK00ATTesT000813920070626~
BAK00RDTesT000859620070808~
Code identifying purpose of transaction set
Always '00'
- 00
- Original
Code specifying the type of acknowledgment
Orders are Fill or Kill.
If ALL line items on the order are accepted, use 'AT'.
If ANY line items on the order are rejected, use 'RD'.
*This field is required
- AT
- Accepted
- RD
- Reject with Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
This will be the Amazon encrypted Shipment ID, which is case sensitive. This number is unique - if a duplicate ShipmentID is ever received it should be rejected via the 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.
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
Order Confirmation Date (Format: CCYYMMDD) expressed in UTC format.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BAK08 is the seller's order number.
Vendor's Order Reference Number.
This will be the reference number in the vendor's system.
This field is required if BAK02 = "AT"
Name
To identify a party by type of organization, name, and code
N1SFABCD92ABCD~
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Free-form name
This will be the Amazon code representing the warehouse that the order should ship from. This is usually a four character alpha code (e.g. ABCD).
Code designating the system/method of code structure used for Identification Code (67)
- 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 will be the Amazon code representing the warehouse that the order should ship from. This is usually a four character alpha code (e.g. ABCD)
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
PO11*****SK1617~
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Line Item ID. This should be the same Line Item ID that was sent in the 850. It must be retained and referred to in subsequent messages (855, 856, 810).
This number is generally sequential (1, 2, 3, etc.).
The combination of PO101 and PO107 should remain constant throughout the order cycle and across messages. Whenever the number in PO101 is used the information will reference the item in PO107.
Quantity ordered
This will be the original Quantity Ordered from the 850.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- 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.
- SK
- Stock Keeping Unit (SKU)
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
ACKIA1EA**************************00
ACKIR41EA**************************03
Code specifying the action taken by the seller on a line item requested by the buyer
Use 'IA' if ALL of the ordered quantity of the item is accepted.
Used 'IR' if ANY of the ordered quantity of the item is rejected.
- IA
- Item Accepted
- IR
- Item Rejected
Numeric value of quantity
Quantity of the Item that is Accepted or Rejected.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Mutually Defined
Identifying number for a product or service
Code indicating a code from a specific industry code list
- ACK29 Industry Reason Code may be used to identify the item status. In addition, it may be used in conjunction with ACK01 to further clarify the status.
Code further detailing exceptions, these codes may be mutually defined. Amazon and vendor will mutually agree upon a list of codes that will be appropriate for their relationship.
- 00
- Shipping 100 percent of ordered product
- 02
- Canceled due to missing/invalid SKU
- 03
- Canceled out of stock
- 04
- Canceled due to duplicate Amazon Ship ID
- 05
- Canceled due to missing/invalid Bill To Location Code
- 06
- Canceled due to missing/invalid Ship From Location Code
- 07
- Canceled due to missing/invalid Customer Ship to Name
- 08
- Canceled due to missing/invalid Customer Ship to Address Line 1
- 09
- Canceled due to missing/invalid Customer Ship to City
- 10
- Canceled due to missing/invalid Customer Ship to State
- 11
- Canceled due to missing/invalid Customer Ship to Postal Code
- 12
- Canceled due to missing/invalid Customer Ship to Country Code
- 13
- Canceled due to missing/invalid Shipping Carrier/Shipping Method
- 20
- Canceled due to missing/invalid Unit Price
- 21
- Canceled due to missing/invalid Ship to Address Line 2
- 22
- Canceled due to missing/invalid Ship to Address Line 3
- 50
- Canceled due to Tax Nexus Issue
- 51
- Canceled due to Restricted SKU/Qty
- 53
- Canceled due to USPS >$400
- 54
- Canceled due to Missing AmazonShipID
- 55
- Canceled due to Missing AmazonOrderID
- 56
- Canceled due to Missing LineItemId
- 71
- Canceled due to discontinued item
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.
CTT11~
Total number of line items in the transaction set
Total number of line items in the message.
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.
Total number of units accepted.
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Fill or Kill
GS*PR*SENDERID*AMAZONDS*20220524*2001*123*X*004010~
ST*855*00012~
BAK*00*RD*TY67JNr9D*20220524****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
PO1*1*3*EA***SK*1617~
ACK*IA*3*EA**************************00~
PO1*2*2*EA***SK*4927~
ACK*IA*2*EA**************************00~
PO1*3*1*EA***SK*1682~
ACK*IR*1*EA**************************03~
CTT*3*5~
SE*11*00012~
GE*1*123~
IEA*1*000000103~
Invalid Ship Method
GS*PR*SENDERID*AMAZONDS*20220524*2001*122*X*004010~
ST*855*00011~
BAK*00*RD*Tc89JNr2d*20220524****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
PO1*1*1*EA***SK*1617~
ACK*IR*1*EA**************************13~
CTT*1*0~
SE*7*00011~
GE*1*122~
IEA*1*000000102~
Invalid SKU
GS*PR*SENDERID*AMAZONDS*20220524*2001*95*X*004010~
ST*855*00010~
BAK*00*RD*Tx40HNv4d*20220524****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
PO1*1*1*EA***SK*B000000000~
ACK*IR*1*EA**************************02~
CTT*1*0~
SE*7*00010~
GE*1*95~
IEA*1*000000101~
Multiple Item Acceptance
GS*PR*SENDERID*AMAZONDS*20220524*2001*36*X*004010~
ST*855*0001~
BAK*00*AT*T9UhKLr6P*20220524****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
PO1*1*3*EA***SK*1617~
ACK*IA*3*EA**************************00~
PO1*2*2*EA***SK*4927~
ACK*IA*2*EA**************************00~
PO1*3*1*EA***SK*9876~
ACK*IA*1*EA**************************00~
CTT*3*6~
SE*11*0001~
GE*1*36~
IEA*1*000000105~
Out of Stock
GS*PR*SENDERID*AMAZONDS*20220524*2001*128*X*004010~
ST*855*00011~
BAK*00*RD*TW11wr2F*20220524****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
PO1*1*1*EA***SK*7005~
ACK*IR*1*EA**************************03~
CTT*1*0~
SE*7*00011~
GE*1*128~
IEA*1*000000109~
Single Item Acceptance
GS*PR*SENDERID*AMAZONDS*20220524*2001*55*X*004010~
ST*855*0001~
BAK*00*AT*T3uPjk5Id*20220524****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
PO1*1*3*EA***SK*1619~
ACK*IA*3*EA**************************00~
CTT*1*3~
SE*7*0001~
GE*1*55~
IEA*1*000000108~
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.