Walmart Marketplace Adds Price and Promotion Testing to Dynamic Sandbox

What happened: On November 17, 2026, Walmart Marketplace's developer portal expanded its Dynamic sandbox to support the PRICE_AND_PROMOTION feed type, so sellers can now test bulk pricing and promotional updates in a sandbox environment before pushing them to production. The change is documented on Walmart's developer "What's new" changelog and confirmed in the feed's own API reference and sandbox throttling docs.
What the sandbox change actually covers
The PRICE_AND_PROMOTION feed is how sellers update prices and promotional pricing in bulk for multiple items at once, through POST /v3/feeds?feedType=PRICE_AND_PROMOTION. Until this change, sellers testing a pricing integration had no safe way to validate a feed's structure, item matching, or promotional logic without risking a live price change on a real listing. The Dynamic sandbox now lets that same feed type run against synthetic data first.
- Feed type:
PRICE_AND_PROMOTION, now available in Dynamic sandbox alongside production. - Scale: each feed can carry up to 10,000 items, though Walmart recommends keeping feeds to 1,000 items and under 10MB.
- Sandbox limits: up to 30 requests per hour, 25KB max file size per call, roughly 30 minutes processing time per request.
- Production SLA: bulk price updates are still processed with a 15-minute service-level target once a feed moves out of sandbox.
Why it matters for Amazon and Walmart brands
Most pricing and repricing tools built for Walmart Marketplace - whether an internal script or a vendor's repricer - eventually have to push a PRICE_AND_PROMOTION feed to change what a shopper sees. Before this sandbox expansion, the only way to confirm that a new rule, a new SKU mapping, or a promotional calendar change actually produced the right payload was to run it against live listings and watch for mistakes. A malformed feed or a bad item match on a pricing feed is not a cosmetic bug: it changes what customers pay.
Brands running their own pricing automation, or evaluating whether to build one instead of leaning on a third-party repricer, now have a safe staging layer to validate feed logic against edge cases - clearance SKUs, multi-tier promotions, bundle pricing - before anything reaches a live catalog. That is exactly the kind of integration work worth building deliberately rather than testing in production: a team doing marketplace platform development services can wire sandbox validation directly into a CI pipeline, so every pricing rule change runs through Walmart's test environment automatically before it ships.
What to check before you touch your pricing feed
- Confirm your integration or vendor already targets Dynamic sandbox for
PRICE_AND_PROMOTION, not just the older static test mode. - Map your busiest promotional scenarios - clearance, multi-buy, bundle - as sandbox test cases before the next pricing event.
- Respect the sandbox throttle (30 requests/hour, 25KB per call) when scripting automated test runs, since it is tighter than production.
- Re-test after any repricer or ERP update that touches how pricing payloads are built, since sandbox now makes that a five-minute check instead of a live-catalog gamble.
None of this is mandatory to keep selling on Walmart today. It is a free way to catch a pricing mistake before it reaches a shopper's cart instead of after.


