X12 850 Purchase Order
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) 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 the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
- ~ 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
- ZZ
- Mutually Defined
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
- PO
- Purchase Order (850)
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).
- 850
- Purchase Order
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
To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
Standard Shipments will be denoted with "SA"
Pre-buy orders will be denoted with "BK"
ZPS invoice POs will be denoted with "KA" (Only applies to vendors actively
enrolled in the Zulily Triple Z program)
- BK
- Blanket Order (Quantity Firm)
- KA
- Agreement
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
ZULILY PO NUMBER
Formatting Notes: All Zulily purchase order IDs are a 12-13 character
string.
All POs requiring a shipment begin with "P0"
ZPS Invoice POs not requiring shipments begin with "45" (Triple Z vendors
ONLY)
Date expressed as CCYYMMDD
- BEG05 is the date assigned by the purchaser to purchase order.
PO DATE
YYYYMMDD
Code defining the method by which invoices are to be processed
- IEL
- Invoice Electronically
- INR
- Invoice Not Required (Such As Evaluated Receipts Settlements)
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code (Standard ISO) for country in whose currency the charges are specified
Zulily used currency codes will be either "USD" or "CAD"
Reference Identification
To specify identifying information
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
ZULILY VENDOR REFERENCE NUMBER
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
Sales Requirements
To specify general conditions or requirements of the sale
Code to identify a specific requirement or agreement of sale
- N
- No Back Order
Code specifying type of date or time, or both date and time
- 001
- Cancel After
Date expressed as CCYYMMDD
PO Cancel Date.
Note: Purchase Order units may still be shipped to Zulily after this date
unless previously specified. Units will be deemed "Late".
YYYYMMDD
Code specifying type of date or time, or both date and time
- 037
- Ship Not Before
Date expressed as CCYYMMDD
Start of ship window.
Note: Will typically be same date of PO cut unless otherwise specified.
YYYYMMDD
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
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.
Please reference the ZULILY FC Address List included in this on-boarding package
Zulily, Inc - HQ = 0000
Note: Billing will always be Zulily Corporate for FC & ZPS Purchase Orders
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
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)
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Free-form name
Will reference the ZULILY FC where the PO will be shipped
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.
Please reference the ZULILY FC Address List included in this on-boarding
package
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
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.
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
Currently, we only support 'EA' as a unit of measure
- EA
- Each
Price per unit of product, service, commodity, etc.
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.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Will always be an integer of 12-13 characters
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Identifying number for a product or service
Value represents Zulily internal product ID.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- GS
- General Specification Number
Identifying number for a product or service
Value represents Zulily PO line item number.
Note: will only be provided when BEG02 = 'KA' for ZPS POs.
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
Number of line items in PO - sum of the PO101 elements
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.
Sum of all PO102 elements - Total Number of items ordered on PO.
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
Zulily Purchase Order
GS*PO*ZVDXPROD*123456789*20151231*1035*000000012*X*004010~
ST*850*0001~
BEG*00*SA*P000GAOUES8V**20230320~
REF*VR*1515~
FOB*CC~
CSH*N~
DTM*038*20230322~
DTM*037*20230320~
DTM*010*20230320~
DTM*001*20230322~
N1*BT*Zulily LLC*92*0000~
N3*2601 Elliott Ave~
N4*Seattle*WA*98121*US~
N1*ST*Zulily LLC - OH*92*0004~
N3*3051 Creekside Pkwy~
N4*Lockbourne*OH*43194*US~
PO1*00001*1*EA*25.00**UP*825076729019*SK*SAGA*IN*113088943~
PO1*00002*1*EA*25.00**UP*825076679536*SK*LUNA*IN*113095510~
CTT*2*2~
SE*19*0001~
GE*1*000000012~
IEA*1*683509995~
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.