Walmart Returns Metrics by Condition: Seller Action Guide

Walmart Marketplace now separates returns performance by item condition in its Seller performance reporting. The REPORT notification can distinguish NEW inventory, covering New and Collectibles, from RESOLD inventory, covering Pre-Owned and Restored items. That split gives sellers a faster way to decide where an investigation should begin. It does not diagnose the cause automatically, but it can help teams avoid a broad response when the signal is limited to one operating model. The practical goal is to connect each condition-group movement to item-level evidence, a targeted corrective action, and a later measurement period.

What Walmart changed in returns reporting

Walmart's official October 9, 2026 developer update says the Seller performance REPORT notification includes a Returns KPI grouped into:

For each applicable group, the report can include a returns score, trend, performance standard, risk level, duration, and a link to the relevant report. These fields tell a seller where performance may require attention; they do not identify the responsible product or root cause on their own.

Walmart's September 11 notice had initially described Returns-New and Returns-Resold as planned for October 19. The October 9 condition-specific update is the more current technical source. Sellers should validate the latest documentation and the output in their own account or integration.

Why the condition split changes seller diagnosis

A blended metric can conceal different patterns. Stable New-item performance can dilute a problem in Restored inventory, while a large Pre-Owned assortment can make a smaller New-item problem harder to see. The split helps a seller decide which process to inspect first.

Preserve a condition-level baseline before reacting. Record the report date, duration, score, trend, standard, risk level, and report link for each group. Add order volume, return counts, item mix, promotions, fulfillment changes, and catalog edits for the same period. Then open the linked report and connect the condition signal to affected products, return reasons, customer language, quality records, packaging, and fulfillment evidence.

Treat return reasons as clues. A "not as described" return may originate in condition disclosure, missing components, inaccurate content, or failed inspection. A damage return may come from product quality, packaging, handling, or delivery. The condition split narrows the search; it does not finish it.

Match corrective actions to the evidence

Apply the smallest change that addresses the supported cause. A catalog-wide rewrite will not solve a defective supplier lot, and stricter restoration testing will not fix shared compatibility language.

or integrations, archive the raw REPORT payload, preserve the retrieval timestamp and report link, and validate which condition groups are present. Do not convert a missing group to zero without checking catalog applicability, reporting coverage, and integration health. Use Walmart's live technical documentation as the schema authority.

Conclusion

Walmart's condition split makes returns performance more actionable by showing whether the signal sits in New and Collectibles, Pre-Owned and Restored, or both. Its value depends on disciplined follow-through: preserve a baseline, trace the movement to item-level evidence, apply a targeted correction, and measure the next comparable period. The report is a better starting point, not a substitute for diagnosis.