X12
Inbound

Mountain High Outfitters X12 850 Purchase Order

Mountain High Outfitters (via SPS Commerce)
The EDI 850 Purchase Order is Mountain High Outfitters's primary document for placing orders with suppliers. It contains item details, quantities, pricing, shipping instructions, and delivery windows. Suppliers must acknowledge and fulfill these orders according to Mountain High Outfitters's compliance requirements.
18segments
5loops
6mandatory

Schema Reference

18 segments · X12 850 Purchase Order

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 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 ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Interchange Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BEG Beginning Segment for Purchase Order
Mandatory Max: 1
BEG01 Transaction Set Purpose Code
M ID 2-2
BEG02 Purchase Order Type Code
M ID 2-2
BEG03 Purchase Order Number
M AN 1-22
BEG05 Date
M DT 8-8
REF Reference Information
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
PER Administrative Communications Contact
Optional Max: 3
PER01 Contact Function Code
M ID 2-2
PER02 Name
O AN 1-60
PER03 Communication Number Qualifier
C ID 2-2
PER04 Communication Number
C AN 1-256
ITD Terms of Sale/Deferred Terms of Sale
ITD12 Description
O AN 1-80
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
N9 Loop Repeat: 1,000
N9 Extended Reference Information
Optional Max: 1
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-50
MTX Text
MTX02 Textual Data
C AN 1-4096
N1 Loop Repeat: 200
N1 Party Identification
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
N2 Additional Name Information
Optional Max: 2
N201 Name
M AN 1-60
N3 Party Location
Optional Max: 2
N301 Address Information
M AN 1-55
N4 Geographic Location
N401 City Name
O AN 2-30
N402 State or Province Code
C ID 2-2
N403 Postal Code
O ID 3-15
N404 Country Code
C ID 2-3
PO1 Loop Repeat: 100,000
PO1 Baseline Item Data
Mandatory Max: 1
PO101 Assigned Identification
O AN 1-20
PO102 Quantity
C R 1-15
PO103 Unit or Basis for Measurement Code
O ID 2-2
PO104 Unit Price
C R 1-17
PO106 Product/Service ID Qualifier
C ID 2-2
PO107 Product/Service ID
C AN 1-48
PO108 Product/Service ID Qualifier
C ID 2-2
PO109 Product/Service ID
C AN 1-48
PO110 Product/Service ID Qualifier
C ID 2-2
PO111 Product/Service ID
C AN 1-48
PID Loop Repeat: 1,000
PID Product/Item Description
Optional Max: 1
PID01 Item Description Type
M ID 1-1
PID02 Product/Process Characteristic Code
O ID 2-3
PID05 Description
C AN 1-80
CTT Loop Repeat: 1
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
M N0 1-6
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Mountain High Outfitters EDI 850

Stacksync validates, transforms, and delivers your 850 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync automatically syncs incoming Mountain High Outfitters 850 Purchase Orders directly to your ERP or database. New orders appear in your system within seconds — no manual data entry, no CSV imports. Field mappings are configured once and every future PO flows through automatically.

Business unit variations

Mountain High Outfitters 2 (via SPS Commerce)
Stacksync automatically syncs incoming Mountain High Outfitters 850 Purchase Orders directly to your ERP or database. New orders appear in your system within seconds — no manual data entry, no CSV imports. Field mappings are configured once and every future PO flows through automatically.

Mountain High Outfitters EDI 850 FAQ

Common questions about 850 Purchase Order transactions with Mountain High Outfitters.

What information does Mountain High Outfitters include in an EDI 850 Purchase Order?

Mountain High Outfitters EDI 850 Purchase Orders contain item-level detail including UPCs or GTINs, ordered quantities, unit pricing, ship-to addresses, and requested delivery dates. Key segments like BEG (beginning of the PO), PO1 (line items), N1 (party identification), and CTT (transaction totals) structure the document. Mountain High Outfitters sends 850s electronically through their EDI network, and each PO must be acknowledged with an 855 to confirm receipt. Stacksync parses these fields and maps them directly to your ERP or database so orders appear automatically without manual data entry or CSV imports.

How quickly does Stacksync process Mountain High Outfitters EDI 850 Purchase Orders?

Stacksync processes incoming Mountain High Outfitters 850 Purchase Orders in real time, typically within seconds of receipt. The platform validates the X12 envelope, parses all segments, maps fields to your system's schema, and inserts the order record automatically. Unlike batch-processing EDI providers that run on scheduled intervals, Stacksync's event-driven architecture means your team sees new Mountain High Outfitters POs immediately. This speed is critical for meeting Mountain High Outfitters's tight fulfillment windows and maintaining high on-time in-full compliance scores.

What are common reasons a Mountain High Outfitters EDI 850 Purchase Order gets rejected?

The most frequent rejection causes for Mountain High Outfitters 850s include invalid UPC or GTIN codes, incorrect ship-to location identifiers, quantities that don't match Mountain High Outfitters's rounding requirements, and missing mandatory segments. Formatting issues like incorrect date formats in the DTM segment or invalid N1 qualifier codes also trigger rejections. Stacksync validates every incoming Mountain High Outfitters 850 against known compliance requirements before syncing to your system, flagging anomalies immediately rather than silently dropping the transaction.

Do I need to send an EDI 855 after receiving a Mountain High Outfitters 850 Purchase Order?

Mountain High Outfitters typically requires an EDI 855 Purchase Order Acknowledgment for every 850 received. The 855 confirms that you received the PO and indicates whether you can fulfill it as ordered, need to modify quantities, or must reject specific line items. Most Mountain High Outfitters compliance programs expect the 855 within 24 to 48 hours of PO receipt. Stacksync can generate and send 855 acknowledgments automatically based on your acceptance rules, ensuring you never miss a compliance deadline. A 997 Functional Acknowledgment may also be required as a separate technical receipt.

How does Stacksync map Mountain High Outfitters EDI 850 fields to my ERP system?

Stacksync uses a visual field mapping interface to connect Mountain High Outfitters 850 segments — such as BEG for PO header data, PO1 for line items, and N1 for party identification — to the corresponding fields in your ERP, WMS, or database. You configure the mapping once, and Stacksync applies it to every subsequent Mountain High Outfitters 850 automatically. The platform handles data type conversions, conditional logic for optional fields, and Mountain High Outfitters-specific formatting requirements. If Mountain High Outfitters changes their 850 specification, Stacksync alerts you and suggests mapping updates.

Ready to automate Mountain High Outfitters EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding