X12 855 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.
Zappos requires the 855 (Purchase Order Acknowledgement) document in response to all 850 (Purchase Order) documents within two (2) Business Days of receiving the 850.
- ~ Segment
- * Element
- > Component
- None included
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
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
PO Acknowledgments with missing BAK segments will fail and cannot be processed by Zappos.
Sample Data::
BAK00ADZUTSRQ654321720110920
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of acknowledgment
When BAK02 = “AC” or “AD”, PO1 is required.
When BAK02 = “RJ”, PO1 is not used.
- AC
- Acknowledge - With Detail and Change
- AD
- Acknowledge - With Detail, No Change
- RJ
- Rejected - No Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
External Information: This field needs to contain the Zappos PO number.
PO Acknowledgments with missing, incomplete, or invalid PO numbers will fail and cannot be processed by Zappos.
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
External Information: This field will be the PO acknowledgment date.
Product Type
To specify identifying information
PO Acknowledgments with missing REF segments will fail and cannot be processed by Zappos.
Sample Data:
REFPRTAP
Code qualifying the Reference Identification
- PRT
- Product Type
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This is a Zappos provided value that uniquely identifies each product line in the Zappos internal system.
- AC
- Accessories
- AP
- Apparel
- BE
- Beauty
- BL
- Bags or Luggage
- EL
- Electronics
- FW
- Footwear
- HA
- Hats
- HO
- Hosiery
- HW
- Housewares
- JE
- Jewelry
- PC
- Personal Care
Vendor ID Number
To specify identifying information
PO Acknowledgments with missing REF segments will fail and cannot be processed by Zappos.
Sample Data:
REFVR4321
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Where REF01 = "VR", Vendor ID Number - used to uniquely identify individual brands in the Zappos system. This number is assigned by Zappos.
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- A
- Allowance
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- C310
- Discount
- D500
- Handling
Monetary amount
- SAC05 is the total amount for the service, promotion, allowance, or charge.
- If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Code indicating on what basis allowance or charge percent is calculated
- 1
- Item List Cost
- 2
- Item Net Cost
- 3
- Discount/Gross
- 4
- Discount/Net
- 5
- Base Price per Unit
- 6
- Base Price Amount
Rate expressed in the standard monetary denomination for the currency specified
- SAC08 is the allowance or charge rate per unit.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Numeric value of quantity
- SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
- SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
- In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
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
Sample Data::
ITD14360NET
Code identifying type of payment terms
- If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
- 14
- Previously agreed upon
Code identifying the beginning of the terms period
- 3
- Invoice Date
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Number of days in the terms discount period by which payment is due if terms discount is earned
Number of days until total invoice amount is due (discount not applicable)
A free-form description to clarify the related data elements and their content
Cancel After
To specify pertinent dates and times
The latest date that Zappos expects the shipment to be delivered to the Amazon.com KYDC listed on the purchase order.
The seller may request a change to the entire order with a BAK02 type of AC (Acknowledge - With Detail and Change) and updating the date information in the DTM segment. Only the start ship date should be requested to be changed. Zappos can only accept a header level date change.
Sample Data:
DTM01020110916
Requested Ship
To specify pertinent dates and times
The earliest date that Zappos expects the shipment to be delivered to the Amazon.com KYDC listed on the purchase order.
The seller may request a change to the entire order with a BAK02 type of AC (Acknowledge - With Detail and Change) and updating the date information in the DTM segment. Only the start ship date should be requested to be changed. Zappos can only accept a header level date change.
Sample Data:
DTM01020110916
Name
To identify a party by type of organization, name, and code
Sample Data::
N1STZAPPOS MERCHANDISING LLC920001
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)
- 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.
0001 - 376 Zappos.com Blvd. Shepherdsville KY, 40165
0002 - 280 Omega Pkwy, Shepherdsville KY, 40165
Additional Name Information
To specify additional names or those longer than 35 characters in length
Sample Data:
N2*C/O AMAZON.COM KYDC LLC.
Address Information
To specify the location of the named party
Sample Data:
N3376 ZAPPOS.COM BLVD.
N3FTZ#029, SITE 6
Geographic Location
To specify the geographic place of the named party
Sample Data:
N4SHEPHERDSVILLEKY40165US
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
PO1 is required when BAK02 = "AC" or "AD".
PO1 not used when BAK02 = "RJ".
PO Acknowledgments with a BAK02 of “AC” or “AD” but are missing PO1 segments will fail and cannot be processed by Zappos.
Sample Data:
PO116EA18.90WEUP801234567891PIZZZ-9876543VA*7607
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- WE
- Wholesale 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.
Either “UP” or “EN” product will be sent, and must be returned on the 855 document.
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PI
- Purchaser's Item Code
- VA
- Vendor's Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PI
- Purchaser's Item Code
- VA
- Vendor's Style Number
Identifying number for a product or service
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
- 91
- Buyer's Item Size Description
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
If PO1 segment present, then ACK segment must also be present.
If ACK01 = IQ, ACK02 and 03 are required.
If ACK01 = IP, new price for this item must be sent in PO104.
If ACK01 = R2, this indicates either the item numbers provided on the 850 are wrong or the supplier does not recognize what is being ordered. If incorrect Vendor Style or UPC/EAN number, then use this code and provide the corrected number in the PO1 segment.
If an item is not available for shipment within the requested shipping window, the seller may request a change to the entire order with a BAK02 type of AC (Acknowledge - With Detail and Change) and updating the date information in the DTM segment or the seller may cancel the item from the current order and contact Zappos to request a separate PO for that item with a later shipping window.
Sample Data:
ACK*IA
Code specifying the action taken by the seller on a line item requested by the buyer
- IA
- Item Accepted
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
- IR
- Item Rejected
- R2
- Item Rejected, Invalid Item Product Number
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Summary
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.