New: Order management webhook event
My Account

New: Order management webhook event

Date: February 11, 2026

Walmart now pushes order lifecycle updates to your endpoint in near real time. The ORDER_UPDATES webhook replaces separate status-specific webhooks with a consistent JSON envelope and extensible sub-events, so you can trigger fulfillment, handle cancellations, and reduce polling. This model lets us add new statuses for sellers and approved solution providers without creating a new webhook for each case.

What changed

  • Added
    • New webhook event: ORDER_UPDATES (Event version V1, Resource ORDER) with sub-events in payload.subEventType
    • Current sub-events: PO_CREATED, PO_LINE_AUTOCANCELLED, INTENT_TO_CANCEL, FRAUD_CANCEL
    • Subscribe once and route by subEventType instead of maintaining multiple webhook events
    • Extensible design so new statuses can be added to ORDER_UPDATES over time
  • Deprecated (removal on Dec 15, 2026)
    • Legacy standalone webhook events PO_CREATED, PO_LINE_AUTOCANCELLED, and INTENT_TO_CANCEL will continue to work, but will be deprecated on December 15, 2026.

Why it matters

  • One subscription covers many order updates, which simplifies setup and maintenance
  • FRAUD_CANCELsub-event gives you a real-time signal from Walmart fraud review to halt fulfillment, prevent seller-fault metrics, and trigger the right customer and refund flows
  • You can adopt new statuses without changing endpoints
  • Fewer moving parts reduce operational risk and speed delivery of future use cases
  • Cuts down on Orders API polling and rate-limit pressure

Next steps

  • Create a subscription to ORDER_UPDATES using POST /v3/webhooks/subscriptions
  • Route by payload.subEventType in your listener
  • Test in sandbox and validate each sub-event end to end
  • Refer to Order Management Webhook API Guide for contract details

Target timelines / migration

  • The legacy PO_CREATED, PO_LINE_AUTOCANCELLED, and INTENT_TO_CANCEL webhook events will be deprecated and removed on December 15, 2026. Begin migrating flows to ORDER_UPDATES now to avoid disruption. The deprecation schedule follows our API deprecation policy.