SP-API Updates: New Listings Items API IVP values in EU5, JP, and CA stores, October Updates to Listing Attribute Usage and Enumeration Values, and a New Notifications API Order Change Type Value

This week's SP-API updates include a new Industry Vertical Pricing (IVP) audience values for the Listings Items API in EU5, JP, and CA stores, the October updates to listing attribute usage and enumeration values, and a new Notifications API order change type value.

Industry Vertical Pricing Audience Values Now Available in EU5, JP, and CA Amazon Stores

Starting October 15, 2026, the Listings Items API will accept new Industry Vertical Pricing (IVP) audience values in the purchasable_offer.audiencefield for eligible third-party sellers in the EU5, JP, and CA Amazon stores.

Industry Vertical Pricing (IVP) allows sellers to set industry-specific prices for B2B buyers based on their industry segment (such as Education, Healthcare, or Government). IVP supports both single unit discounts and quantity discounts. This expansion follows the US launch of IVP support in May 2026.

The Listings Items API (/listings/2021-08-01/items/{sellerId}/{sku}) is expanding the set of supported values for thepurchasable_offer.audiencefield.

This is a backwards-compatible, additive change. No existing API operations, endpoints, request parameters, or response structures are modified. The purchasable_offer.audiencefield already accepts string values; this update expands the set of accepted values to include IVP segment audiences, in addition to the existing B2Band ALLaudiences. Applications that do not use IVP audiences are not affected.

Which Amazon Stores are affected?

This change applies to the following Amazon stores:

United Kingdom
Germany
France
Italy
Spain
Japan
Canada

Who is affected?

Developers with applications that use the Listings Items API to create or update listings with the purchasable_offer.audiencefield are affected by this change. Sellers must be enrolled in the Amazon Business Industry Vertical Pricing program to use these audience values.

What action is required?

For developers not using IVP audiences: No action is required. Existing integrations will continue to function without modification.

For developers who want to use IVP audiences via API:

Update your Listings Items API integration to submit the new IVP audience values in the purchasable_offer.audiencefield when creating or updating listings.
Refer to the updated API documentation for the full list of supported IVP audience values and usage guidance.
Ensure that sellers are enrolled in the Amazon Business Industry Vertical Pricing program before submitting IVP audience values. Contact your Amazon Business representative for enrollment details.

For more information

To learn more about the Listings Items API and IVP audience values, refer to Manage Amazon Haul, Advanced Multiple-Offer, and Multiple-Fulfillment Use Cases.

October updates to Listing attribute usage and enumeration values

Effective October 26,2026, Amazon will update the attribute usage and enumeration values of numerous product types across Amazon stores.

For a complete list of metadata channges and affected Amazon stores, refer to SP-API product metadata changes.

Who is affected?

Both private and public developers who use the Listings Items API v2021-08-01 and JSON_LISTINGS_FEED feed type to create and edit products with offers are affected by this change. Product-only listings, XSD feed uploads, and XML feed uploads are not affected by this change.

What action is required?

This change takes effect when you create or edit listings for products with offers. It requires you to provide values for the newly added attributes with required usage. For attributes with optional usage, you can choose to provide values. You can choose to use an enumeration from the new list in the dropdown values for attributes if the new enumeration is more relevant to the product you are selling.

New Order Change Type value for Amazon Autos

Starting October 28, 2026, the ORDER_CHANGEnotification will include the PreFulfillmentStatusChange order change type value for selling partners that sell vehicles through Amazon Autos. Amazon sends this notification when the reservation (pre-fulfillment) status of an order changes. For example, when a customer reserves a vehicle and the order awaits the seller's acceptance, or when the seller accepts or rejects the reservation.

PreFulfillmentStatusChangenotifications include a new optional field, Summary.PreFulfillmentStatus, with the following values: AWAITING_SELLER_ACTION, ACKNOWLEDGED, and REJECTED. This field is not present on any other order change type.

You can also add PreFulfillmentStatusChangeto the orderChangeTypesevent filter when you create an ORDER_CHANGEsubscription with the Notifications API.

Which Amazon Stores are affected?

This change applies only to the United Kingdom Amazon store.

Who is affected?

Developers with applications that subscribe to the ORDER_CHANGEnotification on behalf of Amazon Autos selling partners are affected by this change. Applications that subscribe to ORDER_CHANGEwithout an orderChangeTypesfilter will automatically receive PreFulfillmentStatusChangenotifications for those selling partners' reservation orders.

What action is required?

If you have an application that is affected by this change, you must:

Update your application to accept the new PreFulfillmentStatusChangevalue in OrderChangeType. If your application validates this field against a fixed list, add the new value or ignore values it doesn't recognize.
Read Summary.PreFulfillmentStatusto find the current reservation status, and handle it as an optional field.
Create or update your ORDER_CHANGEsubscription with orderChangeTypes:["PreFulfillmentStatusChange"]to receive only these notifications. To stop receiving these notifications, list only the change types that you want.
Notifications can be delivered more than once, so deduplicate on NotificationIdand use TimeOfOrderChangeto find the latest status.

For more information

To learn more about ORDER_CHANGEnotifications, refer to Notification Type Values.

For the latest information on the Notifications API, refer to the Notifications API reference.