Chewy.com
/
Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Chewy.com. Contact Chewy.com for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Chewy.com logo

X12 855 Purchase Order Acknowledgment

X12 Release 5010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/chewy-com/purchase-order-acknowledgment/01H66H1QQEEP6B2QEDS682TSVJ
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
0100
Transaction Set Header
Max use 1
Required
BAK
0200
Beginning Segment for Purchase Order Acknowledgment
Max use 1
Required
REF
0500
Reference Information
Max use 1
Required
FOB
0800
F.O.B. Related Instructions
Max use 1
Optional
ITD
1300
Terms of Sale/Deferred Terms of Sale
Max use 5
Optional
DTM
1500
Date/Time Reference
Max use 10
Optional
TD5
2400
Carrier Details (Routing Sequence/Transit Time)
Max use 12
Optional
N9 Loop
summary
CTT Loop
SE
0300
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code indicating sender's request for an interchange acknowledgment

0
No Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
ISA-15
I14
Interchange Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code indicating whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PR
Purchase Order Acknowledgment (855)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission; codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
0100
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BAK
0200
Heading > BAK

Beginning Segment for Purchase Order Acknowledgment

RequiredMax use 1

To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates

Example
BAK-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BAK-02
587
Acknowledgment Type
Required
Identifier (ID)

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.

BAK-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Required
Date (DT)
CCYYMMDD format

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.
Usage notes

Purchase Order Date

Required
Date (DT)
CCYYMMDD format

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.
Usage notes

PO Acknowledgement Date

REF
0500
Heading > REF

Reference Information

RequiredMax use >1

To specify identifying information

Usage notes

One iteration of the REF segment is required for the Chewy.com internal vendor ID (REF01=IA).

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IA
Internal Vendor Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

FOB
0800
Heading > FOB

F.O.B. Related Instructions

OptionalMax use >1

To specify transportation instructions relating to shipment

Usage notes

Only send this segment if the FOB information is changing from what was sent (if sent) on the PO. Else, do not send.

Example
If Description (FOB-03) is present, then Location Qualifier (FOB-02) is required
FOB-01
146
Shipment Method of Payment
Required
Identifier (ID)

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
FOB-02
309
Location Qualifier
Optional
Identifier (ID)

Code identifying type of location

  • FOB02 is the code specifying transportation responsibility location.
DE
Destination (Shipping)
OR
Origin (Shipping Point)
FOB-03
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

ITD
1300
Heading > ITD

Terms of Sale/Deferred Terms of Sale

OptionalMax use 5

To specify terms of sale

Usage notes

Only send this segment if the ITD information is changing from what was sent on the PO. Else, do not send.

Example
ITD-12
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

DTM
1500
Heading > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Usage notes

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.

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

068
Current Schedule Ship
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

TD5
2400
Heading > TD5

Carrier Details (Routing Sequence/Transit Time)

OptionalMax use 12

To specify the carrier and sequence of routing and provide transit time information

Usage notes

Only send this segment if the Carrier information is changing from what was sent (if sent) on the PO. Else, do not send.

Example
If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
TD5-02
66
Identification Code Qualifier
Optional
Identifier (ID)

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)
TD5-03
67
Identification Code
Optional
String (AN)
Min 2Max 4

Code identifying a party or other code

Usage notes

SCAC

TD5-04
91
Transportation Method/Type Code
Optional
Identifier (ID)

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)
TD5-05
387
Routing
Optional
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

Usage notes

Carrier Routing / Name

TD5-12
284
Service Level Code
Optional
Identifier (ID)

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
N9 Loop
RequiredMax >1
Usage notes

If the Purchase Order (EDI 850) is being rejected in full (BAK02=RD) please include a note as to why.

N9
2800
Heading > N9 Loop > N9

Extended Reference Information

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

L1
Letters or Notes
N9-02
127
Reference Identification
Required
String (AN)

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

N902 must contain the following 3 character code to identify the type of note to follow in MTX02.

GEN
General Note
MTX
2900
Heading > N9 Loop > MTX

Text

RequiredMax use >1

To specify textual data

Example
MTX-02
1551
Textual Data
Optional
String (AN)
Min 1Max 4096

To transmit large volumes of message text

Usage notes

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

N9 Loop end
Heading end

Detail

PO1 Loop
RequiredMax >1
Usage notes

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.

PO1
0100
Detail > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

  • PO102 is required.
Usage notes

The Vendor Item # (VN) is required. However, all item identifiers are recommended, specifically the GTIN.

Example
If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
If either Product/Service ID Qualifier (PO1-10) or Product/Service ID (PO1-11) is present, then the other is required
If either Product/Service ID Qualifier (PO1-12) or Product/Service ID (PO1-13) is present, then the other is required
PO1-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
PO1-02
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • PO102 is quantity ordered.
PO1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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)
PO1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

Usage notes

If ACK01=IP, then the new price for this item must be sent in PO104

PO1-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

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
PO1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PO1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Sending the Chewy.com SKU number is highly recommended.

PO1-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PO1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-12
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PO1-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PID Loop
RequiredMax >1
Usage notes

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.

PID
0500
Detail > PO1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

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
PID-02
750
Product/Process Characteristic Code
Required
Identifier (ID)

Code identifying the general class of a product or process characteristic

08
Product
PID-05
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

PID Loop end
ACK Loop
RequiredMax >1
ACK
2700
Detail > PO1 Loop > ACK Loop > ACK

Line Item Acknowledgment

RequiredMax use 1

To acknowledge the ordered quantities and specify the ready date for a specific line item

Example
If either Quantity (ACK-02) or Unit or Basis for Measurement Code (ACK-03) is present, then the other is required
If Date/Time Qualifier (ACK-04) is present, then Date (ACK-05) is required
ACK-01
668
Line Item Status Code
Required
Identifier (ID)

Code specifying the action taken by the seller on a line item requested by the buyer

Usage notes

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
ACK-02
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

When ACK01= IQ, then ACK02 and ACK03 are required.

ACK-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Usage notes

When ACK01= IQ, then ACK02 and ACK03 are required.

BA
Bale
BG
Bag
CA
Case
EA
Each
PH
Pack (PAK)
ACK-04
374
Date/Time Qualifier
Optional
Identifier (ID)

Code specifying type of date or time, or both date and time

068
Current Schedule Ship
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

ACK Loop end
N9 Loop
RequiredMax >1
Usage notes

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.

N9
3500
Detail > PO1 Loop > N9 Loop > N9

Extended Reference Information

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

L1
Letters or Notes
N9-02
127
Reference Identification
Optional
String (AN)

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

N902 must contain the following 3 character code to identify the type of note to follow in MTX02.

GEN
General Note
MTX
3600
Detail > PO1 Loop > N9 Loop > MTX

Text

RequiredMax use >1

To specify textual data

Example
MTX-02
1551
Textual Data
Required
String (AN)
Min 1Max 4096

To transmit large volumes of message text

Usage notes

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

N9 Loop end
PO1 Loop end
Detail end

Summary

CTT Loop
OptionalMax >1
CTT
0100
Summary > CTT Loop > CTT

Transaction Totals

RequiredMax use 1

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
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

CTT Loop end
SE
0300
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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.