Upcoming changes to inventory webhooks

To drastically reduce notification volume and improve integration efficiency, Clover optimizes the Item (I) webhook topic. Historically, the Item topic fired webhooks for item attribute changes and item stock changes. The new architecture decouples item attributes and stock-related changes. New dedicated webhooks include stock count and availability data directly in the payload, which eliminates the need for expensive API callbacks to fetch updates.

New three-webhook architecture

Moving forward, item-related changes split into three distinct, specialized webhook topics:

1. Item (I) webhook

• Trigger: Fires for general item attribute changes (for example, name, price, description, and category).
• Exclusions: Does not fire for stock count or availability changes.
• Payload type: Lightweight notification (indicates that a change occurred; requires a callback for details).

2. Item Stock (IS) webhook

• Trigger: Fires when a merchant manually updates the stock quantity, when stock is updated via the POST /v3/merchants/{mId}/item_stocks/{itemId} endpoint, or when item stock falls below a merchant-defined threshold.
• Payload type: Rich payload (no callback required).
• Payload schema:

{
  "objectId": "IS:UUID_OF_ITEM",
  "type": "UPDATE",
  "ts": 0,
  "object" : {
    "quantity": 0.0, 
    "stockAlertThreshold": 0.0, 
    "modifiedTime": 0 
  }
}

3. Item Availability (IA) webhook

• Trigger: Fires strictly when an item's availability state toggles (true to false, or false to true).
• Payload type: Rich payload (no callback required).
• Payload schema:

{
  "objectId": "IA:UUID_OF_ITEM",
  "type": "UPDATE",
  "ts": 0,
  "object" : {
    "available": true 
  }
}

Compare integration differences

Release timeline

We encourage partners to test these changes in the sandbox environment prior to the production rollout.

• June 9, 2026: Item Availability (IA) webhooks available in sandbox.
• July 7, 2026: Item Stock (IS) webhooks available in sandbox.
• July 20, 2026–July 31, 2026: Live in production.

Clover integration recommendations

Due to the significant drop in webhook frequency, we recommend the following adjustments to your integration logic:

• Transition to pull-on-notify: The Item webhook provides the item_uuid. Subscribers should immediately invoke the GET /v3/merchants/{mId}/items/{itemId} endpoint upon receipt of a webhook to sync the full item state.
• Immediate action: We strongly recommend that partners implement these changes as soon as possible to align with the optimized firing cadence and avoid missing critical inventory shifts.

Frequently asked questions

Do the core Item (I) webhooks continue to fire alongside stock updates?

No. Once this feature goes live in production, the Item (I) webhook is completely decoupled from stock updates and no longer fires when stock quantities or availability change.

Do we need to make a callback API request when we receive an IA or IS webhook?

No. Unlike the traditional Item (I) webhook, both IA and IS pass the relevant state data directly within the event payload. You can update your local database using the webhook payload alone.

Does the Item Stock (IS) webhook fire for every item sold during order placement?

No. To protect system performance, IS does not fire for standard stock decrements during order creation. However, if an order causes an item's stock to drop below the merchant's defined low stock threshold, an IS webhook fires to alert your system. It also fires instantly anytime a merchant modifies stock via the Clover Web Dashboard or via a third-party API endpoint. Note that historically, the Item (I) webhook never fired on stock decrements during order placement.

How do I subscribe to these new webhooks?

No manual action is required. These new topics bundle under the existing Inventory webhook permission group. If your developer application already subscribes to Inventory webhooks, it automatically opts into IS and IA events as they become available.