.png){kind=small}
ISA Interchange Control Header
BJ's Wholesale Club X12 850 Purchase Order
X12 850 (Purchase Order) is the EDI transaction exchanged between BJ's Wholesale Club and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 17
- Loops
- 4
- X12 850
- All partners ↗
Schema reference
17 segments · 4 loops · X12 850 Purchase Order
GS Functional Group Header
Transaction Set Header
Beginning Segment for Purchase Order
Reference Identification
Date/Time Reference
Carrier Details (Routing Sequence/Transit Time)
Loop
Name
Address Information
Geographic Location
Administrative Communications Contact
Loop
Baseline Item Data
Loop
Product/Item Description
Date/Time Reference
Carrier Details (Routing Sequence/Transit Time)
Loop
Transaction Totals
Transaction Set Trailer
Trading partners
4+ 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
BJ's Wholesale Club EDI 850 FAQ
Common questions about 850 Purchase Order with BJ's Wholesale Club.
What is X12 850 Purchase Order?
X12 850 (Purchase Order) is the EDI transaction set used to exchange purchase order data. BJ's Wholesale Club requires it from trading partners.
Does BJ's Wholesale Club require 850 for trading partners?
Yes — BJ's Wholesale Club supports X12 850 Purchase Order. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate BJ's Wholesale Club 850 with Stacksync?
Most companies go live with BJ's Wholesale Club 850 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your BJ's Wholesale Club EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.