The getFulfillmentOrder operation now returns the amazonFulfillmentTrackingNumber property. You can use this property in your request to the getPackageTrackingDetails operation to track Multi-Channel Fulfillment (MCF) packages.

The sourceAddress property used in the requests to createInboundPlan and updateShipmentSourceAddress now contains the districtOrCounty property. This change enables you to use the Fulfillment Inbound API to create shipments in the Turkey marketplace.

The following Data Kiosk datasets have updates.

The Seller Performance report (GET_V2_SELLER_PERFORMANCE_REPORT) now includes the unitOnTimeDeliveryRate response attribute. You can use this attribute to get a seller's on-time delivery rate at a unit level within a reporting date range for one marketplace that you specify.

The Product Fees API v0 has the following updates:

Deprecated SP-API resources are no longer in active development. Calls to deprecated SP-API resources will continue to be successful until their removal date. After the removal date, calls will fail. For more detailed information about SP-API deprecation dates, refer to the Deprecations table.

Announcing the Seller Wallet API, which you can use to retrieve financial information that is relevant to a Seller's Seller Wallet account. You can obtain financial events, balances, and transfer schedules for Seller Wallet accounts. You can also schedule and initiate transactions.

Effective August 20, 2025, the getFulfillmentOrder operation provides delivery photos for eligible Multi-Channel Fulfillment (MCF) orders that use Amazon logistics as the last mile carrier.

Starting August 28, 2025, the following operations will return new payment fields:

Starting August 25, 2025, you must complete battery safety compliance questions when you create or edit any Fulfilled by Merchant product listings that contain batteries or battery-powered items.