Overview

Amazon has changed the response schema for the getFeaturedOfferExpectedPriceBatch operation, making the offerIdentifier field optional. The adjustment takes effect immediately, allowing error payloads to omit this element without breaking client parsers. Sellers using this endpoint need to revise their JSON handling to accommodate responses that may or may not contain offerIdentifier, ensuring uninterrupted price‑prediction workflows.

Key Points

• Optional identifier — The offerIdentifier attribute is no longer mandatory in each FeaturedOfferExpectedPriceResponseBody.
• Error payloads now parse cleanly — Responses that contain errors can be processed even when the identifier is missing.
• Existing optional handling stays valid — Integrations that already treated the field as nullable continue to work unchanged.
• Pricing data unchanged — Predicted price values are delivered exactly as before; only the presence of the identifier differs.
• Live as of announcement — All calls made after the release date follow the new, optional schema.

How getFeaturedOfferExpectedPriceBatch Works

1. Build the batch request — Sellers create a JSON payload listing one or more ASINs and, if desired, their corresponding offerIdentifier values.

   • Example: A request includes three ASINs—B01N5IB20Q, B07PGL2ZSL, and B08K2GWK5R—without supplying any offerIdentifier entries.

2. Amazon processes each entry — The service evaluates every ASIN, determines the featured offer for the target marketplace, and calculates an expected price using historical sales, competitor activity, and algorithmic adjustments.

   • Example: For ASIN B01N5IB20Q, the system identifies the seller’s own listing as the featured offer and returns a predicted price of $24.99.