X12 855 Retail 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
Please Note: All of BAK01, BAK02, BAK03 and BAK04 are mandatory and must be present or the file will reject in the Amazon.com systems. BAK02 AC should be used if response happens with change on quantity
and price, BAK02 AD should be used if no change apply to quantity and price.
Sample Data:
BAK00ACU722965920070801
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
- AD
- Acknowledge - With Detail, No Change
Identifying number for Purchase Order assigned by the orderer/purchaser
This field will be the Amazon PO number that this message is acknowledging.
Formatting Notes: The PO number needs to match the PO number from the Purchase Order. Do not add anything to the PO number like PO# or blank characters. If the PO number on the POA can not be matched against an existing PO number on the PO, your response will not be processed.
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
External Information: This field will be the PO date
Formatting Notes: CCYYMMDD
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Sample Data:
PO1116EA10.96NTEN*9780764327834
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Quantity ordered
This field will be the quantity for this item that was ordered by Amazon in the PO.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
The same unit of measurement code provided in the Amazon Purchase Order should be used.
- CA
- Case
- EA
- Each
Price per unit of product, service, commodity, etc.
This field will contain the cost price to Amazon and should match the cost price on the invoice. Please note this is a required field, if this is left blank the file will reject in Amazon systems. Price information should not be 0 or negative.
Code identifying the type of unit price for an item
Please note this is a required field, if this is left blank the file will reject in Amazon systems.
- NT
- Net
Indicates a net unit price
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.
Please note this is a required field, if this is left blank the file will reject in Amazon's systems.
- BP
- Buyer's Part Number
- EN
- European Article Number (EAN) (2-5-5-1)
- IB
- International Standard Book Number (ISBN)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
A 14-digit code that uniquely identifies the manufacturer's shipping unit, includingthe packaging indicator and check digit; the first digit is the packaging indicator, the next two digitsare the number system characters, the next five digits are the manufacturer ID number, thesecond five digits are the item code, and the final digit is the check digit
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Pricing Information
To specify pricing information
The CTP segment is required only if a vendor sells books with a list price. Do not include the CTP segment if there is no list price on the book, or if you do not have product data. If the CTP segment is included and is missing any of the required data, the file will reject in the Amazon systems.
The CTP segment is required only if a vendor sells books with a list price. Do not include the CTP segment if there is no list price on the book, or if you do not have product data. If the CTP segment is included and is missing any of the required data, the file will reject in the Amazon systems.
Sample Data:
CTP*SLP9.95103UNDIS.44
Code identifying pricing specification
- DPR
- Discount Price
- LPR
- List Price
- NET
- Net Item Price
- SLP
- Suggested List Price
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
External Information: This field will contain the list price of the book.
Code indicating the type of price multiplier
- DIS
- Discount Multiplier
Value to be used as a multiplier to obtain a new value
- CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10% discount is given.
This field will be the discount multiplier that should be applied to the price. CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10% discount is given.
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
The ACK segment is a mandatory part of the 855 and any message without it will be rejected in Amazon's systems. As a minimum, one ACK segment has to be provided for each line item. You can also use multiple ACK segments to indicate different responses and expected ship dates for a line item. If you can provide Estimated Shipment Dates, you have to state it via the ACK04 with ACK05 elements.
For more information on how to use the ACK segment, please refer to the specific examples in the Appendix EDI 855document
Sample Data:
ACKIA5EA06820130815
ACKIB3EA06820130821
Code specifying the action taken by the seller on a line item requested by the buyer
External Information: If codes IS, AN, BC, BH, IF, IH, or IW are used, the messages contained in this file will reject in Amazon's systems. Please also see the Appendix EDI 855 document for further information.
- BP
- Item Accepted - Partial Shipment, Balance Backordered
Amazon interpretation is that stated quantity will be immediately shipped / delivered on the stated date. The remaining quantity (ordered quantity minus all confirmed quantity) will be delivered later (back-ordered). This is not the preferred way of notification about a split shipment.
Amazon would prefer that you indicate one ACK loop using code IA with the corresponding date and another ACK loop using code IB and the corresponding date. - IA
- Item Accepted
Amazon interpretation is that the quantity stated in ACK02 will be immediately shipped / delivered on the stated date.
- IB
- Item Backordered
Amazon interpretation is that the quantity stated in ACK02 is back-ordered and will be shipped / delivered on the stated date.
- IQ
- Item Accepted - Quantity Changed
Amazon interpretation is that stated quantity will be immediately shipped / delivered on the stated date. The remaining quantity (ordered quantity minus all confirmed quantity) is cancelled.
- IR
- Item Rejected
Amazon interpretation is that the quantity stated in ACK02 will not be delivered to Amazon as part of this Purchase Order. The Amazon nomenclature for this is "soft reject", meaning that the item will be reordered with next order run. If you want to remove this item from being ordered you should use ACK code R3 which will be a "hard reject", meaning that Amazon will restrict this item from being re-ordered. After 5 consecutive “soft reject” codes for the same product (separated by a time gap of at least 48 hours). The item will also be placed on an order pause for 1 month.
- R2
- Item Rejected, Invalid Item Product Number
Amazon interpretation is that the quantity stated in ACK02 will not be delivered to Amazon as part of this Purchase Order due to errors with catalog information. The Amazon nomenclature for this is "soft reject", meaning this item can be ordered again. After 5 consecutive “soft reject” codes for the same product (separated by a time gap of at least 48 hours). The item will also be placed on an order pause for 1 month.
- R3
- Item Rejected, Invalid Unit of Issue
Amazon interpretation is that the quantity stated in ACK02 will not be delivered to Amazon as part of this Purchase Order due to the item being obsolete and should no longer be ordered. The Amazon nomenclature for this is "hard reject", meaning this item should not be re-ordered. If this code is received 2 consecutive times (separated by a time gap of at least 48 hours), the item will not be reordered.
Numeric value of quantity
External Information:
This field will be the quantity of this item that relates to theACK code in ACK01. This value should not be zero.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
- EA
- Each
Code specifying type of date or time, or both date and time
Internal Information: If you can provide Estimated ship dates per line item, you have to state these in ACK05 with ACK04 qualifier 068.
- 068
- Current Schedule Ship
Date/Time Reference
To specify pertinent dates and times
If you can provide Estimated delivery dates per line item, you have to state these in DTM02 with DTM01 qualifier 067.
Sample Data:
DTM06720070801
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.
Sample Data:
CTT55
Total number of line items in the transaction set
This field will be the number of line the logical count of PO1 segments.
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 sum of the value of quantities ordered (PO102) for each PO1 segment.
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
AMZN Procurement Example A
GS*PR*VENDOR*AMAZON*20130805*1608*3*X*004010~
ST*855*0001~
BAK*00*AD*L1234567*20130805**17510~
PO1*1*1*EA*10.96*NT*UP*028877454078~
ACK*IA*1*EA*068*20130815~
DTM*067*20130820~
PO1*2*10*EA*11.6*NT*UP*050086068777~
ACK*IA*5*EA*068*20130815~
ACK*IB*3*EA*068*20130821~
ACK*IR*2*EA~
PO1*3*1*EA*12.21*NT*UP*077774644020~
ACK*R2*1*EA~
PO1*4*1*EA*11.19*NT*UP*696998506428~
ACK*IA*1*EA*068*20130815~
DTM*067*20130820~
PO1*5*1*EA*11.38*NT*UP*696998901926~
ACK*IA*6*EA*068*20130815~
DTM*067*20130820~
ACK*IB*4*EA*068*20130821~
DTM*067*20130830~
CTT*5*14~
SE*21*0001~
GE*1*3~
IEA*1*000100000~
AMZN Procurement Example B
GS*PR*VENDOR*AMAZON*20141005*0734*931*X*004010~
ST*855*0001~
BAK*00*AD*N1234567*20141005~
PO1*1*103*EA*4.38*NT*UP*028877454078~
CTP**SLP*9.95*103*EA*DIS*.44~
ACK*IB*103*EA*068*20141009~
PO1*2*1*EA*54.12*NT*UP*050086068777~
CTP**SLP*94.95*1*EA*DIS*.57~
ACK*IA*1*EA*068*20141009~
PO1*3*189*EA*4.38*NT*UP*077774644020~
CTP**SLP*9.95*189*EA*DIS*.44~
ACK*IB*189*EA*068*20141009~
PO1*4*5*EA*10.54*NT*UP*696998506428~
CTP**SLP*23.95*5*EA*DIS*.44~
ACK*IA*5*EA*068*20141019~
DTM*067*20141020~
CTT*4*298~
SE*17*0001~
GE*1*931~
IEA*1*000100001~
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.