This week's SP-API updates include a new shipment notification for tracking number changes in Multi-Channel Fulfillment (MCF), a new EU customs product identifiers requirement for FBM shipments to the EU, and a new Enum value for the Finances API.

Multi-Channel Fulfillment FULFILLMENT_ORDER_STATUS Notification Sends Shipment Event on Tracking Number Changes

Starting October 26, 2026, the Multi-Channel Fulfillment (MCF) FULFILLMENT_ORDER_STATUS notification (payload version 1.0) will send a Shipment event when a shipment's tracking number changes.

Today, when a shipment's tracking number changes after the shipment is created (for example, from a label re-generation at the fulfillment center), the version 1.0 FULFILLMENT_ORDER_STATUS notification sends an Order event that does not include the new tracking information. Applications on version 1.0 are therefore not notified of the change and may keep using an outdated tracking number.

With this update, a tracking number change sends a Shipment event that includes the new tracking information which is the same event you already receive when a tracking number first becomes available. Use it to update tracking in your systems automatically, without polling. The Shipment event will replace the Order event in this scenario.

This change is backward compatible. The Shipment event and its payload are what your application already processes for new tracking numbers; the update only extends when that event fires to also cover tracking and carrier changes.

Which Amazon Stores are affected?

This change applies to all Amazon stores.

Who is affected?

Developers whose applications subscribe to the FULFILLMENT_ORDER_STATUS notification (payload version 1.0) for MCF orders and use its shipment tracking information.

What action is required?

No action is required to receive the corrected notifications. To ensure a seamless transition, be sure to:

• Confirm your tracking-update handling treats the Shipment event as authoritative for the current tracking number and carrier.
• Verify that a change on an existing shipment updates the tracking information you store and pass downstream.

For more information

To learn more about handling tracking number or carrier changes, refer to Retrieve Package Tracking Details.

For the FULFILLMENT_ORDER_STATUS notification reference, refer to the Notifications API use case guide.

EU Customs Will Require Product Identifiers for FBM Shipments to the EU

Starting November 1, 2026, EU customs will require product identifiers for all business-to-consumer (B2C) goods shipped into the EU from outside of the EU.

Which Amazon Stores are affected?

This change applies to all EU Amazon stores.

Who is affected?

Developers with applications that purchase shipping labels or manage carrier integrations for seller-fulfilled (Fulfilled by Merchant, FBM) orders shipped from outside the EU to EU destinations are affected by this change.

What action is required?

Your integration must supply three identifiers for each item:

• The ASIN (Merchant Product Identifier, M-PID). Amazon adds this automatically on Buy Shipping label purchases.
• The manufacturer's part number or model number (Non-Standard Product Identifier, NS-PID). If a product has neither, send a barcode number in its place.
• The Standard Product Identifier (S-PID), for products that have one. Examples include EAN, GTIN, UPC, ISBN, and ISSN.

If you buy labels through Buy Shipping (Shipping API or Merchant Fulfillment API), your integration must send these identifiers on the label purchase request. Amazon adds the ASIN automatically but does not add the part number, model number, or barcode from the product's listing, so your integration must send those. Amazon applies no format validation and transmits the submitted values to the carrier as provided, so you are responsible for the accuracy of the information you submit. Build and test now to be ready before November 1, 2026. Follow these steps:

• Send the manufacturer's part number or model number for each item. This is required. If a product has neither, send a barcode number in that field instead.
• Optionally, send the barcode number (EAN, GTIN, UPC, ISBN, or ISSN) for each item that has one. These fields are optional.
• If a request fails, show the seller the error and provide a field to enter the missing number. Do not submit placeholder values.

If you send customs data to carriers directly, your integration must add these identifiers to the customs data you send to the carrier. This path is required starting November 1, 2026, including for labels purchased outside Amazon. Amazon does not receive or validate this data, so you are responsible for the accuracy of the identifiers you send. Missing identifiers can cause a shipment to be held or returned at customs, at the seller's expense. Follow these steps:

• Confirm the required fields and format with each carrier you support.
• Add the ASIN, the part or model number, and the barcode number for each item to the customs data you send to the carrier.
• Verify that every item has a part or model number before the seller confirms the shipment. If a number is missing, provide a field where the seller can enter it.

For more information

Refer to Shipping API v2 and Merchant Fulfillment API v0 for API details.

New AMAZON_FBA_FROM_ORIGIN Enum Value for Finances API BusinessContext.storeName Field

Starting 6 November 2026, the BusinessContext.storeName field in the Finances API ListTransactions operation (/finances/2024-06-19/transactions) will include a new possible value: AMAZON_FBA_FROM_ORIGIN, representing FBA from origin transactions.

This is an additive, backwards-compatible change. The BusinessContext object is an optional element in the response contexts[] array, so it only appears for program-specific transactions. The new AMAZON_FBA_FROM_ORIGIN value will only appear on new FBA from origin transactions. No existing API responses are modified. This is in addition to the existing AMAZON_HAUL value.

Which Amazon stores are affected?

This change applies to all Amazon stores.

Who is affected?

Developers with applications that consume the ListTransactions API (/finances/2024-06-19/transactions) and parse the BusinessContext.storeName field are affected by this change.

What action is required?

If you have an application that is affected by this change, be sure to:

• Update your storeName parser to handle the new AMAZON_FBA_FROM_ORIGIN value if your application uses strict enum validation.
• No action is required if your application already handles unknown enum values gracefully (e.g., ignores unrecognized values or uses a default/fallback)

For more information

To learn more about the ListTransactions API, refer to the Finances API reference.