Update: Buy Box notification

Date: March 03, 2026

We are excited to share that the Buy Box notification improvements many of you have requested are now arriving.

We are expanding the payload to include offer-level data and improving notification timelines so your tools can respond faster. The updated webhook includes expanded item and offer fields, with parameter-level definitions for new attributes such as priceDifference, offers[], isWFS, and proSellerBadge.

Review the updated Buy Box event schema for exact types, calculation rules, and when each field will be present.

What changed

Added the following webhook payload fields:

  • Support for partnerId and additional itemInfo fields, including itemName, category, productType, itemCondition, brand, sku, and totalNumberOfOffers.
  • Expanded offer details through the currentOffer and winningOffer objects, including seller name, pricing, shipping speed, shipping price, Pro Seller badge status, and WFS fulfillment status.
  • A new offers[] array that returns the top five ranked offers, ordered by landed price (item price + shipping).
  • Updated payload to include prosellerbadge, isWFS(), isSuppressed, itemconditionname + offers.
  • A priceDifference field that provides the calculated difference between the current offer price and the Buy Box winning offer price.

Why it matters

  • Provides clear, consistent logic for how offers are ranked and how price comparisons are calculated.
  • Helps reduce pricing discrepancies and unexpected behavior in repricing or monitoring systems.
  • Minimizes the need for additional API calls by including expanded item and offer details directly in the webhook payload.

Next steps

  • Review the updated Buy Box event webhook payload schema and field definitions.
  • Update your Buy Box webhook handling logic to process the new fields and the offers[] array.
  • Validate changes in a sandbox or non-production environment before deploying to production.