MABD meaning, in the retail supply-chain sense
MABD stands for Must Arrive By Date: the date a purchase order has to be checked in at the retailer's distribution centre, not the date it ships. The MABD meaning that actually costs money is the second half of that sentence. A truck that leaves Fresno on time and reaches a Walmart DC in Bentonville two days after the date on the PO is late, regardless of how the ship date looked.
A second piece of the meaning gets missed just as often: early is also a miss. The date sits at the end of a window, and arriving before the window opens gets the load turned away or rescheduled at the DC's convenience, which frequently lands it outside the window on the other side.
This page is about the date. Which carrier hauls the load, how you book it, and how a retailer's collect programme routes freight are transport questions and are not covered here.
The window, and how it has tightened
Walmart sets the pattern most other large retailers copy, and its window has narrowed. Under the older must-arrive-by-date programme, suppliers had a four-day window for general merchandise and a three-day window for perishables. Under the on-time in-full rules in force since March 2024, that is two days for non-perishable goods and one day for perishables.
A one-day window is the part people underestimate. It means the delivery appointment, the DC's dock capacity and the carrier's transit variance all have to land on the same calendar day. There is no absorbing a four-hour delay.
What a missed MABD costs on the invoice
Missing the date is what triggers on-time-in-full exposure. Walmart set the threshold at 98% of orders arriving on time and in full, with a penalty of 3% of the cost of the goods, effective 15 September 2020. Other large retailers run the same shape of programme with different thresholds and different names.
The measurement itself, how OTIF is computed, where the over-shipment cap goes and why fill rate and OTIF disagree, is a separate subject with its own arithmetic. The supplier performance metrics walkthrough covers that; this page stops at the date.
The bigger half of the cost is not the fine
Here is a single missed date on one PO at a regional grocery banner, and the reason the fine is the part nobody should be optimising against.
| Line | Value |
|---|---|
| Cases on the PO | 1,200 |
| Delivered cost per case | $18.40 |
| PO value | $22,080 |
| OTIF penalty at 3% of cost of goods | $662.40 |
| Stores the PO was allocated to | 210 |
| Stores that went to zero scans | 63 |
| Average days at zero | 3.1 |
| Normal rate of sale, units/store/day | 9.4 |
| Units that never scanned | 1,836 |
| Shelf price per unit | $4.29 |
| Retail sales that never happened | $7,876.44 |
Run it: 1,200 x $18.40 = $22,080, and 3% of that is $662.40. On the shelf side, 63 stores x 3.1 days x 9.4 units = 1,836 units, and 1,836 x $4.29 = $7,876.44.
The fine is $662. The units that never scanned are worth $7,876 at retail, close to twelve times the penalty. Those retail dollars are the retailer's, and the supplier's share is the wholesale value of the same 1,836 units, but both sides lose on the same event and neither number appears on the deduction notice.
That asymmetry is why treating MABD as an accounts-payable problem is the wrong frame. The penalty is a rounding error against the demand the miss destroyed, and unlike the penalty, the lost demand does not show up in a report addressed to you.
Where a missed date shows up in the data
It shows up as a hole in the sales file, and it looks exactly like a demand collapse unless you know the delivery calendar.
Three signatures are worth learning:
- Zeros clustered by DC, not by geography. A demand shift moves gradually across a region. A late truck zeroes out precisely the stores one facility serves, and the store list is the giveaway.
- A clean edge on both sides. Real demand declines taper. A delivery miss produces a normal week, a flat zero, and a normal week, with a small spike when the shelf refills.
- The zero is longer than the delay. A two-day delivery slip commonly produces four or five days of zero scans, because the shelf was already thin before the truck was late and the backroom recovery is not instant. That is an on-shelf availability problem the moment the truck is late, and the days of supply at store level decides how bad it gets.
Where Scout fits
Scout reads the demand side of this. It ingests retailer POS and syndicated sell-through and flags the store-week zeros, so a missed MABD stops being an invisible line in a chargeback file and becomes a dated, store-level number you can put next to the penalty. What Scout is not: it is not a portal, an EDI gateway, a transportation management system or a supply-chain platform. It does not book freight, hold a routing guide, schedule a delivery appointment or transmit a purchase order. It tells you what the miss did to the shelf.
The short version
- MABD means Must Arrive By Date, the day a load has to be checked in at the retailer's DC. It is an arrival date, not a ship date, and arriving early is also a miss.
- Walmart's window is now one day for perishables and two for non-perishables, down from three and four under the older programme.
- Missing it triggers on-time-in-full exposure. Walmart's threshold is 98%, with a 3% penalty on the cost of the goods, in force since 15 September 2020.
- On the worked example, the fine was $662 and the units that never scanned were worth $7,876 at retail, roughly twelve times as much.
- In the sales file a miss reads as zeros clustered by DC with clean edges, lasting longer than the delay itself.
Sources: Mulder Brothers, "Walmart OTIF vs. MABD"; Blume Global, "Walmart Updates OTIF Requirements"; Zipline Logistics, "Walmart OTIF Requirements for Suppliers Increases to 98 Percent".