---
updatedAt: 2026-09-10T17:49:41.000Z
---

# Seller performance alarms

Use this webhook to receive shipping risks and actions for a seller as they are identified based on seller activity. This helps prevent auto cancellations and late deliveries and prioritize fulfillment tasks.

**Event type**

* Use the `SELLER_PERFORMANCE_NOTIFICATIONS` event
* Route by `payload.notificationType`= `ALARMS`

**Who this is for**<br />Operations and fulfillment teams, and approved Solution Providers that coordinate order processing and shipping.

## How it works

1. Walmart evaluates orders for the prior and upcoming windows.
2. Walmart summarizes shipping risks and actions and posts an `ALARMS` notification to your callback URL.
3. Your service stores the event and creates tasks for each alarm.
4. Your service returns 2xx after a durable write.

### Timing

Notifications are triggered based on seller activity and may arrive at different times. They are not delivered on a fixed schedule. Design your integration to process notifications as they arrive.

## Before you begin

* A Walmart Marketplace account and API credentials
* A public HTTPS callback URL

## Delivery payload

### Delivery format

Webhook requests include a `payload` object with event-specific fields. Use the following schema to validate and parse the payload, then return a 2xx response after a durable write.

### Payload schema

```json
{
    "source": {
        "eventType": "SELLER_PERFORMANCE_NOTIFICATIONS",
        "eventTime": "2019-02-21T01:01:08.000Z",
        "eventId": "03d34580-61d4-11ea-9e23-cd38810ff7cd"
    },
    "payload": {
        "partnerId": "123456789",
        "lastRefreshTs": "2025-09-10 12:52:36 UTC",
        "ordersApiUrl": "https://developer.walmart.com/",
        "moreInfoLink": "https://marketplacelearn.walmart.com/guides/Policies%20&%20standards/Performance/Performance-alarms",
        "supportedLanguages": [
            "en-US"
        ],
        "notificationType": "ALARMS",
        "enNotification": {
            "summary": "We have identified 100 orders that need your immediate attention.",
            "message": "For information on all the orders, please use the following orders api",
            "poNumberMaxCount": 1000,
            "alarms": [
                {
                    "alarmType": "LateOriginScan",
                    "orderCount": 5,
                    "description": "We have noticed that the above shipped orders have not been scanned by the carrier within 48 hours of the shipping confirmation being sent.",
                    "action": "We suggest you contact the carrier as needed to address the delays and verify your tracking information is valid for all your shipments.",
                    "poNumbers": [
                        "123",
                        "456"
                    ]
                },
                {
                    "alarmType": "AutoCancelledYday",
                    "orderCount": 5,
                    "description": "We did not receive valid tracking information within 4 calendar days after the Expected Ship Date (ESD), resulting in the automatic cancellation of the         above orders.",
                    "action": "Do not ship the above order, as the customer has already been refunded.",
                    "poNumbers": [
                        "123",
                        "456"
                    ]
                },
                {
                    "alarmType": "AutoCancelledWarning",
                    "orderCount": 5,
                    "description": "We have not yet received tracking information for the above orders.",
                    "action": "Please upload valid tracking information today or proactively cancel the orders.",
                    "poNumbers": [
                        "123",
                        "456"
                    ]
                },
                {
                    "alarmType": "ShippingDueToday",
                    "orderCount": 5,
                    "description": "We have not yet received tracking information for the above orders.",
                    "action": "Please upload valid tracking information today or proactively cancel the orders.",
                    "poNumbers": [
                        "123",
                        "456"
                    ]
                },
                {
                    "alarmType": "UnshippedOrders",
                    "orderCount": 5,
                    "description": "We have not yet received tracking information for the above orders.",
                    "action": "Please upload valid tracking information today or proactively cancel the orders.",
                    "poNumbers": [
                        "123",
                        "456"
                    ]
                }
            ]
        }
    }
}
```

**Field notes**

* `ordersApiUrl` helps developers link to order-level details for investigation and remediation.
* `moreInfoLink` points to guidance on performance alarms.
* `enNotification.alarms[]` contains one element per alarm type, with an `action` string and a list of affected `poNumbers` for quick triage.

## Handle the event

1. Confirm the event targets a seller you manage.
2. Store the payload and deduplicate using the delivery identifier exposed to integrators (for example, a top-level `eventId` or a documented delivery header).
3. Create tasks or alerts based on `enNotification.alarms[]`.
4. Return 2xx after you finish the write.

## Errors and retries

* Walmart retries on non-2xx with backoff.
* Repeated failures can mark your endpoint as broken and trigger email notices to your contacts.
* Monitor delivery logs and fix broken endpoints before you re-enable them. Refer to [Troubleshooting and delivery health](/us-marketplace/docs/troubleshooting-and-delivery-health/).

## Test in sandbox

Use the test delivery endpoint to send a sample event to your callback URL. Start with the sample payload and adjust alarm types to validate your flows.<br />How-to: [Test in sandbox](/us-marketplace/docs/test-in-sandbox/)<br />API reference: [Test notification](https://developer.walmart.com/us-marketplace/reference/testnotification)

## Next steps

* Set up your webhook endpoint: [Set up your Performance webhook endpoint](/us-marketplace/docs/set-up-your-performance-webhook-endpoint)
* Subscribe or update endpoints: [Subscribe to the performance webhook](/us-marketplace/docs/subscribe-to-the-performance-webhook)
* Validate in sandbox: [Test in sandbox](/us-marketplace/docs/test-in-sandbox/)

## Reference guide

* [Get event types](https://developer.walmart.com/us-marketplace/reference/geteventtypes): Lists available performance events and versions.
* [Create subscription](https://developer.walmart.com/us-marketplace/reference/createsubscription): Registers your callback URL for a webhook endpoint that can receive `ALARMS` notifications.
* [Update subscription](https://developer.walmart.com/us-marketplace/reference/updatesubscription): Changes an existing subscription to route this event to a different endpoint or to adjust the event set.
* [Test notification](https://developer.walmart.com/us-marketplace/reference/testnotification): Triggers a sample delivery to your callback URL to validate event handling.

## Related

* [Performance webhook overview](/us-marketplace/docs/performance-webhook)
* [Event catalog](/us-marketplace/docs/event-catalog)