Skip to content
EDI Trinchero Family Estates (TFE) Trinchero Wines 850
X12 EDI

Trinchero Family Estates (TFE) X12 850 Purchase Order

X12 850 (Purchase Order) is the EDI transaction exchanged between Trinchero Family Estates (TFE) (Trinchero Wines) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
18
Loops
5
X12 850
All partners ↗
Book a demo ← All Trinchero Wines transactions

Transaction context

Where 850 Purchase Order fits on Trinchero Wines

Trinchero Family Estates (TFE) channels
1 of 1

1 of Trinchero Family Estates (TFE)'s 1 channel 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 — 18 segments 5 loops · 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

FOB F.O.B. Related Instructions 7 elements

To specify transportation instructions relating to shipment

DTM Date/Time Reference 2 elements

To specify pertinent dates and times

TD5 Carrier Details (Routing Sequence/Transit Time) 6 elements

To specify the carrier and sequence of routing and provide transit time information

N9 Loop Repeat: 1,000
N9 Extended Reference Information 2 elements

To transmit identifying information as specified by the Reference Identification Qualifier

MTX Text 2 elements

To specify textual data

N1 Loop Repeat: 200
N1 Party Identification 4 elements

To identify a party by type of organization, name, and code

N3 Party Location 1 element

To specify the location of the named party

N4 Geographic Location 4 elements

To specify the geographic place of the named party

PO1 Loop Repeat: 100,000
PO1 Baseline Item Data 8 elements

To specify basic and most frequently used line item data

PID Loop Repeat: 1,000
PID Product/Item Description 3 elements

To describe a product or process in coded or free-form format

PO4 Item Physical Details 4 elements

To specify the physical qualities, packaging, weights, and dimensions relating to the item

CTT Loop Repeat: 1
CTT Transaction Totals 4 elements

To transmit a hash total for a specific element in the transaction set

AMT Monetary Amount Information 2 elements

To indicate the total monetary amount

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)

Trinchero Family Estates (TFE) Trinchero Wines EDI 850 FAQ

Common questions about 850 Purchase Order on the Trinchero Wines channel.

What is X12 850 Purchase Order?
X12 850 (Purchase Order) is the EDI transaction set used to exchange purchase order data. Trinchero Family Estates (TFE)'s Trinchero Wines channel requires it from trading partners.
Does Trinchero Family Estates (TFE) Trinchero Wines require 850 for trading partners?
Yes, Trinchero Family Estates (TFE) (Trinchero Wines) supports X12 850 Purchase Order. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Trinchero Family Estates (TFE) 850 with Stacksync?
Most companies go live with Trinchero Family Estates (TFE) 850 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.

Ready to automate your Trinchero Family Estates (TFE) EDI?

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

Book a Trinchero Family Estates (TFE) EDI demo Tour the platform on your own