The deduction shows up on the invoice first. Somebody in finance flags it, somebody in supply chain gets the email, and the reverse engineering begins. Which POs? Which cases? Which DC? Was it the carrier, the case pack, or a truck that showed up a day early? The scorecard says what the score is. It doesn't say why.
For most Walmart supplier teams, that's where OTIF work actually lives. Not in the scorecard review itself, but in the hours spent afterward pulling shipment files, carrier reports, and PO detail into one spreadsheet just to explain a number that's already been billed.
By the time the explanation is finished, the same root cause has usually shipped a few more times.
By the time it posts, the miss behind it is weeks old and often still repeating.
The math is small per case and large per quarter
The mechanics are well documented across the supplier ecosystem. When cases miss Walmart's on-time or in-full expectations, the fine is 3% of the cost of goods on the non-compliant cases. Scoring happens at the case level, not the PO level, so a single shorted case on an otherwise clean order still counts. And since 2024, performance is evaluated monthly but fines are billed quarterly, which means the money lands in a lump, weeks after the shipments that caused it.
Three percent sounds manageable until it compounds. A miss that repeats on the same lane or the same item every week doesn't produce one fine. It produces a quarter's worth of them, all arriving at once, all pointing back to something that was visible in the shipment data the whole time. Early trucks count against you too, because DCs plan dock capacity tightly, so "we shipped it with time to spare" can be its own category of miss.
Why the root-cause work keeps losing to the calendar
The data for a real answer exists. It's just scattered. The OTIF scorecard sits in Retail Link. Shipment detail sits in transportation files. PO detail comes out of NOVA. Item and case-pack context lives in internal spreadsheets. To pattern failures by carrier, lane, DC, or item, an analyst has to pull all of it, fix the column names, align the date ranges, and join everything into one view.
That's the same cleanup grind as every other supplier report, with one difference: this one runs against a dispute clock. Chargebacks can be disputed through Retail Link within a set window, so the hours available go to the question that pays back this week. Is this fine disputable? The pattern question, the one that would prevent next quarter's fines, is the first thing cut when the window is closing.
So the cycle holds. Verify the fine, dispute what's disputable, move on. Next quarter, same email.
The patterns are usually boring, and that's good news
When supplier teams do get all the shipment data into one place, the root causes are rarely mysterious. It's the same lane missing its MABD by one day. The same DC where early arrivals keep getting flagged. One item whose case pack keeps generating shortages at pick. A routing step that slips every holiday week, on schedule, like it's part of the calendar.
Boring causes are fixable causes. You fix a lane once. You don't dispute twenty fines twice.
| Chasing one chargeback | Working the pattern | |
|---|---|---|
| Starting point | The deduction on the invoice | Every shipment, scored, in one view |
| Question asked | "Is this fine disputable?" | "What keeps causing misses?" |
| Outcome | Some money back, sometimes | Fewer misses next quarter |
What consolidated OTIF analysis looks like
None of this requires a data engineering project. The files already exist, because someone already downloads them to explain the last fine. The shift is in the sequence: upload the scorecard, shipment, and PO files you already pull, let the platform standardize and join them, and start from a consolidated view instead of building one.
From there, OTIF work changes shape. Failures group by root cause across all shipments instead of living inside individual POs. You can drill from the quarterly number down to the lane, DC, item, or week that's driving it, and track whether a fix actually moved the number in the months after. The dispute work doesn't go away, but it stops being the whole job.
A team that can see every miss in one place stops paying for the same root cause twice.
The fine is billed quarterly. The causes happen daily. Most of the frustration in OTIF work comes from those two timelines never meeting, and most of the opportunity comes from putting them on the same page.
FAQ
How much are Walmart OTIF fines?
3% of the cost of goods for cases that miss on-time or in-full expectations, measured at the case level. Performance is evaluated monthly and fines have been billed quarterly since 2024.
Where do suppliers see their OTIF performance?
In the OTIF scorecard in Retail Link. Explaining a score, though, usually means joining it with transportation files and PO detail from NOVA, which is where most of the manual work goes.
Can OTIF chargebacks be disputed?
Yes, through Retail Link within a set window. A successful dispute recovers that fine. It doesn't touch the root cause, which is why teams that only dispute tend to see the same fines return.
Stop paying for the same miss twice
If OTIF review on your team still means rebuilding a spreadsheet after the deduction posts, there's a simpler sequence. Upload the shipment and scorecard files you already have, see failures grouped by root cause, and walk into next quarter ahead of the fine instead of behind it.