DIRECT ANSWER
Diagnose a stopped Walmart order in three steps: confirm the item’s Supply Item Status Code, confirm it is still listed rather than NIL, then compare valid stores with traited stores. Each branch points to a different cause and owner; demand forecasting comes later.
Walmart stopped ordering your item for one of a short list of structural reasons, and the demand forecast is usually the last of them. The triage runs in a fixed order. First: can the item be ordered at all? That is the Supply Item Status Code, a three-value lifecycle on the item file. Second: is the item still in the listing at all? That is NIL, a listing status that sits on a separate axis from supply status. Third: where is replenishment actually happening? That is the item’s valid stores, which are not the same set as its traited stores. The most confusing version of “Walmart stopped ordering” is the third one: the modular looks intact, the status reads Active, and stores have quietly stopped replenishing the item one by one. Each branch of this tree has a different owner at Walmart, so the diagnosis also tells you whose desk the fix belongs on.
Is the item still orderable at all?
The item file carries a Supply Item Status Code with three values: Active (A), Inactive (I), and Delete (D). Replenishment for an Owned or DSD item runs off this code, so an item that is not Active cannot order, whatever the forecast says. Two of its behaviors move the code without any action on your side.
The first is date-driven auto-reversion. Activating an item requires that its Item Effective Date not sit in the future and its Supply Item Expire Date not sit in the past; when the dates conflict, the system reverts the item to Inactive on its own. That means a status you set can un-set itself: your records show you activated the item, and the item file shows Inactive, because a stale expire date or a forward-dated effective date pulled it back.
The second is the inactivity clock. Inactive does not mean off. An Inactive item keeps selling in stores and online until it goes thirteen continuous months without a sale, and any sale restarts that clock. Only after a true thirteen months of silence does the system move the code to D on its own. D begins a purge that can take up to ninety days, and a Walmart associate must approve the deletion. So an item can drift from “we stopped pushing it” to “it deleted itself” on a timeline no one at your company chose, with a single clearance sale resetting the countdown along the way.
The code is maintained in Supplier One: Items and Inventory, then Maintenance Hub, then Item Configuration & Supply Chain, then Update item configuration; you export the attribute, edit it, and upload. The change lands as a submission, not an instant edit, and a deletion always needs a Walmart associate’s approval, so the day you submit and the day the change lands can be two different days; the Submissions Manager is where you track a submission across that gap. Two structural notes: DSV items do not carry an editable Supply Item Status Code, and the change is built for a drained item, because flipping the code while the item still has on-hands or on-orders causes receiving issues. These mechanics are current as of July 2026; if what you see inside the portal differs, trust the portal.
Is the item delisted rather than deactivated?
NIL, “Not In Listing,” is a listing status, not a supply status. It answers “is this item in the listing,” while the Supply Item Status Code answers “can this item replenish,” and the two are recorded separately, so checking one does not answer the other. From the outside, an ordering stop reads the same either way, which is exactly why the two get conflated.
An item-file audit counts items by status, and NIL shows up in that count as its own state. When ordering stops, the two axes answer different questions: a clean supply status does not settle the listing question, and a clean listing does not settle the supply question. In Supplier One’s catalog, the WIN-keyed view (Item configurations and hierarchies) is where supply item status and replenishability live, while the Products view carries the site-side publish status (an unpublished listing is a different diagnosis again); the same item answers differently depending on which axis you ask. How an item came to sit NIL is a listing and assortment question, and assortment sits in the buyer’s territory below. Where the tooling itself is the confusion, the Supplier One versus Retail Link split is its own subject.
What is the difference between traited and valid stores?
Traited means the buyer put the item on the modular for that store: the item should be there. Valid means the store is actively replenishing the item: the item is ordering. Store-level replenishment only happens where the item is valid, so an item can hold every modular slot it ever had and still stop ordering.
The two flags make four states, and each state is a different read:
- Traited and valid. On the modular and replenishing. Healthy.
- Traited, not valid. On the modular but not replenishing. This is a store-side outcome (low sales, high returns, excess inventory at that store) or a validity break. These are your “stopped ordering” stores.
- Valid, not traited. No modular home, but the store orders anyway on local demand. Upside, and fragile: distribution with no modular home to defend it can vanish.
- Neither. No modular, no replenishment. Not distribution.
The state that generates the phone call is the second one, at scale: the traited count holds, so every modular report and every walk of a store shows the item where it belongs, while the valid count falls underneath it. The item is not being discontinued; it is being dropped, one store at a time, and the mechanism is silent.
What does the weekly valid-store count reveal?
The valid count is the series that separates a modular decision from store-by-store erosion. A step change in the traited count is a modular decision: someone chose to add or remove the item from planograms, and the buyer’s chair owns that story. A falling valid count under a flat traited count is stores dropping the item one at a time, and no single week of it looks like news.
The reason the weekly read matters is arithmetic, not vigilance: the per-store metrics that matter here are computed against the valid base. In-stock percentage is measured across valid stores, and dollars per store per week is published in more than one denominator variant, with the valid-count read the meaningful one for velocity. A per-store number computed on the valid base can hold steady while total volume slides, because the denominator is shrinking with the numerator.
Here is one read, hypothetical but concrete. An item is traited in 3,400 stores, and that number has not moved in a quarter. Eight weeks ago the valid count was 3,380; this week it is 3,120. Total POS dollars are down about eight percent over the same stretch; divide them by the valid count and dollars per store per week are flat, and in-stock percentage is flat. Nothing in the per-store numbers flags a problem, because both sit on the shrinking valid base. The traited count rules out a modular decision. What the series shows is 260 stores exiting one by one: store-side outcomes or validity breaks, not a forecast miss and not a modular cut. The evidence to carry into the conversation is the store list and the two counts, week over week on Walmart’s own calendar (the week converter maps those weeks to dates), and the conversation belongs to the replenishment manager, because the modular never moved.
One caution across everything in this section: the ordering engine underneath these counts is Walmart’s Global Replenishment System, and its math is Walmart’s own and unpublished. Any formula a supplier reconstructs is a guess wearing a lab coat. What you can actually hold is the evidence the system leaves: issued POs (the only firm orders), the order forecast (a planning tool, not a promise to buy), and the traited and valid counts. Those counts come out of Retail Link and Scintilla reporting; which Scintilla tier you sit on decides how much of that reporting you have.
Who at Walmart owns which fix?
Walmart splits ordering across chairs, and the split, not your org chart, decides where each fix goes. The buyer owns assortment, cost, modulars, line reviews, and promotions. The replenishment manager owns PO generation, in-stock management, and the supply-chain configuration behind ordering: forecast base and trend, safety stock, lead time, order rules, supplemental orders, DC flow. Larger suppliers may also have an inventory manager sitting between the two. And the Supply Item Status Code is the lever that sits on your side of the table: a supplier-submitted item-file change that lands on Walmart’s timetable, not yours.
Mapped to the tree above: a status problem or a date conflict is an item-file fix, submitted through the Maintenance Hub and tracked to completion on Walmart’s side. Modular, traiting, and assortment questions belong to the buyer, and a NIL question starts in the same chair, because the listing is an assortment matter. Valid-store erosion, a forecast that lags reality, an order gap, or anything about how much and when the system orders belongs to the replenishment manager. The split has a practical consequence: a quantity ask sitting on the buyer’s desk stalls, and an assortment ask sitting on the replen’s desk dies. Neither person is failing you; each is answering the mail that belongs to their chair, and Walmart drew the chairs.
What about the next item that stops ordering?
The tree branches differently every time: this item flipped Inactive on a date conflict, the next one is NIL with a clean supply status, the one after that is bleeding valid stores under an intact modular, and each branch changes whose desk the fix belongs on. Retail Reason exists for exactly that moment: ask the question the way you would say it out loud (“this item is Active and traited in three thousand stores; what would make it stop ordering?”) and get back the branch, the evidence to pull, and the chair that owns it. Every answer carries the date it was last verified and a confidence class, so you know which facts are firm and which to re-check in the portal. It answers questions and checks plans; it does not file disputes or touch your account, and no person sits between your question and the answer. See pricing, or contact Matt.