twimco.Let’s talk ↗︎
Menu
Field notes / Operations

Walmart folded the WFS Returned to Seller report into Customer Returns. Walk your returns routine through the change

One Walmart Fulfillment Services report went away on October 29. If a person or a script downloaded it every week to check in returned stock, that routine is now reading nothing. Here's how to walk it, step by step, onto the report that replaced it.

Editorial engraving of a sunny garage receiving bay where a lead holds up a returned carton beside the list on his tablet while a bookkeeper checks the same shipments on her laptop.

On October 29, 2026, Walmart retired the WFS Returned to Seller report. Inventory sent back to you is now tracked in the Customer Returns report, which Walmart says includes the same data, including ship dates, quantities and tracking numbers. Find every routine that used the old report, compare a week of the new one against your last old download, and update the receiving and reconciliation steps before returns pile up after the holidays.

What changed, in one paragraph

On October 29, Walmart posted a short release note: the Walmart Fulfillment Services Returned to Seller report is retired. Instead of two separate reports, you track all inventory sent back to you from the Customer Returns report. Walmart says that report includes the same data the old one had, including ship dates, quantities and tracking numbers.

That's a sensible tidy-up. One report is easier than two. But a lot of sellers don't open reports by hand. Someone downloads a file on Monday and pastes it into a sheet, or a scheduled job pulls it into an inventory system, or a virtual assistant follows a checklist written two years ago. A retired report doesn't fail loudly. It fails as a quiet Monday when nothing seems to have come back.

And the timing matters. Returns climb after the holidays, which is exactly when you want this working.

Step 1: find everyone who used the old report

Start with people, then tools. Ask three questions in your team chat, or of yourself if it's just you.

Who downloaded it? The person who receives returned stock, the bookkeeper who reconciles WFS inventory, the person who files claims for lost or damaged units.

What did they do with it? Checked in boxes at the dock, adjusted stock in a spreadsheet or inventory system, matched it against fees, or chased missing shipments.

Did anything fetch it automatically? A scheduled download, an import in your inventory or accounting software, an automation tool, a script someone wrote. If you use a third-party integration for Walmart, ask the vendor directly whether they used this report and what they're switching to.

Write each answer as one line: who or what, how often, and what happens next with the data. That list is the routine you're about to walk through the change.

Decision guide

Old routine, new routine

ConsiderationBefore Oct 29From Oct 29
SourceReturned to Seller report.Customer Returns report.
What's in itInventory sent back to you.Customer returns and inventory sent back.
First stepDownload and use.Download, then filter to returns sent to you.
Duplicate riskLow, one kind of row.Check by tracking number and quantity.
Illustrative decision framework; Walmart's Oct 29, 2026 note doesn't list column names.
A retired report doesn't fail loudly. It fails as a quiet Monday when nothing seems to have come back.

Step 2: put a new download next to an old one

Download the Customer Returns report for a recent stretch, say the last four weeks. Then find the last Returned to Seller file anyone saved, and compare the two for an overlapping period.

You're checking three things.

Are the shipments there? Pick five shipments of inventory that WFS sent back to you, ones you know arrived. Find each in the new report by tracking number. Walmart says the data is the same, and this is how you confirm it for your own account.

How do you tell the two kinds of return apart? The new report now holds what used to be in two places: returns from customers, and inventory sent back to you. Walmart's note doesn't describe how the combined report marks the difference. Look at your own download and find the column or value that separates them. Don't guess from the file name or the order of rows. If you can't find a clear marker, ask Walmart Seller Support before you rebuild anything on top of it.

Do the columns match what your routine expects? Names, order and formats may differ from the old file. Dates and quantities are the usual places where a pasted sheet goes quietly wrong.

Step 3: rewire receiving, then reconciliation

Start with receiving. This is where returned units turn back into stock you can sell, so it's the step to get right first.

If someone checks in boxes by hand, rewrite their instructions: which report to download, how to filter to the inventory sent back to you, and which column holds the tracking number they match at the dock. Have them do one week with the new instructions while you watch, then hand it over.

If a tool imports the file, update the import to read the new report and apply the filter from Step 2. Test it on the four-week download first, not on today's live data. Check that a unit doesn't get added twice, once as a customer return and once as a return to you. Tracking number plus quantity is a sensible way to spot a duplicate. Keep the old instructions for a month, marked as retired, so anyone who follows them by habit sees the change rather than an empty file.

Then the reconciliation. Once a month, or once a week if you're busy, someone should be able to answer: everything WFS said it sent back, did we receive it? That check used to start from the Returned to Seller report. It now starts from the filtered Customer Returns report.

Keep it simple. A list of shipments sent back, with tracking numbers and quantities, next to a list of what you received. Anything on the first list but not the second after a reasonable delivery window is a follow-up. If you file claims for missing or damaged returned inventory, make sure the person who files them knows where the data now lives. Run the check once on the four-week download before you rely on it, so you know what a normal month looks like.

Step 4: make the next retirement noisy

The reason this kind of change bites is that most routines don't notice an empty or missing file. Add two cheap checks so the next one is loud.

An "empty" alarm. If a routine downloads a report and gets zero rows for a week when you'd normally see some, it should tell a person, not carry on.

A release-note habit. Walmart's release notes page is short and dated. Someone glancing at it every two weeks would have caught this, and the October 19 note that some legacy automotive product types are being retired from early 2027, which matters to anyone mapping listings through the API. We made a similar case about routines that quietly stop working in the report that worked in March times out in December.

When the routine is worth automating

If walking through these steps shows that three people touch the same returns data in three different sheets, the report change isn't the real problem. A single, small workflow that pulls the report, splits the two kinds of return, updates stock and flags missing shipments to one person is a few days of work and saves that every week. It's the kind of thing our business automation team builds, with a named owner and clear errors when something goes missing. Talk to us if you'd like help sizing it.

Related work: Spin Market.

How the work moves

Walking the change

  1. Find users

    People, sheets and scheduled jobs.

  2. Compare files

    Five known shipments, by tracking number.

  3. Fix receiving

    New report, filtered, no double counts.

  4. Fix reconciling

    Sent back versus received.

  5. Add an alarm

    Zero rows means tell a person.

Illustrative order of work; not Walmart's documented process.
twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Spin:Market ↗︎