Skip to content
EDI Google 865
X12 Inbound

Google X12 865 Purchase Order Change Acknowledgment/Request

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

Segments
15
Loops
6
X12 865
All partners ↗

Schema reference

15 segments · 6 loops · X12 865 Purchase Order Change Acknowledgment/Request

ISA

ISA Interchange Control Header

GS

GS Functional Group Header

ST

Transaction Set Header

BCA

Beginning Segment for Purchase Order Change Acknowledgment

REF

Reference Identification

Loop
N9

Reference Identification

MSG

Message Text

Loop
POC

Line Item Change

Loop
PID

Product/Item Description

Loop
ACK

Line Item Acknowledgment

DTM

Date/Time Reference

Loop
N9

Reference Identification

MSG

Message Text

Loop
CTT

Transaction Totals

SE

Transaction Set Trailer

Trading partners

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

Google EDI 865 FAQ

Common questions about 865 Purchase Order Change Acknowledgment/Request with Google.

What is X12 865 Purchase Order Change Acknowledgment/Request?
X12 865 (Purchase Order Change Acknowledgment/Request) is the EDI transaction set used to exchange purchase order change acknowledgment/request data. Google requires it from trading partners.
Does Google require 865 for trading partners?
Yes — Google supports X12 865 Purchase Order Change Acknowledgment/Request. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Google 865 with Stacksync?
Most companies go live with Google 865 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.

Ready to automate your Google EDI?

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