X12 855 Purchase Order Acknowledgment
This X12 Transaction Set 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
- ^ Repetition
- None included
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
- PR
- Purchase Order Acknowledgment (855)
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).
- 855
- Purchase Order Acknowledgment
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 Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
PO1/ACK segment usage required.
Used when the PO is accepted, but there are changes to some or all items. - AD
- Acknowledge - With Detail, No Change
PO1/ACK segment usage required.
Used when all items are accepted. All ACK01 values must contain IA. - RD
- Reject with Detail
PO1/ACK segment usage required.
Used when all items are rejected. All ACK01 values must contain IR.
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BAK04 is the date assigned by the purchaser to purchase order.
Purchase Order Date
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BAK09 is the date assigned by the sender to the acknowledgment.
PO Acknowledgement Date
Reference Information
To specify identifying information
One iteration of the REF segment is required for the Chewy.com internal vendor ID (REF01=IA).
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Only send this segment if the FOB information is changing from what was sent (if sent) on the PO. Else, do not send.
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- DF
- Defined by Buyer and Seller
- PP
- Prepaid (by Seller)
- TP
- Third Party Pay
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
A free-form description to clarify the related data elements and their content
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Only send this segment if the ITD information is changing from what was sent on the PO. Else, do not send.
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
Only send this segment if changing for the entire order. Else, if only the scheduled ship date for certain items is changing, use the ACK segment to indicate this.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Only send this segment if the Carrier information is changing from what was sent (if sent) on the PO. Else, do not send.
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
SCAC
Code specifying the method or type of transportation for the shipment
- A
- Air
- K
- Backhaul
- M
- Motor (Common Carrier)
- P
- Private Carrier
- T
- Best Way (Shippers Option)
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Carrier Routing / Name
Code indicating the level of transportation service or the billing service offered by the transportation carrier
- 3D
- Three Day Service
- AM
- A.M.
- CG
- Ground
- CX
- Express Service
- DC
- Delivery Confirmation
- DS
- Door Service
- ET
- Proof of Delivery (POD) with Signature
- FC
- First Class
- G2
- Standard Service
- ND
- Next Day Air
- NH
- Next Day Hundred Weight
- ON
- Overnight
- PB
- Priority Mail
- PI
- Priority Mail Insured
- PM
- PM
- SA
- Same Day
- SC
- Second Day Air
- SD
- Saturday
- SE
- Second Day
- SG
- Standard Ground
- SH
- Second Day Hundred Weight
- SI
- Standard Ground Hundred Weight
If the Purchase Order (EDI 850) is being rejected in full (BAK02=RD) please include a note as to why.
Extended Reference Information
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- L1
- Letters or Notes
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
N902 must contain the following 3 character code to identify the type of note to follow in MTX02.
- GEN
- General Note
To transmit large volumes of message text
If you are rejecting the entire order, you must provide one of the below reason codes. If possible, please send a second N9 loop with a general description of why you are rejecting the order as well:
VI - Incorrect VPN
PI - Incorrect Pricing
UI - Incorrect UPC
OS - Out of Stock
VD - Vendor Discontinued Item
MD - Manufacturer Discontinued Item
OT - Other
Detail
When indicating acceptance of the entire order (BAK02 = AD), or rejecting the entire order (BAK02 = RD), line item status details are required. If an order is partially accepted (BAK02 = AC), line item status details are required for every item on the Purchase Order.
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
The Vendor Item # (VN) is required. However, all item identifiers are recommended, specifically the GTIN.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Numeric value of quantity
- PO102 is quantity ordered.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- BA
- Bale
- BG
- Bag
- CA
- Case
- EA
- Each
- PH
- Pack (PAK)
Price per unit of product, service, commodity, etc.
If ACK01=IP, then the new price for this item must be sent in PO104
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.
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
Sending the Chewy.com SKU number is highly recommended.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
One iteration of the PID for the Product Description (PID05, when PID01=F and PID02=08) is required. TheProduct Description (PID05, when PID01=F and PID02=08) can repeat (up to 2 iterations) if needed.
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Code identifying the general class of a product or process characteristic
- 08
- Product
A free-form description to clarify the related data elements and their content
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
Code specifying the action taken by the seller on a line item requested by the buyer
If an incorrect item is sent, please reject with ACK01=R2, with the correct item number provided in the PO1 segment and a note included to specify.
- IA
- Item Accepted
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
- IR
- Item Rejected
- R2
- Item Rejected, Invalid Item Product Number
Numeric value of quantity
When ACK01= IQ, then ACK02 and ACK03 are required.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
When ACK01= IQ, then ACK02 and ACK03 are required.
- BA
- Bale
- BG
- Bag
- CA
- Case
- EA
- Each
- PH
- Pack (PAK)
Code specifying type of date or time, or both date and time
- 068
- Current Schedule Ship
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
If the items from the Purchase Order (EDI 850) are being rejected (ACK01 =IR) a line item note as to why is required. See MTX02 for allows reasons codes.
Extended Reference Information
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- L1
- Letters or Notes
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
N902 must contain the following 3 character code to identify the type of note to follow in MTX02.
- GEN
- General Note
To transmit large volumes of message text
If you are rejecting the item, you must provide one of the below reason codes. If possible, please send a second N9 loop with a general description of why you are rejecting the item as well:
VI - Incorrect VPN
PI - Incorrect Pricing
UI - Incorrect UPC
OS - Out of Stock
VD - Vendor Discontinued Item
MD - Manufacturer Discontinued Item
OT - Other
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.
Total number of line items in the transaction set
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
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.