Walmart Will Enforce Return Rates Per Item, Not Just Per Account, Starting January 2027

What happened: On November 6, 2026, Walmart published a release note on its Marketplace Learn portal announcing item-level Return Rate enforcement, effective January 2027. Until now, Walmart's Return Rate standard has looked at a seller's account as a whole. Starting in January, Walmart will also watch individual items: a single SKU with a high rate of seller-accountable returns can get a warning or be temporarily unpublished, even if the rest of the catalog is well within standard. Independent seller-performance coverage, including reporting from SellerEssentials, confirmed the change and flagged that Walmart has not yet published a numeric threshold for what counts as "high" at the item level.
What changes, and what does not
The account-level Return Rate standard that already governs Walmart Marketplace performance is not going away. What is new is a second, narrower layer sitting underneath it. A brand can keep a healthy account-wide return rate and still get an individual listing flagged, because Walmart's enforcement will look at return behavior SKU by SKU rather than only at the blended average across the whole catalog.
- Effective: January 2027, enforcement begins; the metric itself is retroactive to a rolling 60-day window.
- Unit of measure: individual item (SKU), not seller account.
- Trigger: seller-accountable returns on that specific item crossing an as-yet-undefined "high" rate.
- Consequence: warning or temporary unpublishing of the flagged item, separate from account-level standing.
Why this is harder than it sounds for multi-SKU brands
A seller with a dozen listings can eyeball which ones get returned often. A brand running a few hundred or a few thousand SKUs across Amazon and Walmart cannot do that by scrolling through the Returns page by hand, and Seller Center was not built to rank items by return risk or alert on a threshold that Walmart itself has declined to publish. That gap, pull return data per item across both marketplaces, score it against a rate the brand sets for itself until Walmart confirms its own number, and flag SKUs before they get unpublished, is a narrow, well-defined problem. It is exactly the kind of thing that is faster to ship as a focused internal tool than to wait on a platform dashboard that may never arrive in this shape. Brands with catalogs large enough to make a manual recheck impractical are usually better served by a software partner that can build that per-SKU monitoring layer quickly than by trying to bolt it onto a spreadsheet every week.
What to check this week
- Pull 60 days of return data per SKU for every active Walmart listing, not just the account-level summary Walmart shows by default.
- Rank items by return rate and look hardest at anything with low order volume, where a handful of returns can push the rate high fast.
- Cross-check against Amazon if the same product is listed on both marketplaces; a quality or sizing issue driving returns rarely respects the platform boundary.
- Set a recurring pull, not a one-time check. Walmart has not published its threshold, so the safest approach is to monitor the trend now and tighten the internal bar once the real number is confirmed.
None of this needs new tooling to start. A manual export this week tells a brand roughly how exposed it is. The build-vs-buy question only becomes real once the SKU count makes a weekly manual pull impractical to repeat through peak season and beyond.
Sources: Walmart Marketplace Learn release notes, SellerEssentials seller-performance coverage.


