Skip to content
X12 EDI

Target X12 865 Purchase Order Change Acknowledgment/Request - Seller Initiated

X12 865 (Purchase Order Change Acknowledgment/Request - Seller Initiated) is the EDI transaction exchanged between Target (Target Direct Vendor Ship) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
9
Loops
3
X12 865
All partners ↗

Transaction context

Where 865 Purchase Order Change Acknowledgment/Request - Seller Initiated fits on Target Direct Vendor Ship

Target channels
1 of 4

1 of Target's 4 channels carries 865

Trading partners
12

partners across the Stacksync network trade 865

Channels
12

channels network-wide carry 865

This is the seller-initiated use of the 865 transaction set. Instead of acknowledging a buyer's 860, the supplier proposes its own changes to an open purchase order, such as revised delivery dates, adjusted quantities, or updated prices. Buyers require it so supply-side changes enter the order of record through EDI rather than email or phone, keeping the purchase order version both parties fulfill against consistent. The supplier sends it unprompted to the buyer to request or notify changes to a purchase order the buyer previously placed.

When it fires: A supplier determines it cannot fulfill an open order as written, for example a stockout, a price update, or a slipped ship date, and issues an 865 proposing the change.

Common 865 rejection causes
  • Transaction Set Purpose Code set incorrectly, so the buyer's system processes a seller-initiated change request as an acknowledgment of a change it never sent.
  • Change requests referencing purchase orders the buyer has already closed, received, or invoiced, which the buyer's system rejects or ignores.
  • Restated line values that conflict with the buyer's current version of the purchase order, surfacing later as ASN or invoice discrepancies.
  • Missing original purchase order number, leaving the buyer unable to match the request to an open order.

Specification summary

X12 865 Purchase Order Change Acknowledgment/Request - Seller Initiated at the element level

The X12 865 specification defines 21 segments carrying 72 data elements, 40 of which are mandatory.

Segments
21
Data elements
72
Mandatory elements
40
Segments with mandatory elements
Segment Elements Mandatory
BCA 4 3
REF 2 1
N9 2 1
MSG 1 1
POC 12 1
PID 2 1
ACK 15 1
DTM 3 1
CTT 1 1
Key identifiers in 865
  • Transaction Set Purpose Code
  • Purchase Order Number
  • Date
  • Reference Identification Qualifier
  • Free-Form Message Text
  • Change or Response Type Code
  • Item Description Type
  • Line Item Status Code
Full segment guideline — 9 segments 3 loops · X12 865 Purchase Order Change Acknowledgment/Request - Seller Initiated
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

BCA Beginning Segment for Purchase Order Change Acknowledgment 4 elements

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

REF Reference Identification 2 elements

To specify identifying information

POC Loop Repeat: 104
POC Line Item Change 11 elements

To specify changes to a line item

ACK Loop Repeat: 104
ACK Line Item Acknowledgment 5 elements

To acknowledge the ordered quantities and specify the ready date for a specific line item

CTT Loop Repeat: 1
CTT Transaction Totals 1 element

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

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

7+ 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.

Target Target Direct Vendor Ship EDI 865 FAQ

Common questions about 865 Purchase Order Change Acknowledgment/Request - Seller Initiated on the Target Direct Vendor Ship channel.

What is X12 865 Purchase Order Change Acknowledgment/Request - Seller Initiated?
X12 865 (Purchase Order Change Acknowledgment/Request - Seller Initiated) is the EDI transaction set used to exchange purchase order change acknowledgment/request - seller initiated data. Target's Target Direct Vendor Ship channel requires it from trading partners.
Does Target Target Direct Vendor Ship require 865 for trading partners?
Yes, Target (Target Direct Vendor Ship) supports X12 865 Purchase Order Change Acknowledgment/Request - Seller Initiated. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Target 865 with Stacksync?
Most companies go live with Target 865 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 865 on Target Direct Vendor Ship?
On Target Direct Vendor Ship, X12 865 is typically exchanged alongside 855 Purchase Order Acknowledgment, 856 Ship Notice Manifest, 850 Purchase Order, 860 Purchase Order Change Request Buyer Initiated. 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 Target EDI?

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