HomeDocumentationCode SamplesAPI ReferenceAnnouncementsModelsRelease NotesFAQGitHubVideos
Developer HubAPI StatusSupport
Announcements
Developer HubAPI StatusSupport
Back to All

SP-API Updates: EU FBM Requirements, Product Type Definitions API Title Structure, External Fulfillment API Shipment Status

July 1st, 2026 by FabioR_Amazon

This week's SP-API updates cover new Fulfilled by Merchant (FBM) performance requirements and handling time changes for EU stores, a modular title structure for non-media product types via the Product Type Definitions API, and a shipment status change for Merchant Fulfillment Network orders in the External Fulfillment API.

In this post:

Changes to Fulfilled by Merchant (FBM) requirements in EU stores

Starting July 15, 2026, Amazon is updating Fulfilled by Merchant (FBM) performance requirements and handling time settings in EU stores. These changes introduce new delivery performance thresholds, update default handling time options, and add customs compliance requirements for cross-border shipments. Sellers who do not meet the on-time delivery rate requirement may have listings deactivated or lose the ability to list new FBM products.

Changes

On-time delivery rate requirement (DE, FR, IT, ES only)

Starting July 15, 2026, sellers must maintain an on-time delivery rate of 90% or higher. This metric measures the percentage of FBM units delivered on or before the promised "Deliver by" date. Starting September 1, 2026, if performance remains below 90%, non-compliant listings may be deactivated, or sellers may lose the ability to list new FBM products.

Business hour delivery rate requirement

Starting September 30, 2026, sellers must maintain a business hour delivery rate of 90% or higher. This metric measures the percentage of FBM shipments delivered to Amazon Business customers within their hours of operation. Starting October 30, 2026, if performance remains below 90%, non-compliant listings may be deactivated for business customers.

Handling time changes

Starting July 15, 2026, account-level default handling time will only display zero-day and one-day options. If an account-level handling time is currently set to two days, it will automatically change to one day. Sellers can still set longer handling times per SKU.

Starting September 1, 2026, if a SKU's handling time is one or more days longer than actual performance for more than 30 days, Automated Handling Time will be enabled for those SKUs.

Cross-border customs compliance (shipments originating outside the EU)

Starting July 1, 2026, sellers shipping from outside the EU to an EU address must comply with EU Customs Reform regulations. For shipments under €150 imported under Import One-Stop Shop (IOSS), sellers must select an approved carrier authorized to provide correct customs documentation and supply the carrier with Amazon's IOSS number and ASIN details for each product.

Note: This only applies to sellers who confirm their own shipments (self-ship). If a seller uses Amazon's Buy Shipping service to purchase labels, Amazon handles carrier compliance internally — no action needed.

Exemptions

Orders fulfilled using all three of the following tools will not count toward the on-time delivery rate or business hour delivery rate requirements:

  • Automated Handling Time
  • Shipping Settings Automation
  • Amazon Buy Shipping

All three tools must be enabled for the exemption to apply.

Which marketplaces are affected?

This change applies to the following marketplaces:

Germany (DE): On-time delivery rate, business hour delivery rate, and handling time changes
France (FR): On-time delivery rate, business hour delivery rate, and handling time changes
Italy (IT): On-time delivery rate, business hour delivery rate, and handling time changes
Spain (ES): On-time delivery rate, business hour delivery rate, and handling time changes
United Kingdom (UK): Business hour delivery rate, handling time changes, and cross-border customs compliance only

Who is affected?

Sellers who use FBM in the affected EU stores are affected by this change. Developers with applications that manage FBM listings, configure handling times, or set shipping settings may need to account for the new performance thresholds and handling time defaults.

What action is required?

If you have an application that manages FBM seller settings or performance, be sure to:

  • Update any workflows that set account-level handling time to account for the removal of the two-day default option after July 15, 2026.
  • Ensure that applications that display seller performance metrics surface the new on-time delivery rate and business hour delivery rate thresholds.
  • For cross-border shipment workflows, validate that carrier selection and customs documentation fields support EU Customs Reform requirements.

For more information

To learn more about on-time delivery rate, refer to the On-Time Delivery Rate FAQ. For more information about business hour delivery rate, refer to the Business Hour Delivery Rate FAQ. To review handling time settings, refer to Modify Handling Time. To view all policy changes, refer to Changes to program policies.

New modular title structure for non-media product types

Starting July 27, 2026, Amazon is introducing a modular title structure for all non-media product types. Product titles will be separated into two components:

  • item_name (up to 75 characters)
  • title_differentiation — a new attribute (up to 125 characters) in the product type schema

Total content capacity remains 200 characters, split across the two fields. The new Item Highlight (title_differentiation) field can only be used when item_name is 75 characters or fewer.

The modular title structure separates core product identity from differentiating details, enabling more consistent and structured product discovery across stores.

Which marketplaces are affected?

This change applies to all marketplaces, except Saudi Arabia, Egypt, Turkey, and the United Arab Emirates.

Who is affected?

Developers with applications that use the Listings Items API or JSON_LISTINGS_FEED feed type to create and edit product listings are affected by this change. Existing product listings are not affected unless you choose to submit an update.

What action is required?

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

  • Refer to the Product Type Definitions API for the updated schema details, including the title_differentiation (Item Highlight) attribute.
  • Begin submitting item_name and title_differentiation as separate attributes for new or updated listings on or after July 27, 2026.
  • Review your current listings and consider updating to the modular title structure through 2026.

Note: Current listings are not affected unless you choose to submit an update, so you can integrate at your own pace through 2026.

For more information

To learn more about product titles, refer to Product title requirements and guidelines.

Merchant Fulfillment Network shipment status update for External Fulfillment API

Starting June 30, 2026, the initial status for Merchant Fulfillment Network (MFN), including Easy Ship, Self Ship, and Self Delivery program shipments, will change from CREATED to ACCEPTED. This change is rolled out gradually for all sellers, and new shipments will be available in ACCEPTED status upon creation. The CREATED status is on a deprecation path.

Which marketplaces are affected?

This change applies to all marketplaces.

Who is affected?

Developers with applications that use the External Fulfillment API to create or manage MFN / Easy Ship shipments 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 integration to fetch shipments in ACCEPTED status in addition to CREATED.
  • During the transition period, fetch shipments in both statuses (1 status per getShipments API request).
  • If your system relies on the CREATED status as part of your shipment workflow, ensure you update your logic to also handle ACCEPTED status.
  • Plan to fully migrate to ACCEPTED status before the CREATED status is deprecated in late July 2026.

    Note: During the transition period, you are required to fetch shipments in both statuses (1 status per getShipments API request).