Walmart Adds Sort Parameters to the Orders Management API

What happened: On November 5, 2026, Walmart Marketplace updated the Orders Management All orders API to accept two new query parameters, sortOrder and sortBy. The change rolled out globally, not just to the US marketplace, and it is documented on Walmart's developer portal alongside a separate update the same day that removed the Walmart+ badge from seller-fulfilled offers carrying a return policy exemption.
What the API actually does now
Before this update, a call to the All orders endpoint returned results in whatever order Walmart's backend happened to produce them, and any sorting had to happen after the fact, inside whatever system pulled the data. The new parameters let a seller's system specify the sort key and direction directly in the request, so a dashboard or fulfillment queue can ask for orders sorted the way it actually needs them rather than re-sorting a full page of results on every call. For a brand pulling orders into a retail software development services build, that is a small but real reduction in the amount of client-side logic required just to display a usable order list.
- Endpoint: Orders Management All orders API (
GET /v3/ordersfamily). - New parameters:
sortOrder(ascending or descending) andsortBy(the field to sort on). - Market availability: Global - not restricted to US sellers.
- Companion change, same day: seller-fulfilled offers with a return policy exemption lost Walmart+ badge eligibility.
sortOrder or sortBy keep working exactly as before. The parameters are additive, which is why most sellers have not noticed the update at all.Why it matters for Amazon and Walmart brands
Most multi-channel sellers already pull Walmart orders into some kind of operations view - a fulfillment queue, a customer service dashboard, or a combined feed alongside Amazon and a DTC store. Before this change, getting that view sorted by order date, ship-by deadline, or order status meant fetching a batch of orders and sorting them in code after the fact, which gets slower and messier as order volume grows during peak periods like the holiday season. Being able to request orders pre-sorted by the field that matters - say, soonest ship-by date first - means a fulfillment team's queue can match operational priority without extra client-side work.
It also simplifies anything built on a schedule. A job that polls for the oldest unshipped orders, or a nightly reconciliation script that needs the most recent orders first, can now ask the API for exactly that order instead of pulling everything and sorting locally. That is a small efficiency gain per call, but it adds up across a catalog that is making thousands of order calls a day during a peak week.
What to check before you build anything on it
- Confirm which fields
sortByactually supports for the All orders endpoint - not every field sellers would want to sort on is necessarily exposed yet. - Audit where your current integration sorts orders client-side and consider moving that logic into the API call instead, so one less place in your stack has to stay in sync with Walmart's data model.
- Re-test any saved views or dashboards that assumed a specific default order from the API, since relying on undocumented default ordering was never guaranteed to begin with.
None of this requires immediate action - orders will keep flowing in and out the same way they did on November 4. It is a small opportunity to simplify an integration that is doing more sorting work than it needs to.


