Walmart EDI, for a supplier who just got the letter
Walmart publishes a good deal about EDI, and withholds the part that costs the most. This page separates the two: what their own developer documentation says, what is only known through reporting, and which half applies to you. Everything from Walmart is linked so you can check it rather than take our word.
01The expensive part is the part they do not publish
Walmart's supplier penalty is On-Time In-Full, and it is measured per purchase-order line: a line is scored on whether the right quantity arrived and whether it arrived in the delivery window, and failing either marks that line non-compliant.
The figure usually quoted is 3% of the cost of goods on the failing line, against a compliance threshold in the high nineties. We could not find Walmart publishing that themselves on any public page. It is consistently reported (Supply Chain Dive and the Wall Street Journal among others), and the detail lives behind Retail Link, which only suppliers can open.
So treat it as reported rather than quoted, and get the number from your own supplier agreement before you plan around it. We would rather tell you we could not verify something than hand you a figure with a confident face on it.
What matters technically is where it is measured from, and that part is not in dispute: the ship notice. OTIF is a scorecard rather than an EDI requirement, but it is computed from what your 856 says and when it arrives, which makes a late or wrong ship notice a financial event rather than a technical one.
02Plain X12, which catches grocery suppliers out
If you are arriving from a grocer, the trap is immediate: Walmart uses the 850 and the 810, the general-purpose purchase order and invoice, even for food. There is no 875 or 880 here.
Those are not renamed versions of each other. A supplier set up for Kroger's grocery pair is set up for the wrong documents at Walmart, and the mistake runs in both directions when somebody adds the second retailer. The Kroger page covers that pairing if you are facing both.
Walmart's drop-ship documentation names the files it expects over SFTP, which is the clearest published statement of the set list: 855 acknowledgement, 856 ship notice, 846 inventory and 997 acknowledgement going to them; 850 purchase order, 860 purchase order change and 997 coming back.
The 855 is the one people miss. A supplier whose previous retailer only ever wanted an invoice has never had to acknowledge an order, and it is the commonest gap on a first Walmart setup.
Version is per document rather than per account (some sets are 004010 and some 005010), so “we are on 4010” is not an answer that covers everything. Invoicing arrangements differ between the drop-ship and warehouse programmes, so confirm how yours is billed rather than assuming the list above is complete for you.
03You can probably connect direct, and that is money
This is the part worth the page. Walmart's own documentation for drop-ship vendors describes three ways in, not one:
- Direct AS2 — Walmart maintains “a direct AS2 connection with the DSV”.
- Direct SFTP — likewise, “a direct SFTP connection with the DSV”.
- A value-added network — supported, and Walmart says it “does not govern or dictate the data flow between VAN and DSV”.
Set that against the other big name a supplier is likely to be facing. Kroger says of AS2 that they “do not have the capability” today, and name the networks as their preferred method. The two requirements point in opposite directions, and anybody quoting you one connection that covers both is quoting you something that cannot be true of both.
Why it shows up on your bill: a network charges for carrying your documents, either per thousand characters or a flat rate for each retailer you trade with. A direct connection does not. Where Walmart will take us directly, that line is not on your invoice at all, which is the cheap side of a story we usually have to tell the other way round.
One limit on all of the above: the pages documenting it are scoped to drop-ship vendors. The warehouse and import side is not published anywhere we can link to, and is widely reported to be AS2 through a mailbox arranged inside Retail Link. We have not verified that, so we are not going to assert it. Tell us which programme you are in and we will find out properly before anybody quotes you a connection.
04The labels, and the number that fails at the dock
Walmart wants GS1-128 carton labels carrying an SSCC-18, and the serial numbers on the cartons have to match what the ship notice said exactly.
A mismatch here is a deduction rather than a rejection, which is the worse of the two: nothing bounces, nothing errors, and the money comes off a remittance weeks later where it becomes somebody's job to work out why.
An SSCC is eighteen digits and the last one is a checksum of the other seventeen. Get it wrong and the label prints perfectly and fails at the receiving dock. We check it before the file leaves, and say what is wrong in English rather than as a code.
05What it costs here
$79 a month, or $69 for the first ten accounts, with documents not metered at all on the founding rate. Billing starts when your first production document arrives rather than when you sign up. A certification schedule is not something either of us controls, and charging you for the wait would be charging you for their queue.
Our fee does not move with your volume, and it stops climbing however many retailers you add. Where a retailer forces us through a network, that network's charge is variable and is billed on at cost as a separate line. For a direct Walmart connection there is no such line, which is the whole point of section 03.
The full pricing is published, including the parts that cost you more.
06What we have not done
We have no customers yet, so there are no testimonials and no Walmart supplier we can point you at. You would be taking a chance on something young. The honest mitigations: founding accounts cancel at any time with no notice, billing does not start until a real document moves, and your data exports whenever you want.
We have not run a Walmart connection end to end. We have read what they publish and built to it, which is a different thing from having survived a certification, and we are not going to blur them.
Our AS2 server is deployed and unproven. It is live and it answers, and it has never exchanged a message with a real retailer. If your programme turns out to require AS2, that is a thing to know about us before you commit rather than after.
Tell us your deadline before you commit to anything. If it is too close for a vendor with no Walmart certifications behind it, we will say so, and the comparison pages name who else to look at.
—Check we can read their file first
Before you give anybody an email address: take a file Walmart sent you and run it through the validator. It works in your browser and uploads nothing (the file never leaves your machine), and it will tell you what is in it and whether it parses.
Then tell us the retailer and the date on the letter. We would rather have the conversation than the form.
—Where these facts came from
- Connection types, quoted above: developer.walmart.com — EDI connection types
- The transaction sets and the file naming: developer.walmart.com — EDI interface
- Which supplier programmes those cover: developer.walmart.com — US supplier documentation
- The OTIF percentage is not from Walmart. It comes from trade reporting, and section 01 says so rather than dressing it up.
Read on 10 October 2026. Walmart can change any of this without telling us, and the documentation above is explicitly scoped to drop-ship vendors. Check it yourself, and check your own supplier agreement, before relying on a figure here.