Walmart MCS adds order, shipment, and return webhooks: what changes for sellers

Walmart’s September 28, 2026, developer update adds webhook support for Multichannel Solutions (MCS) order, shipment, and return activity. Integrations can subscribe to events instead of repeatedly asking an API whether something has changed.

What is a webhook?

A webhook is a notification sent to a connected application when an event occurs. For a seller, the distinction is straightforward: a system can receive a change notification rather than wait for its next scheduled status check. What happens afterward depends on how that system is built.

Which MCS events are supported?

Walmart names three subscriptions in the update and MCS webhooks guide:

• ORDER_STATUS_UPDATE: changes such as an order being acknowledged, shipped, or canceled.
• ORDER_SHIPMENT_UPDATE: shipment information, including tracking and carrier updates.
• MCS_RETURN_ORDER_STATUS_UPDATE: return activity; payload.header.eventName identifies the particular return event.

Walmart’s return coverage includes stages from authorization and label generation through receipt, disposition, and disputes. The implementation owner should match the events to the processes your business actually needs.

What a seller should expect and check

Hypothetical workflow: an order-management tool receives a shipment event, matches it to the right order, and updates a customer-service dashboard. A returns tool could similarly surface a disposition change for review. These are possible uses, not evidence that a particular provider already performs them.

Map the notification to a business outcome before commissioning work. Do you need quicker tracking visibility, a returns exception queue, or fewer manual status checks? Choose a measurable problem rather than adding every available event to an unused dashboard.

Implementation needs more than a subscription

Walmart’s setup directions call for supported-event discovery, subscriptions, and a publicly accessible HTTPS endpoint. Its best-practices guidance also addresses duplicate events, timely responses, logging, and endpoint monitoring.

A repeated notification should not cause the same downstream business action twice. Ask the implementation owner to demonstrate how duplicates and processing failures are handled before relying on an automated workflow.

• Confirm that your provider supports the new MCS events for your connection.
• Agree which event should update which system or trigger which action.
• Have the integration owner review access, payload fields, and subscription setup.
• Test representative changes and repeated notifications in a suitable test environment where supported.
• Confirm ownership of monitoring and failure handling, then compare the result with the original business problem.