.png){kind=small}
ISA Interchange Control Header
Food52 X12 860 Purchase Order Change Request
X12 860 (Purchase Order Change Request) is the EDI transaction exchanged between Food52 and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 18
- Loops
- 6
- X12 860
- All partners ↗
Schema reference
18 segments · 6 loops · X12 860 Purchase Order Change Request
GS Functional Group Header
Transaction Set Header
Beginning Segment for Purchase Order Change
Currency
Reference Information
Loop
Service, Promotion, Allowance, or Charge Information
Date/Time Reference
Carrier Details (Routing Sequence/Transit Time)
Loop
Extended Reference Information
Text
Loop
Party Identification
Party Location
Geographic Location
Loop
Line Item Change
Loop
Product/Item Description
Loop
Transaction Totals
Transaction Set Trailer
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.
No trading partner matches your search.
Browse the full directory
Food52 EDI 860 FAQ
Common questions about 860 Purchase Order Change Request with Food52.
What is X12 860 Purchase Order Change Request?
X12 860 (Purchase Order Change Request) is the EDI transaction set used to exchange purchase order change request data. Food52 requires it from trading partners.
Does Food52 require 860 for trading partners?
Yes — Food52 supports X12 860 Purchase Order Change Request. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Food52 860 with Stacksync?
Most companies go live with Food52 860 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your Food52 EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.