.png){kind=small}
ISA Interchange Control Header
CVS X12 850 Purchase Order
X12 850 (Purchase Order) is the EDI transaction exchanged between CVS and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 21
- Loops
- 7
- X12 850
- All partners ↗
Schema reference
21 segments · 7 loops · X12 850 Purchase Order
GS Functional Group Header
Transaction Set Header
Beginning Segment for Purchase Order
Reference Identification
Administrative Communications Contact
Loop
Service, Promotion, Allowance, or Charge Information
Terms of Sale/Deferred Terms of Sale
Date/Time Reference
Loop
Monetary Amount
Loop
Reference Identification
Message Text
Loop
Name
Address Information
Geographic Location
Loop
Baseline Item Data
Period Amount
Loop
Product/Item Description
Item Physical Details
Loop
Transaction Totals
Transaction Set Trailer
Trading partners
6+ 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.
PU Purchase Order Change Request CR Credit/Debit Adjustment SH Ship Notice/Manifest AP Application Advice PL Planning Schedule with Release Capability IN Invoice
No trading partner matches your search.
Browse the full directory
CVS EDI 850 FAQ
Common questions about 850 Purchase Order with CVS.
What is X12 850 Purchase Order?
X12 850 (Purchase Order) is the EDI transaction set used to exchange purchase order data. CVS requires it from trading partners.
Does CVS require 850 for trading partners?
Yes — CVS supports X12 850 Purchase Order. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate CVS 850 with Stacksync?
Most companies go live with CVS 850 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your CVS EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.