Walmart Deprecated Five Shipping Settings Endpoints and the Replacement Does Not Ship Until August 31

Most sellers will never read a Walmart developer changelog, and that is usually fine. This one is worth ten minutes, because it touches the thing that decides whether your item shows a competitive delivery date.

On August 4, 2026, Walmart deprecated the Simplified Shipping Settings endpoints. The replacement, SSS 2.0, launches August 31, 2026. Walmart’s own guidance is that calls to the old endpoints are no longer supported and may fail, and that sellers and solution providers need to migrate to avoid disruption.

Read those two dates together. The old thing is deprecated now. The new thing is not live yet. That gap is the story.

What was deprecated

Five endpoints, per Walmart’s developer portal:

• Create Simplified Shipping Settings
• Update Simplified Shipping Settings
• Update FC level Simplified Shipping Settings
• Get Simplified Shipping Settings
• Bulk item migration for Simplified Shipping configuration

Scope, in Walmart’s words, is any integration for shipping templates that relies on those endpoints.

Why an API deprecation is an operations problem

Shipping templates are not a back office detail on Walmart. They set transit time, regions, and the delivery promise the customer sees on the item page. Delivery speed feeds conversion and it feeds the Buy Box. When template automation stops working, the failure is quiet and the symptom shows up somewhere else.

The realistic failure mode looks like this. Your integration tries to push an updated transit time or a fulfillment center change. The call fails. Nobody watches that log. The template stays at whatever it was set to last month. Your delivery promise on a chunk of the catalog is now wrong in a direction you did not choose, and you find out through a soft conversion decline or a late shipment rate creeping up.

That is a bad thing to discover in October.

Who this actually hits

Almost nobody calls these endpoints by hand. The exposure sits with whoever owns your integration:

Channel management platforms and listing tools that write shipping templates for you. 3PLs and fulfillment partners that update fulfillment center level settings. Agencies and in-house dev teams running a direct Walmart Marketplace API connection. Anyone who did a bulk shipping configuration migration and assumed it stays wired.

If your Walmart catalog is managed through any of those, the migration is their work and your risk.

The one question to ask this week

Send this to every partner that touches your Walmart account, in writing:

Are you using the deprecated Simplified Shipping Settings endpoints, and what is your migration date for SSS 2.0?

You are looking for a specific answer with a date attached. A partner who says they are aware and migrating on September 2 is fine. A partner who does not know what you are talking about is the problem, and you want to find that out on August 23, not November 23.

What to do on your side

Confirm your shipping templates are currently correct. Do this manually in Seller Center, today, independent of any integration. Transit times, regions, fulfillment center assignments. This is your baseline. If automation goes quiet, correct settings sitting in place is a much better failure state than wrong settings sitting in place.

Freeze non-essential template changes through the transition. If you do not need to restructure shipping configuration in the next two weeks, do not. Fewer writes means fewer silent failures.

Watch late shipment and delivery promise metrics daily through mid September. Walmart exposes late shipment summary metrics and order level reports through the Insights API, and the same data is in Seller Center. An unexplained move there is your early warning that something in the shipping stack stopped writing.

Validate after your provider migrates. Do not accept “we migrated” as the end of it. Push one real template change and confirm it lands. Migrations of this kind usually work. The ones that do not, fail silently.

The broader pattern

Walmart has been rebuilding its API surface fast this year. Refunds performance endpoints deprecated in March. Item spec 5.0 versions rolling roughly monthly. New listing quality and content quality reports on August 17. Shipping settings now. The platform is maturing quickly, which is good for sellers who want programmatic control, and it means integration debt has a shorter shelf life than it used to.

The operator takeaway is not about this one endpoint set. It is that “our integration works” is a claim with an expiration date on Walmart, and the cost of finding out late is highest in Q4. Put a standing item on someone’s calendar to read the Walmart developer What’s New page monthly. It takes five minutes and it catches this class of problem before it becomes a revenue problem.

If you want someone to audit your Walmart shipping configuration and integration setup before peak, book a strategy assessment.