PlainEDI
EDI 850 Converter • Updated October 2025

EDI 850 Purchase Order
to CSV Converter

Convert EDI 850 Purchase Orders to CSV format instantly. The 850 transaction set is used by buyers to send purchase orders to suppliers, containing item details, quantities, prices, delivery dates, and shipping information.

Convert 850 to CSV Free

No signup required

Last updated: January 22, 2025

TL;DR

Convert EDI 850 Purchase Orders to CSV format instantly. PlainEDI converts EDI 850 files to CSV instantly (typically under 30 seconds). Upload your file, preview free, then export for $9 (single file) or $3.90/file (10-pack). Supports all major retailers including Walmart, Target, Amazon, Home Depot, and more. No software installation required.

Why Convert EDI 850 to CSV?

Convert 850 EDI files to CSV for easy analysis, import into ERP systems, or reconciliation in Excel.

Process purchase orders from major retailers like Walmart, Target, and Amazon

Import PO data into ERP systems (SAP, Oracle, NetSuite)

Reconcile ordered quantities and pricing against invoices

Track delivery dates and shipping requirements

Automate order entry workflows and reduce manual data entry

Validate PO data before sending acknowledgments

What Data is Extracted from EDI 850?

Our parser extracts all standard 850 segments and elements into clean CSV columns you can open in Excel:

PO Number (BEG03) - Unique purchase order identifier
Order Date (BEG05) - Date the order was created
Line Number (PO101) - Sequential line item number
Item Number/SKU (PO107) - Product identifier
Quantity Ordered (PO102) - Number of units ordered
Unit Price (PO104) - Price per unit
Product Description (PID05) - Item description
Delivery Date (DTM02) - Requested delivery date
Ship-To Address (N1/N3/N4) - Destination location

How to Convert EDI 850 to CSV in 3 Steps

1

Upload Your 850 File

Drop your EDI 850 file (.edi, .txt, or .x12) into our converter. Supports files up to 10MB. Processing is instant.

2

Preview Your Data Free

See a summary, validation results, and the first 10 rows of CSV data. Verify accuracy before exporting. No credit card required.

3

Export Full CSV

Pay only when ready to export. Download your complete CSV file instantly. Open in Excel or import to ERP.

Start Converting 850 Files →

Process EDI 850 from Any Major Retailer

PlainEDI handles 850 files from all 10 major retailers we support:

Walmart

850 →

Target

850 →

Amazon

850 →

Home Depot

850 →

Lowe's

850 →

Costco

850 →

Best Buy

850 →

AutoZone

850 →

Albertsons

850 →

Kroger

850 →

Understanding EDI 850 Segment Structure

EDI 850 files follow a hierarchical structure defined by the X12 standard. Understanding these segments helps you interpret purchase order data accurately.

BEGBeginning Segment for Purchase Order

The BEG segment appears once per purchase order and contains the PO number, order type, PO date, and release number.

BEG*00*SA*PO123456**20250115
  • BEG01 (00): Transaction Set Purpose Code - 00 = Original
  • BEG02 (SA): Purchase Order Type - SA = Stand Alone Order
  • BEG03 (PO123456): Purchase Order Number - Your primary reference
  • BEG05 (20250115): Date - Order date in YYYYMMDD format

REFReference Identification

REF segments provide additional identifiers like department numbers, buyer codes, or vendor IDs. Multiple REF segments can appear.

REF*DP*055
REF*IA*1234567890
  • REF*DP: Department Number (common with Walmart, Target)
  • REF*IA: Internal Vendor Number
  • REF*CO: Customer Order Number
  • REF*ZZ: Mutually Defined reference

PO1Baseline Item Data (Line Items)

Each PO1 segment represents one line item on the purchase order. This is where you find SKUs, quantities, and prices.

PO1*1*100*EA*25.50*PE*UP*012345678905
  • PO101 (1): Line Number
  • PO102 (100): Quantity Ordered
  • PO103 (EA): Unit of Measure - EA=Each, CA=Case, PLT=Pallet
  • PO104 (25.50): Unit Price
  • PO106-107 (UP / 012345678905): Product ID Qualifier and Product ID (UPC)

N1Name and Address Loop

The N1 loop contains party information: ship-to, bill-to, buyer, and seller addresses. Each party has N1 (name), N3 (street address), N4 (city/state/zip).

N1*ST*WALMART DC 6022*92*0078742000015
N3*1850 PLEASANT GROVE BLVD
N4*ROGERS*AR*72758
  • N101 (ST): Entity Identifier - ST=Ship To, BT=Bill To, BY=Buyer
  • N102: Name
  • N103-104: Identification Code Qualifier and Code (e.g., GLN)

DTMDate/Time Reference

DTM segments specify critical dates like delivery dates, ship-not-before dates, and must-arrive-by dates (MABD).

DTM*002*20250125
DTM*010*20250120
  • DTM*002: Delivery Requested Date / Must Arrive By Date (MABD)
  • DTM*010: Ship Not Before Date
  • DTM*063: Ship Not Later Than Date
  • DTM*064: Do Not Deliver After Date

Real EDI 850 Example → CSV Conversion

See how PlainEDI transforms raw EDI segments into clean, Excel-ready CSV columns.

Raw EDI 850 File (Sample)

ISA*00*          *00*          *ZZ*RETAILER123    *ZZ*SUPPLIER456    *250115*1430*U*00401*000000001*0*P*>~
GS*PO*RETAILER123*SUPPLIER456*20250115*1430*1*X*004010~
ST*850*0001~
BEG*00*SA*PO987654**20250115~
REF*DP*055~
REF*IA*VENDOR12345~
DTM*002*20250125~
N1*ST*WALMART DC 6022*92*0078742000015~
N3*1850 PLEASANT GROVE BLVD~
N4*ROGERS*AR*72758~
PO1*1*100*EA*12.99**UP*012345678905~
PID*F****WIDGET PRO 2000 BLUE~
PO1*2*50*EA*24.50**UP*012345678912~
PID*F****WIDGET DELUXE RED~
CTT*2~
SE*15*0001~
GE*1*1~
IEA*1*000000001~

Real X12 structure with ISA/GS envelopes, segment terminators (~), and element separators (*)

PlainEDI CSV Output

PO NumberOrder DateMABD DateDeptLineUPCDescriptionQtyUnit Price
PO9876542025-01-152025-01-250551012345678905WIDGET PRO 2000 BLUE100$12.99
PO9876542025-01-152025-01-250552012345678912WIDGET DELUXE RED50$24.50

Clean spreadsheet format, ready for Excel/ERP import. MABD date highlighted for visibility.

EDI 850 Segment → CSV Column Mapping

EDI SegmentElement PositionCSV Column NameExample Value
BEGBEG03PO NumberPO987654
BEGBEG05Order Date2025-01-15
DTM*002DTM02MABD / Delivery Date2025-01-25
REF*DPREF02Department Number055
REF*IAREF02Vendor NumberVENDOR12345
N1*STN102 + N3 + N4Ship To AddressWALMART DC 6022, ROGERS AR
PO1PO101Line Number1
PO1PO107UPC / Item Number012345678905
PO1PO102Quantity Ordered100
PO1PO104Unit Price12.99
PIDPID05Product DescriptionWIDGET PRO 2000 BLUE

Common EDI 850 Integration Workflows

How businesses use PlainEDI to integrate 850 purchase orders into their operations without expensive EDI software.

Small Vendor: Manual Order Entry

Scenario: You receive 5-10 Walmart 850 POs per day. You don't have an ERP system and manually enter orders into QuickBooks.

Workflow:

  1. Download 850 EDI file from Walmart Retail Link or AS2 inbox
  2. Upload to PlainEDI, get CSV with PO number, items, quantities, prices, MABD date
  3. Open CSV in Excel, review line items
  4. Manually enter each PO into QuickBooks or your fulfillment system
  5. Save CSV for records and future reconciliation against invoices

Time Saved: Reading raw EDI takes 5-10 minutes per PO. CSV conversion takes 30 seconds. You save 4.5 minutes per PO × 10 POs/day = 45 minutes daily.

Mid-Size Distributor: CSV Import to ERP

Scenario: You receive 50-100 EDI 850s daily from multiple retailers. You have NetSuite or SAP but don't want to pay $10K+ for full EDI integration.

Workflow:

  1. Batch convert all daily 850 files to CSV using PlainEDI unlimited plan ($99/mo)
  2. Use Excel/Python script to merge CSVs and add required ERP fields
  3. Import CSV into NetSuite using SuiteScript or native CSV import
  4. Automated workflow triggers: inventory check, fulfillment assignment, 855 acknowledgment generation

Cost Comparison: Full EDI integration with SPS Commerce or TrueCommerce = $750-$2,000/month. PlainEDI unlimited + basic scripting = $99/month. Annual savings: $7,800-$22,800.

3PL Warehouse: Client Order Processing

Scenario: You're a 3PL fulfillment center. Your clients receive 850 POs from their retail partners but don't have EDI capability. You need to process these orders on their behalf.

Workflow:

  1. Client forwards 850 EDI file from their retailer to you via email
  2. Convert to CSV to quickly verify: items ordered, quantities, ship-to DC, delivery deadline
  3. Import CSV into your WMS (warehouse management system)
  4. Pick, pack, and ship order with correct retailer compliance labels
  5. Generate 856 ASN from your WMS and send to retailer on client's behalf

Value Add: Offer "EDI-lite" service to clients. They don't need full EDI setup, you handle conversion and compliance. Charge $50-100/month per client for this service.

Retailer-Specific EDI 850 Requirements

While all 850 POs follow the X12 standard, major retailers have unique requirements and critical fields you must track.

Walmart 850 POs

  • MABD Date (DTM*002): Must Arrive By Date - critically important. Missing MABD = 3% COGS penalty under OTIF program.
  • Department Number (REF*DP): Categorizes product type, required for routing and compliance.
  • DC Ship-To (N1*ST): Specific Walmart DC number and GLN code. Must match exactly on 856 ASN.
  • Vendor Number (REF*IA): Your assigned Walmart vendor ID - reference this on all documents.

Target 850 POs

  • TCIN (PO107): Target.com Item Number - unique product identifier, not UPC.
  • Perfect Order Program (May 2025): On-time, in-full delivery tracked per 850 PO. Penalties for variance.
  • Department/Class (REF*DP): Target's internal product categorization system.
  • PODS Reconciliation: Target's Purchase Order Data System - match 850 to 856 to 810.

Home Depot 850 POs

  • OTIF Requirement: 95% on-time, in-full delivery. Tracked via 850 PO vs 856 ASN vs receiving scan.
  • RDC vs Store Direct: 850 indicates Regional Distribution Center or direct-to-store shipment.
  • Appointment Required: Most DCs require scheduled delivery appointments - check DTM dates carefully.

Amazon Vendor Central 850s

  • ASIN (PO107): Amazon Standard Identification Number - primary product identifier.
  • 856 ASN Timing: Must send ASN within 4 hours of shipment creation or risk chargebacks.
  • Shortage Chargebacks: Amazon heavily penalizes short shipments. Ship exact PO quantity or communicate changes via 855.

EDI 850 vs 855 vs 856: Quick Reference Comparison

Understanding how purchase orders, acknowledgments, and ship notices work together in the retail EDI workflow.

TransactionWho SendsPurposeTimingKey Segments
850 Purchase Order
This page
Retailer → Supplier
Walmart, Target, Amazon, etc.
Place order for products: items, quantities, prices, delivery dates, ship-to locationFirst in workflow
Sent when retailer needs inventory
BEG, REF, DTM, N1, PO1, PID
855 PO Acknowledgment
View 855 page →
Supplier → Retailer
You send to confirm receipt
Acknowledge PO receipt: accept, reject, or propose changes to quantities/dates/pricesSecond - within 24hrs
After receiving 850 PO
BEG, ACK, DTM, N1
856 ASN (Ship Notice)
View 856 page →
Supplier → Retailer
You send before delivery
Notify retailer of shipment: what shipped, how much, which cartons, tracking numbers, SSCC labelsThird - before arrival
Before truck reaches DC
BSN, HL, PRF, MAN, TD5, LIN, SN1

Complete EDI Workflow Example:

  1. Day 1: Walmart sends you 850 PO for 100 units of Product A, delivery by Jan 25
  2. Day 1 (within 24hrs): You send Walmart 855 Acknowledgment confirming you accept the order
  3. Day 5: You ship the order. Before truck leaves, you send Walmart 856 ASN with carton SSCCs and tracking number
  4. Day 7: Truck arrives at Walmart DC. They scan SSCCs and match against your 856 ASN
  5. Day 8: You send Walmart 810 Invoice for payment
  6. Day 38: Walmart pays invoice (Net 30 terms)

Convert EDI 850 Purchase Orders by Retailer

Each retailer has unique requirements for 850 purchase orders. Select your retailer for specific compliance details and conversion examples.

Walmart EDI 850 to CSV

MABD dates, department numbers, DC routing, OTIF compliance

Target EDI 850 to CSV

TCIN product codes, Perfect Order Program, PODS reconciliation

Amazon EDI 850 to CSV

ASIN tracking, Vendor Central integration, shortage penalties

Home Depot EDI 850 to CSV

RDC vs store direct, appointment scheduling, 95% OTIF requirement

Lowe's EDI 850 to CSV

Distribution center requirements, vendor compliance programs

Costco EDI 850 to CSV

Direct import programs, depot delivery specifications

Best Buy EDI 850 to CSV

Electronics retail compliance, returns integration

AutoZone EDI 850 to CSV

Automotive parts compliance, store distribution requirements

Albertsons EDI 850 to CSV

Grocery distribution, perishable goods handling

Kroger EDI 850 to CSV

Supermarket distribution, vendor managed inventory

View All Retailer EDI Hubs →

Frequently Asked Questions

What is an EDI 850 Purchase Order?

The EDI 850 is a standardized electronic purchase order format used in B2B transactions. It contains all the information found in a traditional paper purchase order: items being ordered, quantities, prices, delivery dates, shipping addresses, and billing information. The 850 is part of the X12 EDI standard and is widely used by major retailers.

Which retailers send EDI 850 Purchase Orders?

All major retailers use EDI 850 for purchase orders, including Walmart, Target, Amazon, Home Depot, Lowe's, Costco, Best Buy, AutoZone, Albertsons, and Kroger. If you're a supplier to any large retailer, you'll likely receive 850 EDI files regularly.

How long does it take to convert an 850 EDI file to CSV?

PlainEDI converts EDI 850 files to CSV instantly - typically in under 30 seconds. Upload your file, preview the first 10 rows for free, then export the full CSV when ready. No software installation required.

What CSV columns are included in the 850 export?

Our 850 CSV export includes: PO Number, Order Date, Line Number, Item Number, Quantity Ordered, Unit of Measure, Unit Price, Product Description, Delivery Date, Ship-To Name, Ship-To Address, Bill-To Name, Department Number, and more. All standard 850 segments (BEG, REF, DTM, N1, PO1, PID) are parsed and included as columns.

Can I use the CSV in Excel or Google Sheets?

Yes! The CSV file can be opened directly in Microsoft Excel, Google Sheets, or any spreadsheet application. You can sort, filter, and analyze the data, create pivot tables, or import it into your ERP or inventory system.

Do you support large 850 files with many line items?

Yes, PlainEDI handles files up to 10MB, which can contain thousands of line items. Each line item becomes a separate row in the CSV output, making it easy to work with multi-line purchase orders.

Ready to Convert Your EDI 850 Files?

Try it free. Preview first 10 rows. Pay only when you export.

Upload 850 File Now

No signup required • Free preview • Instant conversion