SP-API Updates: New Shipment Notification for Tracking Number Changes in MCF, New EU Customs Product Identifiers Requirement, and New Enum Value for Finances API
Amazon is updating the SP-API between October and November 2026, introducing a 'Shipment' event for MCF tracking changes (Oct 26), mandatory three-tier EU customs identifiers (Nov 1), and a new 'AMAZON_FBA_FROM_ORIGIN' enum value in the Finances API (Nov 6).
Overview
Amazon is implementing three distinct updates to the Selling Partner API (SP-API) scheduled for rollout between October and November 2026. These changes target Multi-Channel Fulfillment (MCF) tracking notifications, mandatory customs documentation for European Union (EU) imports, and the categorization of financial data within the Finances API. Sellers must update their technical integrations and product databases to prevent shipment seizures at EU borders, avoid customer service friction due to outdated tracking, and ensure accounting software remains compatible with new financial data labels.
Key Points
- MCF Notification Shift — Starting October 26, 2026, Amazon will trigger a "Shipment" event instead of an "Order" event whenever a tracking number for an MCF order is modified.
- EU Import Mandate — Beginning November 1, 2026, all B2C shipments sent from non-EU countries into the EU must contain specific product identifiers to satisfy customs requirements.
- Three-Tier Identification — EU-bound shipments must now include a combination of the ASIN, a manufacturer-specific part or model number (or barcode), and a Standard Product Identifier (S-PID) like a GTIN.
- Finances API Expansion — On November 6, 2026, the
ListTransactionsoperation will introduce a newAMAZON_FBA_FROM_ORIGINvalue within theBusinessContext.storeNamefield. - Global vs. Regional Scope — While the MCF and Finances API updates affect all global Amazon marketplaces, the customs identifier requirements apply exclusively to shipments entering the EU.
- Seller Liability — Amazon explicitly states it will not verify the accuracy of manufacturer part numbers or barcodes; sellers bear all risk for customs delays or seizures resulting from incorrect data.
What's Changing
Multi-Channel Fulfillment (MCF) Tracking Notifications
Amazon is altering the notification logic for MCF orders to ensure that sellers and their customers always have the most current shipping information, particularly when a package is rerouted or relabeled.
Analysis & Recommendations
Why This Matters
Failure to provide ASIN, NS-PID, and S-PID for EU shipments will result in customs delays or seizures. Developers must also update OMS logic to handle 'Shipment' events to prevent customers from using outdated tracking numbers.
Key Takeaways
- MCF tracking updates will shift from 'Order' events to 'Shipment' events starting October 26, 2026.
- EU B2C shipments must include a three-tier ID system: ASIN, Manufacturer Part/Model Number (NS-PID), and a Standard Identifier (S-PID) like GTIN.
- The Finances API ListTransactions operation adds 'AMAZON_FBA_FROM_ORIGIN' to the BusinessContext.storeName field on November 6, 2026.
Recommended Actions
- →Update Order Management System (OMS) code to overwrite existing tracking IDs when a 'Shipment' event is received for MCF orders.
- →Audit EU-bound SKU databases to ensure every product has a manufacturer part number or barcode mapped to the NS-PID field.
- →Add 'AMAZON_FBA_FROM_ORIGIN' to the allowed values list in financial data parsers to prevent accounting software errors.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!