Walmart Updates Simplified Shipping Settings API
Walmart has updated its shipping settings API by removing the shippingPriority field and adding parameters including shippingMethod, which may affect shipping-rule synchronization and product migration.
What are the key facts?
- 1Walmart revised Simplified Shipping Settings
- 2The shippingPriority field was removed and the shippingMethod field was added
- 3The customShippingRuleName and migrateEligibleOffers parameters were added
- 4Multiple error responses were updated and supplemented
What happened?
On October 15, 2026, Walmart released an API update that significantly revised Simplified Shipping Settings. The update removes the shippingPriority field from requests and responses and adds the shippingMethod field for carrier configuration at the account and fulfillment-center levels. The interface also adds the customShippingRuleName and migrateEligibleOffers parameters and supplements multiple 400, 401, 403, 404, and 500 error responses. The change may not immediately alter consumer-facing shipping prices, but it directly affects cross-border sellers, third-party ERP and SaaS providers, and proprietary systems that read, create, and maintain Walmart shipping rules. Programs using legacy API fields may encounter failed requests, unsynchronized shipping rules, or incomplete product migration. Merchants that manage products in bulk through carrier rules, shipping templates, and fulfillment-center configurations need to check whether their ERP and WMS support the new interface and monitor API error rates and order promise times after the official switch.
What does this mean for cross-border sellers?
Walmart’s Simplified Shipping Settings API removes shippingPriority and adds shippingMethod, customShippingRuleName, and migrateEligibleOffers. Legacy programs may experience failed requests, unsynchronized rules, or incomplete product migration. Sellers using ERP, WMS, or proprietary systems to manage shipping rules should prioritize interface compatibility checks and monitor API error rates and order promise times.
What should sellers do now?
- 1This week, have the technical team inspect Walmart ERP, WMS, and proprietary systems item by item to confirm that shippingPriority has been removed from requests and responses and that shippingMethod is supported; produce a field-mapping table and compatibility assessment.Listing character checker
- 2This week, test the customShippingRuleName and migrateEligibleOffers parameters for Walmart carrier rules, shipping templates, and fulfillment-center configurations; record successful and failed requests and the list of products with incomplete migration.
- 3This week, establish a Walmart API monitoring table after switching to the new interface, classify 400, 401, 403, 404, and 500 error responses, and cross-check the order promise times of affected products to create an exception review table.