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
- 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
- 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
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
- RE
- Reorder
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
The IA and X9 qualifiers are always used
- CO
- Customer Order Number
Customer's order number w/merchant (REF02). Customer PO Index (REF03)
- DP
- Department Number
Merchant's department/site id
- IA
- Internal Vendor Number
Merchant assigned vendor number
- MR
- Merchandise Type Code
Indicates that this is a Site to Store order
- PQ
- Payee Identification
Payment type.
- X9
- Internal Control Number
CommerceHub internal ID
Sales Requirements
To specify general conditions or requirements of the sale
Code to identify a specific requirement or agreement of sale
- P2
- Ship As Soon As Possible
Monetary amount
- CSH03 is the maximum monetary amount value which the order must not exceed.
Expected Processing Priority flag.
Numeric rank to be used as a factor in determining the order in which fulfillment work is released to the fulfillment operation on a given day.
The work from Orders with a higher rank should be released ahead of the work from Orders with a lower rank. The work from Orders where this element is not present ranks lowest.
NOTE: This segment will only be present if this is an Expected Processing Priority order
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.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- ZZZZ
- Mutually Defined
Order total
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.
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 004
- Purchase Order
Will only be present if the partner is configured to receive full date/time/offset values. The Purchase Order date will always be sent in the BEG05
- 006
- Sold
Customer order date/time.
- 069
- Promised for Delivery
If 069 is sent please arrange to have item delivered on this date/time.
Date expressed as CCYYMMDD
Depending on the qualifier used this element contains the corresponding value.
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
See HubEDI User Guide.pdf for interpretation of time codes.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
The Shipping Code used here is drawn from a specific list. Your Vendor Implementation Representative can supply the specific list of codes for you to map from here and for your 856. Please note that Walmart uses multiple carries and determines the best carrier based on several requirements. You may be asked to ship via UPS, FedEx, DHL, or USPS as well as LTL. Also note that if your shipment has fallen outside the agreed upon window and you have to upgrade the service to meet customer expectation you cannot bill the shipping to a Walmart account.
For your list of codes please ask your Vendor Implementation Representative
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
The ST qualifier will always be used
- BT
- Bill-to-Party
- ST
- Ship To
Free-form name
The N1 segment contains the full name for the party. If the first and last names are reported separately, they will be found in the N2 segment.
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
Code 93 is used for ship to store orders
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.
Store Number
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)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
USED TO ASSOCIATE A COMPANY NAME, TELEPHONE NUMBER AND/OR E-MAIL ADDRESS WITH N1 ENTITY
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
Used for primary instance of PER segment in N1 loop.
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
This will contain the telephone number if it is sent in the original PO.
Code identifying the type of communication number
- EM
- Electronic Mail
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.
Merchant's PO line number.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Unit cost the merchant expects to be billed for each unit fulfilled.
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.
- SK
- Stock Keeping Unit (SKU)
This is Walmart.com's SKU for the item
Identifying number for a product or service
Merchant's SKU code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
This is your SKU for the item.
Identifying number for a product or service
Vendor's product SKU
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
This is the UPC code for the item.
Identifying number for a product or service
"The UPC that may be included on the order from Walmart.com will not be identical to the GS1-compliant UPC that you have loaded into the CommerceHub inventory system. The UPC value that may be listed by Walmart.com on the PO is the Walmart.com-adjusted value."
Pricing Information
To specify pricing information
This is the retail price of the item to the customer and is used for the pack slip. If the price isn't sent it is one of the identifiers that this is a Gift Order
Code identifying pricing specification
- RES
- Resale
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
Reference Identification
To specify identifying information
The REF*CS contains data that is used to create a bar code for returns on the packslip if you are creating them.
Code qualifying the Reference Identification
- CS
- Condition of Sale Document Number
Reference number for use w/ in-store returns
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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
The SAC contains pricing information and additional charges for the customer.
This is generally used for packslip generation. If this data is empty it may be used to identify this order as a Gift Order.
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.
- C
- Charge
- S
- Service
Special processing/handling information
Code identifying the service, promotion, allowance, or charge
- F150
- Packaging Service
Gift wrap control
- G821
- Shipping
- H151
- Special Services
Gift processing
- H850
- Tax
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.
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.
If SAC-02 = F150, then ID of gift registry list to which product belongs.
A free-form description to clarify the related data elements and their content
- If SAC-02 = F050 then packslip message
- If SAC-02 = F991 then processing message
- If SAC-02 = H151 then gift message
- Otherwise, optional description of charge or allowance
Date/Time Reference
To specify pertinent dates and times
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
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.
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
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.