How to Open Walmart EDI Files Without Special Software
Step-by-step guide to opening and reading Walmart EDI files using free text editors on Windows, Mac, or converting to CSV instantly.
Quick Answer
Walmart EDI files are plain text files that can be opened with any text editor (Notepad on Windows, TextEdit on Mac). However, they're difficult to read due to X12 formatting with special delimiter characters like * (element separator) and ~ (segment terminator). For easier viewing, convert to CSV using PlainEDI's free converter in 30 seconds.
In This Guide:
Why Walmart EDI Files Are Hard to Open
If Walmart sent you an EDI file (typically with extensions like .edi, .x12, .txt, or .dat), you might have tried double-clicking it and encountered a confusing error or a wall of unreadable text. This is normal.
Walmart EDI files use the ANSI X12 standard — a structured text format designed for computer-to-computer communication, not human reading. The files contain purchase orders (850), advance ship notices (856), invoices (810), and other transaction types formatted with special delimiter characters instead of the rows and columns you'd see in Excel.
⚠️ Important Context
While you can open Walmart EDI files with a text editor, reading them is extremely difficult due to the X12 format structure. Most vendors immediately convert EDI to CSV or Excel for practical use. This guide shows you both approaches: viewing the raw file AND converting it to a readable format.
Method 1: Open with Text Editor (Free, But Hard to Read)
On Windows (Using Notepad)
- Right-click the EDI file (e.g.,
walmart_850_PO.edi) - Select "Open with" → "Notepad" or "Notepad++" (if installed)
- The file will open showing text like:
ISA*00* *00* *ZZ*WALMART *ZZ*YOURCOMPANY *250120*1034*U*00401*000123456*0*P*~GS*PO*WALMART*YOURCOMPANY*20250120*1034*1*X*004010~ST*850*0001~BEG*00*SA*1234567890**20250120~... - Problem: The entire file appears as one continuous line because X12 files don't include line breaks after each segment.
💡 Pro Tip: Make It Readable in Notepad++
If you have Notepad++ (free download from notepad-plus-plus.org):
- Open the EDI file in Notepad++
- Press Ctrl + H to open Find & Replace
- In "Find what" box, type:
~(the segment terminator) - In "Replace with" box, type:
~\n(adds a line break) - Check "Extended search mode" at the bottom
- Click "Replace All"
Now each segment appears on its own line, making it much easier to identify segments like BEG (purchase order start), N1 (name/address), IT1 (line items), etc.
On Mac (Using TextEdit)
- Right-click the EDI file
- Select "Open With" → "TextEdit" (built into macOS)
- If TextEdit shows formatted text, go to TextEdit → Preferences → "Plain text" under "Format"
- Reopen the file to see the raw X12 content
Limitations of this method:
- You see delimiter characters (* and ~) everywhere, making data hard to extract
- No automatic parsing of dates (20250120 = January 20, 2025)
- Line items buried in IT1 segments mixed with addresses (N1), dates (DTM), and metadata
- Cannot easily copy purchase order details into your system without manual reformatting
- Risk of missing critical data like MABD dates, department numbers, or ship-to GLN codes
What You'll See in Raw X12:
ISA*00* *00* *ZZ*WALMART *ZZ*YOURCOMPANY *250120*1034*U*00401*000123456*0*P*~ GS*PO*WALMART*YOURCOMPANY*20250120*1034*1*X*004010~ ST*850*0001~ BEG*00*SA*PO1234567890**20250120~ DTM*002*20250125~ N1*ST*WALMART DC 6022*92*0078742001696~ N1*BY*WALMART*92*0078742000005~ IT1*1*100*CA*12.99*UD*UP*012345678901*VN*YOUR-SKU-123~ PID*F****48 Pack AAA Batteries~ CTT*1~ SE*10*0001~ GE*1*1~ IEA*1*000123456*~
Translation needed: This 850 Purchase Order requests 100 cases of item 012345678901 (UPC) at $12.99 per case, ship to Walmart DC 6022, must arrive by January 25, 2025 (DTM*002).
Method 2: Copy to Excel for Semi-Structured Viewing
Microsoft Excel can parse the delimiters to create columns, making it slightly easier to review than plain text.
Steps:
- Open the EDI file in Notepad (Windows) or TextEdit (Mac)
- Press Ctrl + A (Windows) or Cmd + A (Mac) to select all text
- Press Ctrl + C (Windows) or Cmd + C (Mac) to copy
- Open Microsoft Excel or Google Sheets
- Paste the content into cell A1
- In Excel: Select the column → Go to Data tab → "Text to Columns"
- Choose "Delimited" → Click Next
- Uncheck all preset delimiters, then check "Other" and type:
*(asterisk) - Click Finish
✅ Result
Each element now appears in its own column. For example, an IT1 segment splits into: IT1 | 1 | 100 | CA | 12.99 | UD | UP | 012345678901 | VN | YOUR-SKU-123
However: You still need to know X12 segment definitions to understand what IT1*1*100*CA means (Line #1, Quantity 100, Unit CA=Case). This is better than raw text but still requires manual interpretation.
Limitations:
- Segments like ISA, GS, ST, N1, IT1 mixed together — hard to separate purchase order data from metadata
- No automatic labeling (you don't know column D is "Unit Price" unless you reference X12 documentation)
- Multiple IT1 segments (line items) require manual consolidation
- Dates still in CCYYMMDD format (20250125 instead of "January 25, 2025")
- Cannot filter or sort by retailer-specific fields like Walmart's department number or MABD date
Method 3: Convert to CSV (Recommended — Easiest & Fastest)
Instead of manually parsing X12 delimiters and looking up segment codes, use PlainEDI to automatically convert Walmart EDI files to clean CSV with human-readable column headers.
How It Works:
- Go to PlainEDI Free Converter
- Upload your Walmart EDI file (850, 856, 810, 820, 846, 997)
- Preview instantly — see parsed data in 5 seconds (no account needed)
- Download CSV with labeled columns like:
PO Number,PO Date,Ship By DateItem UPC,Quantity,Unit Price,DescriptionShip To Name,Ship To GLN,Ship To AddressDepartment Number,Vendor Item Number
- Import CSV into Excel, Google Sheets, QuickBooks, or your inventory system
🎯 Example Transformation
Raw X12:IT1*1*100*CA*12.99*UD*UP*012345678901*VN*YOUR-SKU-123~PID*F****48 Pack AAA Batteries~
PlainEDI CSV Output:
| Line # | Quantity | Unit | Unit Price | UPC | Vendor SKU | Description |
|---|---|---|---|---|---|---|
| 1 | 100 | Case | $12.99 | 012345678901 | YOUR-SKU-123 | 48 Pack AAA Batteries |
Why This Is Better:
- No X12 knowledge required — columns are pre-labeled with plain English headers
- Dates automatically formatted — DTM*002*20250125 becomes "January 25, 2025"
- Walmart-specific parsing — extracts MABD dates, department numbers, GLN codes automatically
- Handles all transaction types — 850 POs, 856 ASNs, 810 Invoices, 820 Payments, 846 Inventory, 997 Acknowledgments
- Works with 10+ retailers — not just Walmart (Target, Amazon, Home Depot, Lowe's, Costco, Best Buy, AutoZone, Albertsons, Kroger)
- Takes 30 seconds — vs 2-4 hours of manual data entry (according to Aberdeen Group study)
Pricing (No Subscription Required)
Preview any file free before purchasing export
💰 Cost Comparison
Manual Processing: 2-4 hours per file × $18.75/hour (entry-level admin wage) = $37.45 per file (Aberdeen Group study)
PlainEDI 10-Pack: $3.90 per file (90% savings)
If you process 50 Walmart POs per month: Save $1,677.50/month = $20,130 annually
Understanding X12 Format & Delimiters
If you need to read raw EDI files regularly, understanding the X12 structure helps you identify key data even without converting.
X12 Delimiters (The Special Characters)
| Delimiter | Character | Purpose | Example |
|---|---|---|---|
| Element Separator | * | Separates data fields within a segment | BEG*00*SA*PO123 |
| Segment Terminator | ~ | Marks the end of a segment | BEG*00*SA*PO123~ |
| Subelement Separator | : | Separates composite elements (rare) | REF*DP*001:002 |
🔍 How to Find Delimiters in Any EDI File:
The ISA segment (first 106 characters) defines the delimiters:
- Character 4: Element separator (usually
*) - Character 105: Subelement separator (usually
:) - Character 106: Segment terminator (usually
~)
Example ISA: ISA*00* *00*... — the 4th character is *, so that's your element separator.
Common X12 Segments in Walmart Files
| Segment | Name | Purpose | Example |
|---|---|---|---|
ISA | Interchange Header | File metadata (sender/receiver IDs) | ISA*00* *00* *ZZ*WALMART... |
GS | Functional Group Header | Transaction set type (PO, Invoice, etc.) | GS*PO*WALMART*VENDOR... |
ST | Transaction Set Header | Starts a new transaction (850, 856, etc.) | ST*850*0001 (850 PO) |
BEG | Beginning Segment | PO number and date in 850 files | BEG*00*SA*PO1234567890**20250120 |
DTM | Date/Time Reference | Ship by date, delivery date (MABD) | DTM*002*20250125 (deliver by Jan 25) |
N1 | Name/Address | Ship-to location, buyer info | N1*ST*WALMART DC 6022*92*0078742001696 |
IT1 | Baseline Item Data | Line items: UPC, quantity, price | IT1*1*100*CA*12.99*UD*UP*012345678901 |
PID | Product Description | Human-readable item name | PID*F****48 Pack AAA Batteries |
SE | Transaction Set Trailer | Ends transaction (segment count) | SE*10*0001 |
⚠️ Walmart Date Format: CCYYMMDD
Walmart uses 8-digit dates in X12 files: 20250120 = January 20, 2025. The DTM*002 segment shows the MABD (Must Arrive By Date) — critical for Walmart's 90% OTIF requirement. Missing this date can result in a 3% COGS penalty.
Walmart-Specific EDI Requirements
When opening Walmart EDI files, pay special attention to these retailer-specific requirements that affect compliance:
Critical Fields in Walmart 850 Purchase Orders
| Field | Location | Why It Matters |
|---|---|---|
| MABD Date | DTM*002*CCYYMMDD | Must Arrive By Date — late delivery = 3% COGS penalty if OTIF falls below 90% |
| Department # | REF*DP*[number] | Required on ASN and invoice for proper routing |
| Ship-to GLN | N1*ST*[name]*92*[GLN] | 13-digit Global Location Number — identifies exact DC, must match on ASN/invoice |
| PO Number | BEG*00*SA*[PO#] | 10-digit number — reference on all documents (855, 856, 810) |
| Item UPC | IT1*...*UP*[UPC] | 12-digit GTIN-12 — must match case/each level correctly |
Walmart OTIF (On-Time In-Full) Requirements
Walmart enforces strict delivery performance metrics that affect your ability to stay compliant:
- 90% On-Time (Prepaid Freight): Deliver within MABD-3 to MABD window (can arrive up to 3 days early, not late)
- 98% On-Time (Collect Freight): Must be ready for carrier pickup on scheduled date
- 95% In-Full: Ship 95%+ of ordered quantity (each line item counted separately)
- 3% COGS Penalty: If OTIF drops below 90%, Walmart deducts 3% of cost of goods sold from your invoices
🚨 Common Compliance Failure
Scenario: You open the Walmart 850 PO in Notepad, manually copy the quantity (100 cases), but miss the DTM*002 segment showing MABD date of January 25. You ship on January 26 (one day late).
Result: Walmart logs a late delivery. If your OTIF score drops below 90%, you face a 3% COGS penalty on all future invoices until you recover above 90% for 4 consecutive weeks.
Prevention: Use PlainEDI to automatically extract MABD dates into a labeled CSV column, reducing risk of manual error.
Required Responses to Walmart 850 POs
After opening and processing a Walmart 850 PO, you must send these responses:
- 855 PO Acknowledgment (within 24 hours):
- Confirm you can fulfill the order (code: AC = Accepted)
- Or reject/partially accept with reason codes
- Must match PO number from BEG segment
- 856 Advance Ship Notice (before shipment arrives):
- Required for all Walmart shipments
- Missing ASN = $200-$500 chargeback (Code 21)
- Late ASN (arrives after shipment) = Code 22 chargeback
- Must include SSCC-18 barcode (MAN*GM segment) for each pallet/carton
- 810 Invoice (after delivery):
- Must match PO quantity and price exactly
- Price mismatch = Code 11 deduction (Walmart pays the lower of PO price vs invoice price)
- Quantity shortage = Code 64/65 chargeback (unit cost + handling fee)
💡 Tip: If you're not set up to send EDI responses (855, 856, 810) electronically, many vendors use Walmart's Retail Link web portal to manually submit ASNs and invoices. However, you still need to read the incoming 850 PO to know what to submit — which is why converting to CSV makes the process manageable without full EDI software.
Common Problems & Solutions
Problem: "Windows can't open this file"
Cause: The file extension (.edi, .x12, .dat) isn't associated with any default program in Windows.
Solution: Right-click → "Open with" → "Notepad" or "Choose another app" → Select Notepad and check "Always use this app to open .edi files"
Problem: File appears as one continuous line
Cause: X12 files don't include line breaks (carriage returns) after segment terminators by default.
Solution: Use Notepad++ Find & Replace to replace ~ with ~\n (adds line break), or use PlainEDI to convert to CSV which automatically separates segments into rows.
Problem: Can't find the MABD date in raw EDI file
Cause: MABD date is buried in a DTM segment, often mixed with other dates (PO date, requested ship date, etc.)
Solution: Search for DTM*002 (002 = delivery requested date qualifier). The date follows in CCYYMMDD format. Example: DTM*002*20250125 = Must Arrive By January 25, 2025. Alternatively, use PlainEDI which extracts this automatically into a "Ship By Date" or "MABD" column.
Problem: Department number missing or incorrect on ASN/invoice
Cause: Failed to extract department number from REF*DP segment in 850 PO when manually transcribing data.
Solution: Search for REF*DP* in the EDI file — the department number follows (e.g., REF*DP*123). Must include this on your 856 ASN and 810 invoice or risk routing errors and chargebacks. PlainEDI automatically extracts this into a "Department Number" column.
Problem: Excel Text-to-Columns creates 100+ columns
Cause: X12 files have varying numbers of elements per segment, and all segments are pasted into Excel at once.
Solution: Instead of converting the entire file, copy only the segments you need (e.g., all IT1 line item segments) into Excel. Or skip manual Excel parsing and use PlainEDI, which intelligently organizes data into the correct CSV structure (one row per line item with all relevant fields).
Problem: File contains multiple purchase orders (batch file)
Cause: Walmart sometimes sends multiple 850 POs in a single EDI file (multiple ST/SE transaction sets within one ISA/IEA envelope).
Solution: Look for multiple ST*850 segments — each starts a new PO. Count the number of ST*850 occurrences to know how many POs you received. PlainEDI handles batch files automatically, parsing each transaction separately and including a "Transaction Number" column to distinguish them.
Related Guides
How to Read a Walmart EDI 850 File
Detailed breakdown of every segment in Walmart purchase orders including MABD dates and department numbers.
How Walmart Suppliers Use EDI to CSV Conversion
Complete Walmart supplier workflow: convert EDI, meet 90% OTIF, avoid 3% COGS penalty.
Understanding EDI X12 Delimiters & File Structure
Master the fundamentals: segment terminators, element separators, ISA/GS/ST envelope hierarchy.
EDI to CSV vs Manual Processing: Cost Comparison
Real ROI calculations: 30 seconds vs 2-4 hours per file, $3.90 vs $37.45 per order.
Ready to Stop Wrestling with Raw EDI Files?
Convert any Walmart EDI file to clean CSV in 30 seconds. No X12 knowledge required. Preview free before you buy.
Try Free Walmart EDI Converter →Works with all Walmart transaction types: 850 PO, 856 ASN, 810 Invoice, 820 Payment, 846 Inventory, 997 FA