Skip to content
EDI Rehlko Rehlko Generator 850
X12 EDI

Rehlko X12 850 Purchase Order

X12 850 (Purchase Order) is the EDI transaction exchanged between Rehlko (Rehlko Generator) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
6
Loops
1
X12 850
All partners ↗
Book a demo ← All Rehlko Generator transactions

Transaction context

Where 850 Purchase Order fits on Rehlko Generator

On Rehlko Generator, the X12 850 Purchase Order precedes the 855 Purchase Order Acknowledgment, 856 Ship Notice Manifest and 810 Invoice in the Order-to-cash cycle.

Rehlko channels
1 of 2

1 of Rehlko's 2 channels carries 850

Trading partners
389

partners across the Stacksync network trade 850

Channels
516

channels network-wide carry 850

Most common alongside 850

The 850 is the electronic purchase order a buyer sends to formally request goods or services, carrying items, quantities, prices, ship-to locations, and requested dates. It initiates the order-to-cash cycle and is the reference document that the acknowledgment (855), ship notice (856), and invoice (810) must reconcile against. Trading partners require it because a machine-readable PO removes manual re-keying and the wrong-item, wrong-quantity errors that come with it. Sent by the buyer (retailer, distributor, or manufacturer procurement) to the supplier or vendor fulfilling the order.

When it fires: A buyer's procurement or replenishment system releases an approved order for goods to a specific supplier.

Common 850 rejection causes
  • Ship-to addresses or location codes that do not exist in the seller's system, causing the order to fail validation or ship to the wrong warehouse.
  • Item identifiers referencing discontinued SKUs or UPCs that do not match the seller's catalog, forcing manual intervention.
  • PO line prices that do not match the agreed contract price in the seller's system, triggering business-level rejection on the 855.
  • Missing or malformed mandatory segments or data elements, rejected on receipt via the 997, and duplicate PO numbers that confuse order processing.

Specification summary

X12 850 Purchase Order at the element level

The X12 850 specification defines 71 segments carrying 282 data elements, 84 of which are mandatory.

Segments
71
Data elements
282
Mandatory elements
84
Segments with mandatory elements
Segment Elements Mandatory
BEG 5 4
CUR 5 2
REF 3 1
FOB 7 1
SAC 11 1
DTM 4 1
PID 4 1
TXI 8 1
N9 3 1
MSG 2 1
Key identifiers in 850
  • Transaction Set Purpose Code
  • Purchase Order Type Code
  • Purchase Order Number
  • Date
  • Entity Identifier Code
  • Currency Code
  • Reference Identification Qualifier
  • Shipment Method of Payment
Full segment guideline — 6 segments 1 loop · X12 850 Purchase Order
ISA Interchange Control Header 16 elements

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

GS Functional Group Header 8 elements

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

ST Transaction Set Header 2 elements

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

BEG Beginning Segment for Purchase Order 4 elements

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

PO1 Loop Repeat: 100,000
PO1 Baseline Item Data 1 element

To specify basic and most frequently used line item data

SE Transaction Set Trailer 2 elements

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

Trading partners

3+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Browse the full directory

Rehlko Rehlko Generator EDI 850 FAQ

Common questions about 850 Purchase Order on the Rehlko Generator channel.

What is X12 850 Purchase Order?
X12 850 (Purchase Order) is the EDI transaction set used to exchange purchase order data. Rehlko's Rehlko Generator channel requires it from trading partners.
Does Rehlko Rehlko Generator require 850 for trading partners?
Yes, Rehlko (Rehlko Generator) supports X12 850 Purchase Order. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Rehlko 850 with Stacksync?
Most companies go live with Rehlko 850 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 850 on Rehlko Generator?
On Rehlko Generator, X12 850 is typically exchanged alongside 810 Invoice, 856 Ship Notice Manifest, 855 Purchase Order Acknowledgment. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.

Ready to automate your Rehlko EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a Rehlko EDI demo Tour the platform on your own