Flat file EDI kept a small 3PL I work with alive for 8 months. But let me back up — because in e-commerce, the worst moment isn't a bad review. It's a big client asking "does your warehouse support EDI?" — and you going completely blank while the deal walks out the door.
Last year, a home goods brand came to me — tens of thousands of orders a year, wanting to run through a small 3PL I work with. Everything was going great until their buyer casually asked: "does your warehouse support EDI?" My brain just went "bzzzt" — EDI what now? Is that edible?
Turns out that one question nearly killed the deal. So this one's for every small warehouse and small 3PL owner who felt exactly as clueless as I did: how to hold the line with flat files when a client demands EDI — and when you absolutely must upgrade.
Plain English First: What Even Is EDI
EDI (Electronic Data Interchange) is, stripped of jargon, "machines exchanging secret handshakes."
Emailing spreadsheets is human-to-human — someone on the other end still has to key it in by hand. EDI is system-to-system: your WMS generates a standardized message, the client's system receives it, parses it, and books it in. No humans in the middle.
The "handshake" follows international standards — ANSI X12 is the one you'll meet in North America. A few message codes you'll run into sooner or later, worth memorizing:
- 850: purchase order (client orders from you)
- 856: ship notice / ASN (you tell the client "it shipped, here's the tracking number")
- 810: invoice
- 940: warehouse shipping order (3PL world: the client tells you to ship)
- 945: warehouse shipping advice (3PL world: you confirm "shipped")
When a big client says "we need EDI," nine times out of ten they really only need two or three of these — usually 856 plus 810, or 940 plus 945. Ask exactly which ones before discussing how to implement anything. Don't buy the full buffet when you only need two dishes.
The Flat File Workaround: CSV Plus SFTP, the Scrappy Way
Full EDI means going through an EDI provider (SPS Commerce, TrueCommerce, that crowd). Implementation is measured in months, and pricing is whatever their website says this quarter — check their official site for current rates. For a small warehouse, that's too expensive and too slow. The deal won't wait.
So here's the scrappy route we took — the "flat file":
- Every afternoon at a fixed time, the WMS exports a CSV: order number, tracking number, SKU, quantity, ship date. One row per order.
- Reorder the columns and fix the date format to match the client's Excel mapping sheet.
- Push the file on a schedule via SFTP to the client's server.
- Their IT guy wrote a small script that parses it into their system automatically.
Total cost: zero. The WMS already exports, SFTP tools are free, and the client wrote their own script. We ran on this for 8 months while volume grew from two or three hundred orders a day to seven or eight hundred. Not a single hiccup.
This trick works — I tested it myself. But fair warning up front: it's a band-aid, not a cure.
Show Me the Numbers: Flat File vs True EDI vs API
| Flat file (CSV + SFTP) | True EDI (via provider / VAN) | API integration | |
|---|---|---|---|
| Upfront cost | Basically zero | Implementation + mapping fees (check provider's official pricing) | Developer time |
| Time to launch | Days | Weeks to months | Depends on the dev queue |
| Who notices errors | Whoever does manual reconciliation | 997 acknowledgment confirms automatically | Real-time response codes |
| Fits what volume | A few hundred orders/day | 1,000+/day, multiple clients | When you have a tech team |
| Client acceptance | Depends on the client | Industry passport | More and more clients accept it |
See the trade-off? Flat file wins on speed and cost. It loses on "nobody tells you when it's broken" and "the client might not accept it."
Where It Blew Up on Me: The Date Format Incident
Let me tell you about the time it burned us, because this is flat file's biggest weak spot.
Our WMS pushed an upgrade that silently changed the CSV date format from YYYY-MM-DD to MM/DD/YYYY. We didn't notice; the file went out as usual. The client's system treated every date as invalid — the entire batch of 856 ship notices got rejected. Their receiving appointments are auto-scheduled off the 856s, so the whole appointment board collapsed and trucks started stacking up at their gate. Their ops director called and let us have it.
True EDI has something called the 997 — a functional acknowledgment. Did they get your message? Was the format valid? The system confirms automatically. Flat file has none of that. When it's wrong, it's just wrong, nobody tells you, and by the time you find out the client is already yelling.
After that we added a low-tech fix: every day after the push, manually spot-check 5 orders against the client's system. Primitive, but it works. At low volume, human eyes are the best 997 you can get.
Three Signals It's Time to Upgrade Your Small Warehouse EDI
How long can flat file hold? Watch for these three signals — if any one shows up, stop white-knuckling it:
Signal one: volume outgrows human oversight. Two or three hundred orders a day, spot-checks are fine. A thousand a day with human eyeballs on reconciliation — it's a matter of time before something breaks.
Signal two: the client starts asking for acknowledgments and real-time data. 997 confirmations, daily 947 inventory syncs, real-time 214 shipment status — flat file can't play there. That's true EDI's home turf.
Signal three: do the math. Grab a calculator: weekly hours spent on "exporting, reconciling, re-sending, arguing with the client," times the hourly wage, times 4 for the month. If that number beats the EDI provider's monthly fee (check their official site), upgrading literally makes you money. When I ran our numbers, the hours we were burning every week had passed the monthly fee long ago — nobody had just bothered to add it up.
And here's the counterintuitive one for small warehouse owners: going true EDI first isn't always progress. If your WMS inventory is a mess — book vs. physical never matching — then EDI just automates and accelerates your errors straight to the client. Wrong, faster, and neater. Get your inventory accuracy to a level you'd stake your reputation on first, then talk EDI. Reverse the order and you're burning money.
Don't-Get-Burned Checklist: Before You Sign Anything
- Ask the client exactly which transactions they need. 850, 856, 810 is the most common combo — don't pay for messages you'll never use.
- VANs (value-added networks) bill by volume. Small volume, don't sweat it. Big volume, negotiate — and check the provider's official site for current rates.
- Don't just test the sunny-day path. Returns, split shipments, short picks, bad addresses — run every exception message through. Nine times out of ten, production failures come from exception flows nobody tested.
- Pick a provider with 3PL industry templates. A generic EDI provider might map 940/945 from scratch; one with industry templates can have you running in days.
The flat file trick works — I tested it myself, and at low volume it's magic. But it's a band-aid. Keep white-knuckling it as volume grows and one blowup costs more than the upgrade ever would. When it's time, spend the money — spend it where it counts.
By Ah K, E-commerce Seller (5 yrs)
