Overview

Amazon’s Fulfillment Outbound API now lets sellers request a recipient signature for Multi‑Channel Fulfillment (MCF) shipments. The capability is limited to deliveries within the United States and can be toggled per order, giving sellers a way to protect high‑value items shipped from Amazon’s warehouses to external sales channels. Sellers who rely on MCF should review the new parameter because it can reduce loss‑related chargebacks while adding a modest fee.

Key Points

• Signature flag — Adding SIGNATURE_CONFIRMATION to the featureConstraints array of the createFulfillmentOrder call triggers a signature requirement for that specific order.
• Order‑level control — The setting is applied individually, so a $750 electronics order can be protected while a $25 accessory order ships without the extra service.
• U.S. only — The feature works solely for destinations that belong to the Amazon.com marketplace; other regions are not yet supported.
• Simple integration — Existing MCF integrations need only one extra field, eliminating the need for separate API endpoints or policy documents.
• Premium pricing — Amazon adds a surcharge on top of standard MCF rates; the fee varies by carrier and service level but is disclosed in the fulfillment cost breakdown.

How Signature Confirmation Works

1. Add the flag — When a seller calls createFulfillmentOrder, they include "SIGNATURE_CONFIRMATION" inside the featureConstraints list.
   Example: A Shopify store sends a fulfillment request for order #1023 and adds the flag to protect a $1,200 smartwatch.
2. API validation — The endpoint checks the destination address to confirm it belongs to the U.S. marketplace and that the selected carrier supports signature collection.
   Example: The API returns an error if the address is in Canada, prompting the seller to remove the flag or choose a different service.